Infrastructure facts don't belong in service code
A fact about infrastructure stored in service code is a second source of truth, and two copies drift. Generate the view from the source instead.
Migrate one variable at a time, or you won't know what broke
Hold every variable but one and a failure has one suspect. Bundle two and the suspects grow like the subsets: three places to look, then seven.
The irreversible decisions go first
Most risks are prices you can pay. The one with no affordable way back is different. Settle those decisions first, while you still have a choice.
Automate what your attention can't change
The work you watch out of habit should run without you. Automation's job: make that true and hand back the attention the watching was quietly costing.
A green dashboard is a claim about components
A green board means the components are up. Whether a user can finish the task is a question the system was never built to answer about itself.
Pressure code is the debt you don't want to remove
Refactoring pressure code raises its perceived value without paying down the debt. A structural diagnostic for technical debt prioritization.
Reasoning the team can't rerun leaves with the engineer
Team capability transfer holds only when the team can rerun the reasoning themselves. What lives only in the engineer's head leaves with them.
The business model is the ceiling
When the business model is the constraint, execution discipline raises the ceiling without breaking it. A diagnostic for model constraints.
Redundancy ends where the dependency tree converges
Two backups, two providers, two regions. None of it is redundancy if components share a dependency anyone forgot to map. The failure proves which.
Faster reconciliation doesn't fix drift
Configuration management asks what each value should be. Governance asks whether anyone decided. Drift accumulates in the gap between the two.
Validation separates self-healing from a keep-alive script
Keep-alive automation checks whether the script ran. Self-healing checks whether the system recovered.
Procedural risk shrinks; structural risk doesn't
Some risks shrink with effort. Others absorb the same investment and don't move. One question tells them apart during evaluation.