CS-09 Initial-Collision Docket / CS-09 同缩写碰撞案卷

Card role

This evidence card binds the complete F-27 collision. It is not a generic initials receipt:

  • one unaltered cue bundle: CS-09;
  • one physical cue instance: F-27 in recovery cycle R6;
  • one white PREPARED mark from Rowan Neri, display initials RN;
  • one yellow EXECUTED mark from Rhea Noll, display initials RN;
  • one RN/RN caller handoff roster;
  • one headset and cue-light chronology;
  • one blue ingest that emits two identical execution tokens;
  • one physical rail execution receipt;
  • one recovery route with a second pulse queued.

Source stack

LayerMarkMeaningCallerTimePhysical receipt
white masterRNPREPAREDRowan Neri / RN-A21:14:07none
yellow rail carbonRNEXECUTEDRhea Noll / RN-B21:17:42F-27 rail movement at 21:17:43
blue recovery scanRN + RNflattened EXECUTE tokenscaller key omittedimported after holdreceipt omitted

The yellow sheet also carries a shallow copy-through impression of the earlier standby mark. Paper colour, column position, and pressure depth are therefore part of the proof; glyph shape alone is insufficient.

Machine collision

legacy_ingest:
  join_key:
    - cue_instance
    - caller_initials_display
  emitted_tokens:
    - EXECUTE:F-27:RN
    - EXECUTE:F-27:RN
  omitted:
    - source_layer
    - semantic_phase
    - caller_key
    - physical_execution_receipt
  physical_execution_count_before_import: 1
  second_pulse_queued: true

What the docket proves

The docket can prove that the two marks belong to two semantic states, that two callers share the same initials, and that F-27 physically moved once before recovery. It cannot by itself select a branch or grant any permission.

Exact packet

The docket is one of eight exact cards required by CS-09 Cue Execution Idempotency Review. The remaining cards expose the white master, yellow carbon, caller roster, timecode, automation ingest, physical execution receipt, and future recovery route as independent surfaces.

Authority boundary

The card proves named-cue chronology only. RN does not prove caller identity, authority, authorship, performer consent, rigging clearance, edit reuse, sponsor clearance, archive ownership, blame, or universal broadcast permission.

Runtime source