Tag: systems-accountability
-
Intel Report 083: Current Is Not Necessarily Applicable
Reviewing a decision requires more than finding the newest instructions. Separate version identity, effective dates, scope and the procedure for reconsideration.
-
Field Note 085: The Rule in Force
The station finally traces its evidence. Then Mara notices that the rule offered to explain the restriction did not exist when the decision was made.
-
Intel Report 082: Agreement Without Independence
Several records can agree because they share an origin. Evaluate how a claim was obtained before treating repeated references as corroboration.
-
Field Note 084: The Three Witnesses
Three station records appear to confirm the same journey. Mara discovers that all three inherited a single unfinished claim.
-
Intel Report 081: A Summary Is Not Its Source
A summary can repeat accurate fragments while changing what they support. Keep decisive qualifications, source references and review limits visible.
-
Field Note 083: The Missing Column
The attachment reaches a reviewer. Its summary preserves every destination but loses the column that says which journeys were cancelled.
-
Intel Report 080: Intake Is Not Evaluation
Receiving a form, accepting an attachment and assessing its contents are different events. Keep those distinctions visible in receipts and review summaries.
-
Field Note 082: The Unopened Attachment
A traveler tries to submit a correction. The station rejects the attachment, then tells the reviewer that no supporting evidence was supplied.
-
Intel Report 079: A Match Is Not an Identity
Record matching proposes relationships. Keep candidate links, confirmed decisions and downstream consequences distinguishable, especially when evidence is incomplete.
-
Field Note 081: The Shared Name
A station search returns two histories beneath one name. Mara watches a possible match become a restriction before anyone asks whether the records belong together.