Nuke Sprint

The pipeline miniaturized to one session (map: references/family-map.md). Producers research and plan, exec builds, verify reviews — sprint runs all four stations itself, at everyday scale, for one small deliverable. Where nuke-code is the loop the constitution engages for un-invoked work and nuke-blitz is the fast lane that prints its plan and goes, sprint is the deliberate lane: it is only ever invoked, it stops at its plan by default, and its hand-back is invalid without the reuse, review, and fit lines.

Core principle — small never means unreviewed: the cycle stays complete at every size. Savings come from scale — one session, solo build, one validator — never from the stations: research, gate, review, and the fix loop run even when the diff is twenty lines.

Arguments

plan — run CALL + RESEARCH + PLAN, print the sprint-plan block, STOP — nothing built, nothing written. <task> — inline text or a path to a brief file. --go — skip the default gate: the block prints and the build starts immediately. The inverse of blitz's --ask.

The lane — countable, checked at CALL