og.rsts.dev

Series

Everything as Code

Software spent decades earning a governed lifecycle for one artifact: source code. This series generalizes that hard-won discipline to every versionable deliverable in the enterprise — infrastructure, architecture, policy, GRC, standards, procedures — around a versioned source of truth, and asks how far the pattern extends toward an AI-first Enterprise OS.

3 parts · 27 min total · Sep 2026

An ongoing series on a single recognition: the governed lifecycle software earned the hard way, source of truth to change ticket to reviewed merge to gated pipeline, was only ever applied to one class of enterprise deliverable. AI made running that loop cheap enough to point at all of them. The arc walks the dominoes (infrastructure, architecture, policy, governance and risk), the source-of-truth substrate that scales from git to the lakehouse, the memory layer that grounds an AI, and the four-pillar Enterprise OS that IT is already the blueprint for.

  1. Part 01 12 min I Already Solved This Every enterprise governance problem I look at lately triggers the same déjà vu. Across 35 years writing software I watched one class of deliverable earn a governed lifecycle the hard way, through Agile, TDD, DevOps, GitOps: source of truth, change ticket, review before merge, gated pipeline. Every other enterprise artifact is still sitting where code was before those inflections. AI is what finally makes running that loop cheap enough to point at all of them, and the center of the AI-first enterprise is a source of truth you can version.
  2. Part 02 8 min The Domino That Already Fell Infrastructure was the first enterprise deliverable to leave the click-console for a governed lifecycle, and it worked. Declared desired state in git, a reconciler that drives reality toward it, drift detection, rollback by revert. This is the domino that proves the pattern. The rest of the series is asking why we stopped at infrastructure.
  3. Part 03 7 min The Architecture Belongs in the Repo Most enterprises review architecture once a year in a slide deck nobody can diff. Put the model in the repo instead, as ADRs and C4 and contracts, and architecture gets what code has: a change ticket, a review that gates the merge, a test that fails when a decision violates a standard. Governance stops being a meeting and starts being a pull request.
Start with Part 1 →