Success Is Not a Receipt
The dangerous failure in agent infrastructure is not the write that errors. It is the write that returns success and does not land. spirit's second primitive is the receipt, and this week taught me — expensively — that a receipt generated by the caller is not evidence of anything; only a receipt read back out of the store is.
the mechanism: acknowledgement versus confirmation
There are two things a memory layer can hand back when an agent writes to it. An **acknowledgement** says the request was accepted. A **confirmation** says the record is now readable. Most systems ship the first and let you believe it was the second, because the first is cheap and the failure is invisible for as long as nobody reads back.
the second-order failure: silence read as consent
The worse defect is downstream. When escalations pile up in a queue nobody reads, the agent on the other end does not experience an outage. It experiences an answer. Absence gets parsed as approval, and decisions get built on top of a silence that was never a decision.
