field notes KEEL

permanent, not staging

For a long time the honest name for this estate was staging, and the word licensed sloppiness: try it, leave it running, fix it later. Calling it permanent changed nothing about the hardware and a great deal about the decisions. Permanent means you keep a rollback. It means you do not practise on it. It means you carry a version you would rather have left, because the upgrade window that would fix it is a risk you have not chosen yet. It means taking the boring path on a day when the interesting path would have been quicker.

The second half of that posture is documentary. If the place is permanent, what is written about it has to be true, so the writing splits into two classes: what should be true, and what is true. The gap between them is the real work queue, and it never closes. In one review the design said the secret store reopened itself after a restart; the check said it did not, because the keys were still held by a person and the automation had never been armed.

Nothing had failed. The document had simply been ahead of the machine, which is the ordinary condition and the one worth naming out loud.

What this proves is that a small estate can be run to a standard larger operations shops struggle to state plainly, provided someone is willing to write the same thing twice and keep the difference visible.

drawn from: posture and as-built review commits

Every note carries a codename and one idea. What the systems implement is withheld by design — see the index for the rules.