Governance Without Killing the Joy

Public Posts

• Clean Commits in a Multi-Agent World

  The morning a commit ate my commit. Git stopped being a filing cabinet and became the audit trail, the handoff boundary, and the review checkpoint.

• Governance-as-Code, But for My Own Sanity

  A few YAML files and a risk classifier do real governance work: they make an agent stop before anything irreversible, and turn blocked into a respected verdict.

• The First Thing the Factory Was Allowed to Delete

  Every automation in this factory was additive or read-only, on purpose, until the night it needed to clean up its own branches. The engineering was the easy part. The hard part was deciding what it was allowed to touch.

• The Field Journal's First Interactive Island

  Adding one interactive component to a static site is exactly the kind of change that tends to sprawl. This one went through an ARB review and a security pass before merging, and then became a shared pattern instead of a one-off.

• The Typo That Meant "No Restrictions"

  A privacy gate passed every test I gave it, then routed a machine-local task toward the cloud over a single underscore. The bug was not the typo. The bug was what the gate did when it met a word it didn't know.

• The Engines Now Edit a Photocopy

  Three AI engines are allowed to edit my repositories. As of this week they edit a git worktree copy instead, and the human gate reviews one diff and chooses to apply it. The design work was the edges: escalations, conflicts, and the runs that must not be isolated.

• Cloud Egress Is a Runtime Property

  The same model is reachable three ways from my machine, and each way has a different answer to whether my task's content leaves the building. The gateway stopped asking which vendor an engine belongs to and started asking how it runs.

• The Routing Policy Finally Learned Something

  Every rule in the routing policy started life as a guess with good posture. One rule carried a counter that forced a re-check after five real runs. The counter fired, the evidence came back, and the rule changed in the most boring way possible: not at all.

• Shipping Through the Gate You Wrote About

  Go-live day is when governance gets bypassed. This site's own launch was the test: the agent's safety check flagged its own launch plan RED, the flag was honoured even though it was a false positive, and a human ran the apply.

• Honest Evals as Culture

  My eval log is a list of recorded disappointments: a fix that didn't move the number, a review panel wrongly flagging clean code three times out of four. Writing those down felt like self-sabotage. It's the only reason the eventual win means anything.

• Who Designed the Lock?

  Two labs asked to trust cryptography that didn't exist yet, in the same week. Both times the answer was the same: the control's owner designs the lock, shape-checking is not signing, and a decision to accept a design is not the deliverable.

• The Exception That Sat in a Drawer

  Two governance proposals were drafted, never sent, and reviewed three days later. In those three days the docs they cited had been restructured and the systems they assumed had moved. Reviewing an exception is not re-reading its words.

Draft Queue

No draft placeholders assigned to this series yet.