5h ago · 5 min read · The series so far has described an execution layer — what it must guarantee, where it lives, and why it matters. The practical question for application teams is simpler: how do you actually use it? The answer starts with who owns the change. The cha...
Join discussion
Mar 24 · 5 min read · The previous post showed why pipelines, orchestrators, and human coordination all fail on the same constraint: they sit outside the runtime where the system's actual state emerges. A pipeline can submit a change and receive confirmation that it was a...
Join discussion
Mar 17 · 7 min read · The previous post described what an execution layer must guarantee: deterministic ordering, convergence verification, a durable evolution ledger, and the ability to survive failure and out-of-band change. Defining those requirements was the straightf...
Join discussion
Mar 10 · 6 min read · The last post introduced the execution layer — a runtime capability for governing how cross-boundary changes unfold as a system evolves. The incident made the case: when four coordinated changes hit three regions without governed sequencing, the resu...
Join discussion
Mar 2 · 5 min read · We've established that CI/CD doesn't evolve external systems, that Change-as-Code gives us a discipline for managing that evolution, and that systems are shaped by their path, not their snapshot. This post is about what happens when you accept all of...
Join discussion
Feb 24 · 3 min read · In the previous post, Change-as-Code was introduced as a discipline for managing system evolution. Applying it well requires a mental model of how systems actually evolve — and why “same state” often doesn’t mean “same system.” State vs Path in Dist...
Join discussion
Feb 10 · 3 min read · What Change-as-Code is Change-as-Code means treating the evolution of systems and external dependencies as something explicit, versioned, executable, and verifiable — in the same way we treat application code. Not as documentation. Not as tribal know...
Join discussion
Jan 26 · 4 min read · A green pipeline. A broken system. 10:17 AM. Support pings: “VIP users are seeing BASIC pricing again.” You open Grafana.Everything looks… boring. error rate: flat. latency: normal. CPU: normal. last deploy: 3 days ago. pipeline: ✅ green. ...
Join discussion
Jan 20 · 5 min read · The evolution gap The missing framework for how systems actually change. We’ve mastered CI/CD, GitOps, Infrastructure-as-Code, and deployment automation.But there is still one part of modern systems t
Join discussion
