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.

8 parts · 59 min total · Sep 2026 – Oct 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.
  4. Part 04 8 min Compile the Policy A risk standard today is a document in a shared folder with the version typed into the footer, and the enterprise calls that governance. Walk it through the software chain instead: authored from source, rendered on build, tested as policy-as-code in a throwaway sandbox, versioned immutably in a registry, promoted through sign-off gates into the system it governs. None of it is new. It is the pipeline software has run for years, pointed at the document.
  5. Part 05 6 min Version Control for Data Git is the source of truth until the artifact is a terabyte of unstructured content or a billion-row table, and then it isn't. The principle survives the medium: text lives in git, unstructured content lives in a lineage-tracked lake, structured data lives in a lakehouse whose table-format time travel is literally version control for data. Same invariant, three substrates, chosen by the shape of the thing.
  6. Part 06 6 min Grounding Is a Memory Problem Everything-as-code builds the semantic layer of context, the governed meaning of the business. It does not build the other half. Grounding an AI turns out to be a memory problem, and the answer has always been the second brain, at every scale from a person's notes to an enterprise knowledge base. Here is the practical shape of memory at the individual, team, line-of-business, and enterprise level, and why every framework keeps rediscovering what neuroscience still can't fully explain.
  7. Part 07 6 min One Word Moves the Control The governed lifecycle has one weak joint, and it is the review gate. Code review works partly because the machine runs the test and tells you, objectively, that something broke. For prose where meaning is the payload, one changed word can move a control, and no test catches it. This is where everything-as-code stops being a mechanical win and starts demanding human judgment, and why automating a broken review just scales the mistake.
  8. Part 08 6 min IT Is the Blueprint Every post in this series built one pillar of a larger machine. The AI-first enterprise is an operating system with four of them: Context, Prompt, Model, and Tools, each solved from the individual up to the enterprise. The reason IT gets to go first is that IT already runs the blueprint. The governed lifecycle isn't an aspiration in software, it's Tuesday. This is the case that IT is the reference implementation the rest of the business copies, and the honest account of what it still can't do for you.