Development record

2026-09-25 — Three shape rulings for the model-tier routing's surface (lane implementer, autonomous run A, on spc-2609180535002478 part 2). First, `--route` sits on the seven verbs whose step an agent in the `agents/` roster runs: `intent audit` and its ingest, `launch ship`, `disembark review`, `principles`, `press-release` and `graveyard`, and `reading ingest`. The spec listed `memory ingest` as an eighth, but its distiller is the host session itself (`commands/memory.md`), not a roster agent, so no row could govern it and a flag there could only refuse; it gains the flag when a roster agent takes that step. A dual-mode verb's deterministic mode dispatches no agent, reads no routing table and refuses `--route`. Second, the receipt is the ingest's result: a `route` member in its JSON and a `route:` line in its text. It is not a new field in any durable record, because each verb's durable record differs (a CHANGELOG, a lifeboat file, an intent's Audit Notes, a reading run) and a routing fact belongs in none of them; the request block is likewise a `routing` member on the steps that precede an agent (`intent audit <itd-N>`, a ready `launch ship` cut), plus a `## Routing` section in the audit's request document outside the hashed prompt. Third, a routing table that cannot be read refuses a delegating verb at exit 2, where the bare board only omits its lines: the verb is about to ask for a model, and the loud-staging rule does not let it guess past the file that decides which.