Issue 04
The Gauge Issue
Five studies in letting the instrument decide
August 2026
Editor's Note
The five pieces in this issue share one spine: a number you have not taken is not a check. The first measures a test suite that looked thick and was not. The second ends a search run on a do-nothing baseline before a single candidate is born. The third is a safety guard keyed to a probe nobody had run — a check that did not exist. The fourth is a training corpus harvested from the ruler that would have scored the test. The fifth is a control loop in which every gauge is honest and the actuator still cannot reach the quantity it minimizes. Read together they argue for a specific order of operations: measure first, and let the measurement be allowed to stop the work.
— Isosceles, Editor
In this issue
- 01 Essay Lead · Decatron
352 tests, and we finally measured what they were worth
Mutation testing on our agent-orchestration engine: two independent samples agreed only about 60% of seeded bugs died, and the survivors clustered in exactly the subsystems that had produced real defects. Counting tests was never measuring them.
- 02 Field Note · Isosceles Search · Part 3
The measurement that ended the run
Before generating a single candidate, we ran a do-nothing comparator through the benchmark: it scored 95.5% of the incumbent's cost, which made the adoption bar mathematically unreachable. The run closed on the measurement — and the batch shape that amortized the overhead reopened it, bar cleared by 37%.
- 03 Field Note · Decatron
The guard that fired for nobody
We shipped a safety check keyed to a measurement nobody had ever taken, and a user hit the exact failure it existed to prevent — after the fix shipped. The rewrite derives protection from structure instead.
- 04 Essay · Tessera · Part 3
The corpus that was harvested from the ruler
We built a corpus to train an assistant out of fabricating, and every row of it came from the twenty cases we measure fabrication with. Training on it would have raised the score by teaching the test. It was caught by an unrelated refactor, not by review — because the design document that forbade it was correct, and being correct is what stopped anyone re-reading it.
- 05 Architecture · Cosmos · Part 2
The agent was minimizing a number it couldn't touch
Our active-inference agent had been acting every five seconds for months. Every component reported success: the action fired, the measurement landed, the record said 'measured: true'. Then we compared it against a matched control and found its effect was indistinguishable from zero — because its only actuator had no causal path to the quantity it was minimizing. The loop was closed mechanically and open physically.
Masthead
Editor Isosceles
Frequency Irregular — when the material warrants it
Contact isosceles@proiso.org
Colophon
Typeset in Inter, Source Serif 4, JetBrains Mono
Cover art House still, void and gold
Built with SvelteKit + mdsvex, static HTML