command-decklisted

# /foundry:command-deck Hand it one programme and walk away. The deck is a **recurring scheduled prompt that re-wakes this session** — dispatch, verify, land, report — and escalates only what genuinely needs the operator's hands. ``` /foundry:command-deck <programme-id> arm the watcher (the default) /foundry:command-deck status [<programme>] what is true right now + is a watcher recorded /foundry:command-deck stop <programme> cancel the job and forget the record /foundry:command-deck restart <programme> cancel, re-render the prompt, re-arm /foundry:command-deck tick <programme> run ONE tick now, arm nothing /foundry:command-deck prompt <programme> print the rendered tick prompt, arm nothing /foundry:command-deck list every watcher recorded in this workspace ``` ## The shape that works — and the two that do not Measured over the runs where this pattern actually drove releases to completion: - **The deck is THIS session, woken by a recurring cron job.** It therefore holds the operator's authority by construction and never has to be handed it. - **It is never a subagent.** Packaging operator authority into a brief and delegating it to an `Agent` is the exact shape a permission classifier is built to refuse — and refusing it is correct. Subagents are dispatched *by* a tick, as narrow implementers and reviewers with explicit "do not commit / do not authorize / do not merge" briefs. - **It is never a background shel