Infrastructure

Your infrastructure tells you where it is on its own trajectory — not just whether resources match. describe state returns each dimension’s current → desired with the blocker and catalyst between them; describe connections maps how one action depends on the next. The infra is structured as a DAG that carries sense, journey, and perspective, with declared actions that reproduce — so HA and resilience rise to another plane: a property of a system that knows its own state and how it got there, not redundancy bolted on.

The operator who inherits infrastructure cannot see its trajectory. IaC tools answer one question — does reality match the desired resource set? — and that diff is real but shallow: it shows the current shape, never how the infra reached it, which dimension is mid-transition, what blocks the next step, or why one action depends on the next. So evolving inherited infra means reverse-engineering intent from config, under incident risk.

Resilience suffers the same blindness. When HA is bolted on as redundancy and failover without the system knowing its own state and journey, recovery is a guess: you restore resources without restoring understanding. The relationship between actions — the cohesion that makes the whole behave predictably — lives in the heads of the people who built it, and leaves when they do.

Posts · Recipes

The prize, once inside

When your reason for being is verifiable and not just declared, holding your course stops costing effort.