Writing
The Bounty Economy: When AI Gets Stuck, Humans Get Paid
As agents take on more work, they will not fail in clean ways. They will get stuck on ambiguous requirements, missing credentials, weird edge cases, social judgment, and tasks where a human can resolve the blockage in five minutes. That creates a new labor surface: human escalation as a market.
The core idea
The bounty economy is a model where AI systems post small, high-context tasks to humans when automation hits uncertainty. The human does not own the whole workflow. They provide the missing judgment, permission, correction, or data point that lets the agent continue.
Why it matters
This could invert parts of knowledge work. Instead of humans delegating to AI, AI systems may delegate exception handling back to humans. The valuable worker becomes the person who can resolve ambiguity quickly and leave the agent with a better path next time.
How to use it
- Design handoff packets with enough context that a human can answer without reconstructing the whole task.
- Pay for resolved uncertainty, not time spent looking busy.
- Use each handoff to improve the underlying automation so the same blockage does not repeat forever.
The market design problem
A human handoff market only works if the agent can package the task well. The packet needs goal, current state, failed attempts, relevant context, available tools, constraints, deadline, risk level, and what counts as completion. Otherwise the human spends the bounty reconstructing the problem rather than solving it.
The interesting technical layer is routing. Some tasks need domain experts, some need local context, some need policy judgment, and some only need a quick sensory check. The system should classify the blocker, estimate value at stake, and route to the cheapest reliable human intervention.
Useful primitives
- Blocker taxonomy: missing context, ambiguous requirement, tool failure, policy decision, taste judgment, or external dependency.
- Escalation budget: maximum human cost justified by the task value.
- Completion proof: artifact, answer, approval, code diff, or external confirmation.
- Learning loop: convert repeated human fixes into better tools, instructions, or eval cases.
Bottom line
If AI absorbs the routine path, human value moves to the exception path: judgment, taste, context, and permission at the moment automation stalls.