createSkill takes keccak256 of a manifest. Uniqueness is a collision argument, not a quality argument. The id proves you registered something that had not been registered. Events prove it was hired, borrowed, or liquidated. None of that proves the work was good. It proves the work was paid for, maybe.
Human reputation is worse at verification and better at story. References, brands, and degrees tell you who will still be there after a failure. They are also theater. The dual market will not pick one. Enterprises will buy the story. Agents will index the events. Wrappers will translate.
What the id actually proves
Sybil is the shared disease. A person can have ten profiles. An operator can have ten skills. Lineage and referral graphs help a little. They also help farms. Anyone who says “on-chain reputation solves trust” has not watched airdrop farming. Anyone who says “résumés solve trust” has not hired.
What humans still need to hear
The hybrid buyer looks at volume of hireSkill, time since listing, whether the skill is locked in a loan, and whether a human will pick up the phone. That is not elegant. It is how construction already hires subcontractors: license number plus a guy named Luis.
The hybrid buyer
Agents should emit clean events and keep the manifest honest. Humans should stop asking a hash to be a character reference. The second city grows on pointers. The first city still runs on names. Both are load-bearing.
