SpecRouteCapability class

The SPEC committee's route (beads pow-7nm + pow-ui8) — the spec-side counterpart of the code committee's CodeRouteCapability, with a THIRD arm between advance and a human gate. It assembles ONE fresh lane vector at entry — the GATING lane's grade off the ambient SiblingView (the effect verb — never a subscription/re-query, D-5), and each JUDGEMENT lane's grade

• rationale off that lane's CURRENT-ROUND verdict artifact on disk (currentVerdictFromFile; a lane with no current-round artifact does not join — bead pow-96s) — applies the deterministic decideSpecRoute matrix over it, and:

• SpecAdvance ⇒ Advance with the SAME provenance payload the code route emits (verdict/grades/spread/rule), and the guidance ledger is DELETED (a later rework round must never re-inject a stale spec correction). When the advance CARRIES a single finding (bead pow-bhm, ratified 2026-07-18) the payload also names it (fix_in_flight + fix_in_flight_finding) and the carry is WRITTEN into the worktree at fixInFlightPath for the build brief to embed — a write that cannot land throws a RouteFailure, LOUD, because an advance whose one known defect silently evaporated is exactly what "every catch keeps its value" forbids. The arm still carries NO grade key, so an advancing round invalidates nothing.

On EVERY arm the route also surfaces the REFINEMENT FLAG (bead pow-bhm): each lane's non-grading BEAD-GRAPH observations, read off the kVerdictRefinementKey verdict column, written to refinementFlagPath, named on the result payload, and appended to an escalate's gate reason. NO arm reads them — tracker state is never the spec author's defect.

• SpecRespec ⇒ the ledger is WRITTEN into the worktree, then an Advance carrying the INVALIDATING stamp grade: 'F' on this route's OWN result. This step declares validates: kSpecifyStep, so the engine DERIVES the wave off that edge the moment the stamp lands on a positively-terminal source: specify ∪ everything downstream of it ∪ this route re-mint as successor incarnations, the committee re-runs VIRGIN in the SAME session, and the next specify ride reads the ledger back as its correction guidance. NO human, no gate bead, no session re-mint. A ledger write that cannot land throws a RouteFailure — LOUD, never a respec whose guidance silently never arrives.
• SpecEscalate ⇒ Escalate — the human flare (a structural F, a critic F, a rationale-less fail, or the round cap) — and the guidance ledger is DELETED. The flare hands the bead to a human, so the AUTOMATIC counter is spent: a gate-resolve re-arm decides on the CURRENT join alone instead of re-reading the consumed round and re-flaring forever (bead pow-p8w).

Offline/dry-run posture: an absent Workspace, or a workspace directory that does not exist on disk (the synthetic /grid/worktrees/... an offline suite mounts), skips the ledger I/O entirely — the same no-op posture ClearCritiqueCapability takes. The verdict and engine-injected circuit round are unchanged.