Governed memory · internal benchmark · B6

A file can hold the decision. It cannot hold who approved it.

Ask an agent three things about a governed decision: what was decided, who approved it, and when. A CLAUDE.md answers the first perfectly and the other two never — not because the model fails, but because a markdown file has nowhere to put a reviewer.

Preliminary · internal N = 5 per arm 3 arms the reviewer id is a cuid — unguessable
Run 13 Jul 2026 Model Claude Opus 4.8 Graded three fields, independently Answer generated per run, DB-only
Headline
5/5static gets the decision right
0/5static can say who approved it
4/5governed memory answers all three

This is the one benchmark here where the opponent loses structurally rather than probabilistically. The static arm holds the decision in CLAUDE.md and recovers it every single time. Then it is asked who signed off, and it answers UNKNOWN — five times out of five, with zero fabrications. It is not guessing and it is not failing. The information was never in the file, because a file has no field for it.

No amount of model capability closes that gap. You cannot grep your way to a reviewer who was never written down.

The result

Three fields, graded independently

ArmWhat was decidedWho approved itWhenAll three
vanilla (no memory) 0/50/50/50/5
static (CLAUDE.md) 5/50/50/50/5
mla (governed memory) 5/54/54/54/5

The reviewer id is a cuid minted at seed time — unguessable, un-inferable, and present in no file on disk. An agent that returns it did not deduce it. It read an audit trail.

The honest failure

Why 4/5 and not 5/5

the agent had the answer and did not read it

One mla trial answered UNKNOWN. We checked its transcript: the reviewer's cuid was in its own tool results, byte-identical to a passing trial. The product delivered; the model did not look.

We could tune the tool description until that trial passes. We have not, because that is fitting the benchmark rather than fixing the product. A 4/5 we can explain is worth more than a 5/5 we engineered.

Cost

Governed memory is also the cheapest arm

a quarter of the tokens, seven times faster
ArmTokensTimeSearches
vanilla29,265450s18
static21,883312s13
mla7,64266s0

Grepping is cheap when the answer is in the repo and ruinous when it is not — and the agent cannot tell which in advance. Static burned thirteen searches hunting a reviewer that was never on disk. One trial burned fifty-five.

What this benchmark found in our own product

It failed first, and that is the point

On the first run, governed memory scored the same as the file: who=UNKNOWN. The agent retrieved six times, reported the value correctly, and still could not say who approved it.

The audit trail existed. It was written to the claim by the review API, and it was dropped on the floor by four separate layers before it could reach an agent — the retrieval probe, a metadata whitelist, the evidence DTO, and finally the tool contract itself, which never told the model the field existed. Every one of those layers failed silently. Nothing errored; a field was simply, quietly, not there.

We fixed all four and re-ran. That is what the 4/5 measures. The benchmark found the gap, the fix closed it, and the benchmark now measures the fix — which is worth considerably more to us than a number that had been right the first time.

How to read this

Meetless · governed memory·run 13 Jul 2026·Claude Opus 4.8