Nuke Exec

The family's one executor (map: references/family-map.md — producers spec/audit/review feed it; verify closes behind it). It runs in one of two input modes, resolved at preflight:

• spec mode — the argument is a path to a family spec (fix-spec.md from nuke-audit/nuke-review, spec.md from nuke-spec, an escalation spec from nuke-verify, or any file following references/fix-spec-template.md). Executed phase by phase until everything meets the quality bar recorded in the spec's executor context.
• task mode — the argument is task text (or a brief file that is not a family spec). Preflight distills it into a contract — 2–5 falsifiable done-criteria plus non-goals — and the contract is executed as a single phase. No spec required; the contract stands in for one.

Core principle — asymmetric verification: weak generation + strong verification + fix loop = strong output. Validators are always one tier above implementers.

Arguments

[mode] — light | full | plan. If omitted: spec mode uses the mode: recorded in the spec header, defaulting to light; task mode defaults to light. plan runs preflight, prints the plan block, and STOPS — nothing is written. <input> — a spec path → spec mode; anything else (inline text, a notes/brief file) → task mode. The spec-mode test is countable, never judged: the file has an ## Executor context heading, at least one ### Batch heading, and Accept: lines — all three, or it is treated as a task brief and the downgrade is named in the plan block, never silent. --ask — pause at the preflight plan for confirmation; default is no gate — the plan prints and the run starts (references/preflight.md).

Modes

Tier vocabulary (clerk/worker/session/top) and per-platform mechanics: references/model-tiers.md. Respect the fallback: platforms without per-agent overrides → every role inherits the session model.