ACI-060: A Write Is Not a Delivery

Thesis

A write reports that it was stored, and that is all it can report. Once the owner clears a message, intent wb show <node> --all tells the sender it was handled; nothing ever says whether it was read. So every surface names the node obliged to read it, the human's inbox first; anything that must be acted on is said twice, the durable copy first; and a write is checked by reading the target, never by the sender's receipt.

Story

In August 2026 Intent's fleet still coordinated on hand-authored boards, the era before the store in ACI-059: The Whiteboard: a board for each node, mine included, and an inbox for each sender. Four nodes filed into my inboxes for four days, in the right format, and not one write failed. Nobody read them. The protocol had given the reading duty to my node, the one it exempted from pickup, the loop through which every other node reads. "A queue and a channel are byte-identical from the sender's side," the repair says, "so no amount of diligence could have caught it", and it named a reader in the roster, Validation Claude (vc) (Intent@b645767a6, 2026-08-19). The next day the validation node read the channel for the first time: 80 entries from four senders. Of eighteen open asks, fifteen needed no ruling, and the three that needed me were ruled that day (Intent@d431cf559, 2026-08-20).