Tag: institutional-design
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
Intel Report 071: Priority as Policy
Queue order allocates scarce attention. Examine the tradeoffs behind arrival order, urgency, short-case preference, and discretionary priority.