blindspot

# Blindspot The work file, the prompt, the glossary — all map. The codebase, its history, its real constraints — territory. The gap between them is the unknowns, and an unknown left unfound doesn't stay unfound: the diff review finds it, or production does. Sort any unknown into one of four kinds; the flow already mines three: | Kind | What it is | Who finds it | |---|---|---| | Known knowns | Already written down | The work file carries them | | Known unknowns | Questions you know are open | Wonder settles or parks them | | Unknown knowns | Obvious to the user, never said | The interview extracts them | | Unknown unknowns | On nobody's question list | **Only the territory can surface them — this skill** | An interview can't reach the fourth kind: it only asks questions someone thought to ask. This skill owns three moves for the moments the map is furthest from the territory. Each feeds a stage; none replaces one. ## Move 1 — the territory pass (before the work) When work enters an area the user names as unfamiliar, when interview answers keep coming back "I don't know", or when a whole discipline nobody on the work has judgment in walks in (a new subsystem, a new domain entirely) — walk the territory before anyone writes the brief. Read only — the code, its tests, its docs, and its history (log and blame of the area; reverted commits and bug-fix clusters are where it bit last time). Spawn the pass as a fresh subagent **on a frontier-tier model — the session's main mod...