Field notes

Notes from the merge gate.

Research, observations, and design partner conversations
Operations · Leadership

Production Resilience Is the Thing You Stopped Buying When You Bought Velocity

The velocity dashboard looks great. The on-call rotation is on fire. These two things are now happening at the same time in roughly every enterprise that has adopted autonomous coding agents at scale.

Read
Architecture · Strategy

When the Agent Has an OS and Production Has No Gate, the Gate Is the Product

RTX Spark and Bedrock AgentCore ship substrate governance. The harder problem is what governs the artifact after it crosses a boundary. Every substrate converges at one universal layer: the merge gate you own.

Read
Research · Risk

The Verification Debt Nobody Put on the Balance Sheet

AI agents now initiate 96% of the work in collaborator-driven repos. Almost none of it is governed by anything other than a human glancing at a diff. The gap between those two numbers is where risk quietly accumulates.

Read
Research

The Agency-Governance Split Is Real, and the Audit Trail Wasn't Designed for It

Agentic pull requests now constitute a substantial share of code authoring. Terminal merge approval remains almost exclusively human. The audit infrastructure most enterprises rely on was built before that split existed.

Read
Architecture

Two Halves of a Merge Gate, and the Layer That Sits On Top

Credo AI argues for policy-as-code upstream. Qodo argues for diff-aware analysis at the gate. Both are right. Neither captures the human governance decision itself, and that layer needs its own infrastructure.

Read
Strategy

Shift Left, Shift Right, and the Governance Layer Between Them

AI compressed both ends of the software lifecycle. The governance layer that holds the middle has not caught up. What that means for engineering, product, marketing, sales, and support in a SaaS company, and why the TCO case favours planning it in now.

Read