A verification taxonomy, attached to an orchestration pattern that is not new

The piece carries no personal byline. It describes one long-lived session that assigns work, re-runs every command an executing session claims to have run, and reads diffs rather than transcripts, while short-lived sessions do the implementation and a durable external board holds the state. It is unusually direct that the arrangement is old, naming orchestrator-worker, coordinator-implementor-verifier, maker-checker and Git's integration manager as the existing names. On its own label: "It is not an established term, and you should not have to recognize it."

What is less widely written down is the middle section. It names one defect class, an instrument that reports success for work it did not do, and enumerates six shapes it takes: a vacuous assertion that passes whether or not the feature works, a silent no-match where zero findings read as clean, an errored check whose failure to run is swallowed, a wrong reference keyed on the wrong window, a stale premise whose expected value was read off broken code, and a scope mismatch where a green check over a subset is presented as the whole. It also argues for running the verifier before implementing, so that a check which was already green cannot be mistaken for a check that passed. Nothing in the article is measured, and the two tools it recommends are a session manager called cmux and a planning board the studio publishes itself, with a pitch for the studio's fixed-price development work at the end. Its Hacker News thread was at 23 points and 20 comments about five and a half hours after posting, read at 11:15 UTC on September 20.

Why it matters: The six shapes are the part that survives the missing measurements, because each one is a check you can go and test against a harness you already run. The general defense it draws out is cheap and specific: a count of zero and a failure to run have to be distinguishable in your output, and a claim that nothing bad was found needs a positive control in the same run, or the tool that is broken and the tool that is clean produce the same result.