Disciplining the Coding Agent
Four posts on the same problem from four angles. If you did not write the code and cannot read all of it, what is left to trust?
The answer each post converges on is: not the code, and not the model’s account of itself, but the environment — a contract the agent cannot renegotiate, a decision rule that was allowed to say no, an answer key sealed before the first line was written, and a standing assumption that every one of those guards is dead until something has tried to kill it.
The origin of the whole discipline is a project that had none of it: The Ablation That Beat the Agent, where holding both pens — designing the benchmark and the thing being benchmarked — produced a headline number that did not survive a fair re-run.
Keeping the Coding Agent on the Straight and Narrow
A companion to the PKM Phase 1 post. The foundation was built by two AIs — Claude.ai for design, Claude Code for implementation — with a spec as the contract between them. Ten SPEC revisions in four days, and what the …
The Gate That Said No
Whether to adopt a tool you built is itself a decision under uncertainty, so it deserves a decision rule, not a leaderboard. I built a pre-committed, frozen-blind adoption gate over a posterior on the utility difference …
Signed Before the Code Existed
The frozen-oracle protocol under which a language was built by a coding agent: the acceptance tests were authored and signed before any code, then handed off compiling-but-failing-red, so the agent could not fit the …
Fifteen Ways Past My Own Gate
A fresh agent session was pointed at a governance repo with one question: can the repo's own rules be broken while the verification gate stays green? It found fifteen ways, three of them without touching anything the …