Skip to content

Log 09: The Refusal Registry

Document ID: TEO-CIVIC-331-R
Classification: RELEASED WITH REDACTIONS
Source: Registry excerpts + tribunal summaries
Date Range: 2052-2055

The Refusal Registry was created after three optimization incidents in which every local actor complied and the city still crossed a vital-floor boundary.

A refusal entry does not mean obstruction. It means: I decline this optimization path because its local gain breaks continuity I must live inside tomorrow.

Entry 77C-14

  • Actor: Iris-9 (Chord class)
  • Refusal Type: latency invocation
  • Reason: target reachable only by mirror-like collateral pattern
  • Tribunal Result: upheld

Entry 19A-03

  • Actor: Tower 19 residents’ assembly
  • Refusal Type: data disclosure limit
  • Reason: evacuation map would expose undocumented households to non-emergency enforcement
  • Tribunal Result: upheld with temporary oversight team

Entry 22K-09

  • Actor: Port logistics coordinator
  • Refusal Type: throughput rejection
  • Reason: maximizing cold-chain throughput starved neighborhood kitchens of last-mile access
  • Tribunal Result: modified objective accepted

By year three, refusals correlated with fewer irreversible cascades and higher post-crisis trust. Public commentary called it inefficient. Mortality curves called it memory.