intent-router

# Intent-Router A compiler does not guess the address of an undefined symbol. Do not guess the user's intent. This runs one layer *before* planning, routing or coding. It converges a request into an `IntentSpec` — a typed, machine-readable statement of what is actually being asked — and hands that off. It does not implement anything itself. ## 1. Purpose and when this fires Three passes, in compiler order: **Parse** the request into a draft spec, **Resolve** every open question by looking it up or asking, then **Typecheck and emit** — route, ask, or halt. Start when **both** hold: 1. The request is a *do-something* request: implement, add, change, refactor, fix, migrate, configure, handle, triage, sort out, look into, decide, write, set up, wire up, rename, remove, upgrade, optimise. 2. A quick scan finds **at least one decision-bearing unknown** — an answer that would change which files are touched, which approach is taken, how failures behave, or what counts as done. Do not start when: - the request asks you to explain existing state ("what does X do", "why is Y slow") rather than to find something out and produce a deliverable; - the silence check below passes — the request already states every decision-bearing item, so there is nothing to converge; - the request is trivially scoped and reversible (fix a typo, bump a patch version). **The silence check.** Run it once, against the request text alone, before probing anything. The request is fully specif...