# `deploy/`

One file per release, and one report per release.

```
deploy/
├── 2026.08.21.01.md         the plan — what to run, in order, on which hosts
└── 2026.08.21.01.report.md  what actually happened, written by the commander
```

The plan is written by hand before the release commit. The report is written by the deploy commander
afterwards and pushed back here.

**The report's presence is what marks a release deployed.** That is the whole idempotence mechanism: a
watcher that restarts checks for the report before acting, so it cannot roll the same release out twice.

See `prompts/deploy-commander.md`.