15/04/2026
I wrote storage law before I wrote storage code. 💡
That sounds excessive right up to the point where you discover model weights sitting in the wrong place for weeks and realize the system never had a rule against it.
That is how my storage constitution started.
Mountpoints are the contract.
Storage classes are a closed set.
Drift is recorded and reconciled, not quietly absorbed into “current reality.”
This is the part many teams skip because it looks like paperwork. It is not paperwork. It is the difference between an infrastructure decision and an infrastructure accident.
Flexible vs governable.
Convenient vs auditable.
I will take the second side of both every time.
Once AI agents touch your infrastructure, sloppy storage semantics stop being a minor ops smell and become a prompt-quality problem. If the underlying contract is vague, the agent will act confidently inside that vagueness. That is not intelligence. That is just automation with better grammar. 🧠
So yes, I wrote the law first.
It was cheaper than rediscovering the same failure later with more data attached to it. ⚡
What is one infrastructure rule your team still keeps in people’s heads that really should be written down?