pastilhasandClaude Opus 5
e0d80fd3ae
Speech-to-text leaves the platform for the transcribe plugin. No schema, no dependencies — a removal plus a catalogue entry. The plan says explicitly not to install the plugin during the rollout. Which hosts get transcription is the owner's call, made per host, and an install now grants access to every role. Removing and installing in one unattended pass would decide that for five machines at once. Nothing is lost anywhere: no host had an STT endpoint configured, so the routes this removes have never answered on any of them. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Officer-Session: 656f5c85-e49a-4f1f-b9f3-042a04b4d043
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.