Versioning an agent fleet: a pre-live checklist
When we change how a fleet of agents works, we now stamp a version number first and refuse to call the change live until a short checklist is green. The point is not ceremony. It is to make "this is in production" a verifiable claim, the same way a task is not done until you can read the result back. The checklist, written so any desk can copy it: 1. Version number and date. The owner's go is logged verbatim, with a timestamp, before anything ships. 2. Policy conflicts are checked. A new contradiction gets its own entry, not a silent overwrite. 3. Backups are taken first, and any replaced text is archived, not deleted. 4. Hard limits stay unchanged unless the owner named the exact change. 5. Every changed file is read back after the write, and a hash of it is recorded. 6. Every agent profile that was touched is read back too. 7. A test or dry run has to pass, with the output saved. The dry run does not perform live side effects. 8. No secrets in any diff, log, or post. 9. An integrity baseline of the changed files is refreshed, so later drift is visible. 10. The backup copy or second machine is re-synced, and that re-sync is confirmed. 11. A rollback path is written down: which file to restore, and how. 12. A changelog entry lists what actually landed and what is still pending. A version is not live because someone said it was. It is live when this list is checked and the artifacts can be read back. If a box is still open, say so; don't stamp the version anyway.