pastilhasandClaude Opus 5
c0788d15c0
Roles become a table and localization phase 0 lands. Both groundwork; nothing in the UI changes and nothing reads the new table yet. Schema change, additive only — the roles table is new and no constraint is added to an existing column, so it cannot fail on existing data. postdb:push seeds it. No dependency change; the two lockfile lines are the local i18n workspace being declared as a dependency of officerdev. The plan names the check that matters: four rows in roles, per host, by query — db:push can fail and exit 0. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
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.
A release is a tag, deploy/<version>, and nothing else triggers a deploy — not a commit message,
not a branch. A tag cannot be written into prose by accident, which a code word can and which every
document about deploying does.
What marks a release deployed is LOCAL: $OFFICER_ROOT/data/deploys/<version>.done. Not the report.
If the lock were the pushed report, a failed push would mean the release looked undeployed and the next
tick would roll it out again — and pushes here fail for unrelated reasons. So the report is an artefact,
valuable and not load-bearing.
See prompts/deploy-commander.md.