## Claim As a coding agent becomes able to traverse most of a problem on its own, the human's leverage shifts from writing the code to specifying intent well and resolving the unspecified decision points — the "unknowns" — that the agent surfaces along the way. <!-- atomicity: 1 idea ✓ --> ## Scope & conditions Holds for capable agentic-coding harnesses working on real, non-trivial codebases. Breaks when a task is small enough that specification overhead exceeds just doing it directly, or when the agent's autonomy outpaces the human's ability to actually review its output. ## Evidence The map/territory framing from the interview: the plan, prompt, and spec in the human's head is the map; the codebase is the territory; whenever the agent hits something in the territory that isn't on the map, that's an "unknown" to resolve. > [!quote] > the plan and prompt and spec that I have in my mind is the map… the territory is the actual code base… whenever Claude runs into something in the territory that's not in the map, I call that an unknown ## Links - [[3. Resources/MOCs/AI & the Future of Knowledge Work MOC.md]] — because this defines what the human's job becomes once agents can carry most of the implementation ## Tests/falsifiers - This claim would be undermined by a clear counter-case where the described dynamic holds even without the scope condition above, or fails to hold even when the scope condition is met. ## Maintenance - Last tended: 2026-08-16 - Next review: 2026-11-16 ## Source [[3. Resources/Readwise/Articles/Field Guide to Fable — Thariq Shihipar, Anthropic]]