Ticket Printer Ribbon Residual Ledger / 票机色带残像账本线

A discarded thermal ticket-printer ribbon is not another ticket, comp stamp, or receipt. Its used surface is a negative image of the order in which names, aliases, seats, voids, and reissues were printed. When the live database and sponsor recap have already been cleaned, that residual sequence can reveal that a protected patron was displaced, a witness alias was printed, or a ticket row was voided after broadcast reality began treating the cleaned version as true.

This line starts downstream of Receipt Printer Ribbon Priority, Will-Call Envelope Afteruse Receipt, and Source Anonymity Escrow. Those lanes decide which proof is printed, what a pickup object can prove, and who may rely on a hidden source. This line asks a different question: who may recover the erased sequence still present on a spent ribbon, how much may be read, and who must be warned before recovery exposes them?

The residue proves historical print sequence only. It never grants current seat access, sponsor-comp authority, identity consent, archive ownership, memorial authority, or universal broadcast permission.

State-triggered entry

entry_state:
  trigger_kind: state_pressure
  spent_ribbon_roll_visible: true
  residual_print_sequence_recoverable: true
  canonical_record_conflict_visible: true
  voided_or_reissued_ticket_row_visible: true
  protected_subject_or_route_visible_or_explicit_absence: true
  recovery_method_visible: true
  custodian_visible_or_explicit_absence: true
  future_reader_requests_recovery: true
  future_route_consumes_residue_state: true
  player_can_seal_extract_notify_publish_embargo_redact_or_suppress: true
  no_fixed_turn_trigger: true
  no_fixed_day_or_week_trigger: true
  no_raw_ribbon_count_trigger: true
  no_dashboard_or_lens_health_trigger: true

The line does not open because a ribbon exists. It requires a live contradiction and a named reader who wants to consume the physical residue.

Story spine

1. The database says balcony seat B-14 was never issued to protected alias Moth; cold-light inspection of TP-17 shows the alias between an issue and sponsor-block reprint.
2. Unspooling improves legibility but can tear the segment, expose adjacent patrons, or create an uncontrolled derived copy.
3. The player assigns the exact master roll, sequence, conflict row, protected subject, scanner, custodian, reader, and docket to Ticket Printer Ribbon Residue Review.
4. The future route inherits a real limitation: inspector-only extract, named-row-only proof, patron notice, public-only proof, embargo key, certified digest, or suppression recovery.
5. Quiet disposal triggers Suppressed Ticket Printer Ribbon Residue, recording damaged recovery or admitted destruction as a durable scar.

Branch map

| Branch | Relief | Cost | Future effect | |---|---|---| | Seal residue for inspector | preserves sequence integrity and lawful review | exposure log and delay | inspector extract required | | Extract named voided row | restores the erased B-14 contradiction | physical segment is consumed | named row only | | Notify exposed patrons | protects people on adjacent rows | leak risk and delay | patron notice receipts required | | Publish displacement sequence | exposes sponsor rewriting | identity exposure and retaliation | public displacement proof only | | Archive under embargo | preserves the whole sequence | archive debt and key burden | embargo key required | | Redact after certified digest | preserves scoped proof and removes adjacent data | original residue integrity falls | certified digest only | | Suppress residual sequence | buys immediate sponsor quiet | evidence loss and recovery scar | suppressed default pending |

Missability and recovery

The storyline is missed if the spent roll is discarded before the contradiction becomes visible, if full-sequence scanning is treated as costless public proof, or if the protected subject disappears from the docket. It fails if the residue becomes a clean replacement for the current box-office ledger.

Recovery remains possible only through a damaged-segment scan, custodian confession, patron notice queue, inspector-only digest, source-anonymity appeal, or public correction that admits the original sequence can no longer be reconstructed.

Replay expectation

The durable replay must use eight starter cards actually present in hand, fill every exact slot, select seal_residue_for_inspector, and emit ribbon_residue.state.inspector_sealed plus future_route.inspector_extract_required. Focused runtime tests must prove all seven branches, rejection paths, and both suppressed-residue outcomes.