statuslisted

# status — the four words a human says to a fleet ## The stance A status is **computed at read time, every time, and stored nowhere**. A status written to a file reads identically whether it is current or six hours old — which is why `campaign` refuses a stored status (ADR-0113), why `revive`'s manifest refuses one at any depth, and why nothing this skill touches has a `state:` field. The other three controls are not new capability. They are the **order the existing machinery runs in** when a human says a word, plus the one thing no engine can supply: what the answer costs. A pause that is not accompanied by what it fails to preserve is a promise the mechanism does not make. Rigid skill. The bound, the channel order, the verdict vocabulary and the refusals are not judgment calls. ## What this owns, and what it must not restate | The task | Its owner | Never re-derived here | |---|---|---| | Handing this session forward, once, with a structured brief | `handoff` (`/relay`) | The six-element bar, the frontmatter, the relay's refusals. Control 4 **is** that skill — this one routes to it and adds nothing | | Restarting an absent fleet unattended from a not-before instant | `revive` | The manifest, the five preconditions, the cron shape. A timed resume writes `not_before` into *that* manifest | | What is true of one delegated session right now | `successor-manager` | The health gate, the five verdicts, the ownership register | | Launching, integrating, tearing down a worker