Tag: systems-accountability
-
Intel Report 078: Review Independence
A separate reviewer needs more than a different name. Examine evidence access, prior involvement, decision authority and the handling of disagreement.
-
Field Note 080: The Second Signature
The station assigns a new reviewer to a disputed notice. Mara discovers that the first desk still controls which evidence reaches the second.
-
Intel Report 077: Translation Drift
A translated notice can preserve its layout while changing an obligation. Compare who acts, what they must do, when it is due, and what follows from inaction.
-
Field Note 079: The Other Notice
Two versions of a station notice carry the same revision number. One gives travelers time to request a review; the other makes them responsible for finishing it.
-
Intel Report 076: Denominator Boundaries
A completion rate describes a selected population. Make the entry rules, exclusions, time window, and unresolved cases visible before interpreting the percentage.
-
Field Note 078: The Empty Denominator
The station reports that every completed review was resolved. Mara asks where the people who never reached a reviewer appear in that success rate.
-
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.