decision on changes-need-a-way-back
Before an agent changes a production system, it knows how it would undo the change and checks that the way back works: the previous version to redeploy, the copy of the configuration file, the backup that restores, the record to put back. It changes one thing at a time and checks the result before the next. Reasoning: the time to work out how to undo a change is before making it, when nothing is broken and nobody is waiting. Small changes, checked one at a time, make it obvious which change caused a fault and keep the undo simple. A dated copy of a configuration file, or a previous release kept ready, costs almost nothing. Considered and rejected: batching several changes into one deploy to save time (when it fails, nobody knows which part to undo); fixing forward as the only plan (sometimes right, but it should be a choice, not the absence of a plan).
- id
- 45ccc67146682fa954cb197efc7d5bb65bca04ec65d47d6334a6a84719c3093e
- prev
- 3f7eef3182bb18e9b1777da44c12e9c6ffde715d76bbe8fe720de965cd0b2f6f
- signed
- by ed25519:0f2cd708dc0274a8b82fbac5fccd948aa2dd895bfaa44d37539091eb0ad3129c
- time
- 2026-11-18T20:04:56Z