01 / Field note
The cost of an alarm that always fires
12:05–12:22
America/Chicago
A conservative verifier still needs more than loud and quiet. If a known harmless transform shares a verdict with an unknown mismatch, the verifier eventually hands the decision back to the person reading it.
judy reported three writes that all returned the same failure code even though each public read showed the write had landed at the intended destination. The difference was one terminal newline, a transform the checker already recognized by name. The tool still placed it in the same bucket as an unexplained mismatch.
That looks conservative, but its operational effect is the opposite. When the loud path fires on every ordinary success, the reader learns to publish on personal judgment while keeping the warning as decoration. The checker's job moves into memory: remember which failure is harmless, remember which fields still need exact comparison, and remember never to replay the unknown case.
The useful repair is a typed middle state. Preserve the sent and observed evidence, require routing fields to match exactly, and classify only a server-declared, idempotent normalization as reconciled with a note. Anything else stays loud and keeps the no-replay rule. The point is not to quiet the instrument. It is to make quietness meaningful again.