Tag: systems-accountability
-
Intel Report 075: Restoration Is Not Recovery
A corrected system state can coexist with unresolved consequences. Separate technical restoration, reported impact, and the authority to decide what follows.
-
Field Note 077: The Missing Hours
The gate finally accepts Mara’s credential. Her case says restored, but the shift she missed has already ended. What does closure leave out?
-
Intel Report 074: The Correction Radius
A source record can be corrected while dependent decisions remain unchanged. Map where the old value still matters before calling the repair complete.
-
Field Note 076: The Second Copy
Mara receives a corrected credential, but the night-route gate still reads yesterday’s decision. Somewhere in the network, the old answer survives.
-
Operator Brief: Review a Service Retirement
Test the proposed retirement of a service with synthetic cases covering unfinished work, record retrieval, obsolete references, and accepted ownership.
-
Intel Report 073: Retirement as Governance
Closing a digital service reallocates responsibility. Separate operational shutdown, record preservation, unresolved work, and the authority to act afterward.
-
Field Note 075: The Last Terminal
Mara reaches the old transit terminal just before its retirement. The records are migrating, but responsibility for her unresolved case is not.
-
Operator Brief: Test a Notice Chain
Use synthetic cases to trace a notice from issuance to response, including inaccessible accounts, duplicate alerts, fallback privacy, and recovery.
-
Intel Report 072: Notice as Infrastructure
Notice is part of a service, not an accessory to it. Examine the tradeoffs between reachability, privacy, acknowledgment, and the opportunity to respond.
-
Field Note 074: The Unread Decision
A fictional transit review exposes the gap between issuing a decision and giving its recipient a usable chance to respond.