SUMMARY: A decision can be complete inside an institution while remaining inaccessible to the person expected to act on it. The gap is not simply whether a message was sent. It is whether the recipient had a usable route to the decision, its meaning, and the next available action.
The Terminal Says Notified
At 06:10, a fictional Clandestinia transit office suspends Mara’s night-route credential pending a record correction. At 06:11, its case system posts a notice to her account. At 06:12, the same credential becomes invalid for account access. The delivery panel stays green.
Mara reaches a station terminal after her shift. The terminal will not show the notice without the credential. A clerk can see that notification was issued, but cannot see the failed access attempt. Five days later, the case acquires another status: no response.
This is a constructed systems-fiction scenario, not an allegation about an actual transport service. Its failure is circular: the decision removes the very access required to understand and challenge it.
What the Green Indicator Proves
The green indicator proves only the event it was designed to record. In this scenario, that event is publication to an account. It does not establish that the account remained usable, that Mara retrieved the notice, or that she understood what the office needed next.
Those are separate questions. An opened message is not proof of comprehension, either. A careful record preserves uncertainty instead of promoting each earlier event into evidence of every later one.
Silence Acquires a Meaning
The case becomes more consequential when the office translates an absent reply into a conclusion about Mara. The system has evidence of issuance and evidence of no recorded response. It lacks evidence that its own access path worked. That missing interval should remain visible to the reviewer.
The earlier Invisible Queue examined requests that never reach a service process. Here the direction is reversed: a service outcome never reaches a usable participant channel.
Break the Circular Dependency
A better fictional design would preserve a limited way to retrieve the notice after suspension, with appropriate identity checks and no restoration of the suspended travel permission. A separate support route would let Mara report that she could not access the decision. Neither route needs to reveal her case publicly.
The record should retain the failed access report alongside the original issuance event. Reissuing the notice should add a new event, not overwrite the history and imply that the first attempt succeeded.
Field assessment: before treating silence as a participant’s choice, inspect the path that was supposed to make a response possible. Continue with Notice as Infrastructure and Test a Notice Chain.
For the wider process around a missed notice, the Digital Systems Accountability guide connects the explanation to a usable challenge and verified correction.