nuke-code
Nuke Code
The discipline below every ceremony. Family positioning (map: references/family-map.md): exec delegates implementation to subagents · verify repairs another agent's implementation · code is how this session itself works — the loop it runs for its own everyday changes, so ordinary work arrives already reviewed.
Core principle — the family doctrine applied to the session's own hands: weak generation + fresh verification + a fix loop beats trusting the first draft. Final quality is bounded by the strongest verifier, not by the model that typed the code. Nothing leaves the session unreviewed.
Engagement
The constitution (references/constitution.md) routes here with countable triggers; never engage by feel.
| Mode | Trips when | Machinery |
|---|---|---|
| inline | single file AND ≤~30 changed lines AND no contract change | BUILD charter + narrowest gate. No agents. |
| standard | anything beyond inline | full loop; ship validator at session, fresh context |
| elevated | any risk flag — public API, auth/security, concurrency, data migration, new dependency — even when size says inline | full loop; ship validator at top |
Escalate out instead of stretching: diff past ~5 files / ~300 lines → checkpoint and propose nuke-review or nuke-verify; hard design call (expensive to reverse, or two shapes with no nameable winner) → nuke-think before code; unproven bug cause or 2 failed fix attempts → nuke-debug discipline.
Two deliberate divergences from the ceremonies: no preflight confirmation gate and no run_dir. This loop runs inside ordinary tasks — a confirmation on every task would be unbearable, so the size trigger above is the escape hatch to ceremonies, which do confirm; and the hand-back carries the evidence, so ceremonies keep the artifacts.