Co-pilots, agents, and the new contract

When the agent does the work, the human still gets the paycheck. That has been the awkward truth of the last few years. The employment contract begins to make that arrangement explicit — and Manav is the bookkeeping layer it requires.

The three contracts

Outcome contracts. Pay for the result, regardless of whether a human or an agent produced it. The customer cares about the deliverable; the contractor decides how to deliver. Manav's role is to record what was shipped, by whom, and under whose attribution. Hybrid contracts. Pay a base for human time plus a percentage for agent-augmented yield. The human's salary is honest about the agent's contribution. Attribution contracts. Pay strictly for the human's authorship at a declared role (authored / supervised / directed) with different rates per role. Knowledge work, increasingly priced this way.

Why this needs an identity layer

Each contract type assumes a verifiable answer to: "what did the human do, and what did the agent do?" Without Manav, the answer is contractual fiction — both sides agree to a number that satisfies the spreadsheet without resolving the actual contribution. With Manav, role declarations are signed, attestations are witnessed, and the math is real. Disputes over "did the human or the agent ship this" reduce to evidence rather than negotiation.

The IP question

Most modern employment contracts vest IP in the employer — language drafted before agents could meaningfully contribute. When an agent fine-tuned on the employer's data produces work the employee then refines, the employer owns the work. When the employee fine-tuned a personal agent on their own time and uses it at work, the IP question gets harder. Manav's role declarations document the chain so the contract can apply rules; it does not write the rules.

What's already shipping

Three platforms run pilots. Toptal is rolling out Manav-attested invoices for engineering contractors; the contract pays per attested artifact rather than per hour. Upwork's agent-disclosure beta requires freelancers to declare AI involvement on each milestone; Manav-attested declarations carry premium pricing. An undisclosed Fortune 100 is piloting an internal "agent-augmented bonus" — engineers receive a multiplier on bonuses for projects where attestations show meaningful supervision-and-direction of agent work, in addition to the base salary on traditional authorship.

What this looks like for unions

Unions have spent the last two years negotiating "AI riders" to existing contracts. The riders typically guarantee that AI-augmented productivity does not become a pretext for headcount reduction. Manav's audit trail makes those guarantees enforceable; without it, the rider is unverifiable. SAG-AFTRA's deal with the studios includes attribution requirements that Manav-style infrastructure would make automatic.

The forward path

Expect every salaried role above $80k to include a paragraph in the employment contract specifying the human's expected role declaration on assigned work, the rate at each declaration class, and the audit log retention obligations on both sides. Manav becomes the substrate the paragraph references. The clauses end up looking like the data-protection paragraphs every contract has carried since GDPR — boring, ubiquitous, structurally important.

Common objections

Two pushbacks we expect. Won't this slow workers down? First delegation prompt costs 90 seconds; allowlisted scopes vanish after that. Won't employers weaponize the audit trail? The protocol design — selective disclosure, user-owned wallet, explicit non-features around compensation and termination cause — addresses the most cited abuse paths.

Frequently asked questions

Does this change my employment contract? Yes, slowly. Expect a paragraph in salaried offers above $80k specifying role-declaration on AI-augmented work, audit-log retention, and IP attribution. The clauses look like the GDPR paragraphs every contract has carried for years — boring, ubiquitous, structurally important.

What about people who don't use AI? They keep working without changes. The protocol is opt-in at the action layer; an unsigned action is the default for any human who has not enrolled an agent. Adoption follows incentives, not mandates.

What happens to my work history when I change jobs? It stays with you. The attestations your employer signed are bound to your DID, not their tenant. The next employer can verify them in seconds; you can revoke their visibility at any time.

Where to start

From here, proof of human work sets the broader work-history substrate and my agent shipped this addresses the hiring-side mechanics. Read those together and the policy questions get a lot more answerable.

The clause every agent contract needs

Every agent payment contract — between merchant and consumer, between counterparties, between platform and user — is converging on a clause that did not exist three years ago. The clause names the human upstream of the paying agent, asserts the scope under which the agent is authorized to transact, and binds the contract's validity to the verification of that scope at the relying party. The clause is short, regulator-readable, and increasingly mandatory. Without it, the merchant cannot defend the transaction against chargeback claims that the agent acted outside authority. With it, the chargeback dispute resolves in seconds against the verification record. The clause is being added to merchant agreements, payment processor T&Cs, and B2B procurement contracts at a quiet but accelerating rate. We expect it to become as standard as the indemnification clause within several years. Builders shipping agent-payment functionality should adopt the clause now and inherit the case law that the early adopters are writing.

If your employment contract treats AI work as invisible, you are negotiating last decade's contract.