v1
The as-code family

Process as Code.

A process written in a wiki describes; a process written as automation executes. Between the two sits every procedure that was documented once and drifted quietly ever since.

The wiki gap: described processes drift.

Most organizations document their processes and then operate from memory. The documented version and the operated version diverge, nobody notices because nothing checks, and the divergence surfaces during an incident or an audit.

Software delivery closed this gap by making the pipeline the process. Nobody consults a wiki page to remember how to release; the release process is a workflow, and running it is following it. The process cannot drift from its documentation because the automation is the documentation.

The PMO’s processes can run.

The recurring procedures of portfolio governance turn out to be automatable in exactly the same way. Each of these operates today in the reference deployments:

Document review
Every changed document is validated on the pull request, and the whole traceability graph is checked before merge.
Scope intake
When approved scope merges in the governance repo, the delivery boards are scaffolded within seconds, routed per project.
Progress roll-up
When the last story under a feature closes, the feature closes itself, with the record on the issue.
Drift repair
Reconciliation runs keep boards converged with documents, and a sentinel sweeps for stalled automation and opens findings on itself.

What should stay written.

Judgment-heavy procedures do not belong in a workflow file: how to run a steering conversation, when to escalate, what to do in a situation nobody predicted. The honest test is drift: if the written procedure and reality can diverge silently, encode the procedure; if a person must weigh the situation each time, write it down and govern the writing.

The halfway house
Procedures that need human hands can still live under the gate: a runbook as a governed document, with numbered steps, changed only by pull request. The steps stay human; the change control is code.