You Were Never Declaring State. You Were Observing By Hand.
This title could be clearer and more informative.Try out Clickbait Shieldfor free (5 uses left this month).
Traditional infrastructure-as-code tools like Terraform, Chef, and Puppet required humans to manually observe systems and encode those observations into declaration files — because the tools themselves couldn't observe reality. This was never true 'desired state declaration'; it was humans doing the observation work on behalf of blind agents. Now that agents can observe live systems directly (capturing typed, versioned, schema-validated snapshots), the architect's role shifts from crafting HCL/YAML declarations to designing data schemas and defining boundaries between observation and action. Declarations still matter for provisioning new resources, compliance baselines, and rollback targets — but they live in method logic and schema constraints rather than static files that drift from reality. Idempotency also moves up the stack: instead of each resource operation being individually idempotent, the workflow queries current state and decides whether to act at all.
