Tag: systems-accountability
-
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.
-
Operator Brief: Audit a Queue Discipline
Use a small synthetic case set to test queue admission, ordering, aging safeguards, retries, and closure without disrupting a live service.
-
Intel Report 071: Priority as Policy
Queue order allocates scarce attention. Examine the tradeoffs behind arrival order, urgency, short-case preference, and discretionary priority.
-
Field Note 073: The Invisible Queue
A submitted request is not necessarily a queued request. Trace the hidden boundary between receipt, admission, assignment, and service.
-
Field Note 072: Burden Shifting
Burden shifting occurs when a system transfers the work of proving, reconciling, monitoring, and correcting institutional state onto the person affected by it.