State Scar Callback Readback Lens / 状态伤痕回叫回读 Lens

Design intent

A past state scar should not become flavor text after it is recorded. When a later route or reader tries to consume the scar as proof, pity, sponsor clearance, or route-asset authority, the game must force a visible callback: name the source scar, name the current claimant, show who is harmed or absent, and leave a future route effect.

Entry oracle

trigger_kind: state_pressure
source_scar_row_visible: true
current_callback_reader_visible: true
attempted_future_use_visible: true
harmed_or_displaced_reader_visible_or_explicit_absence: true
proof_bridge_or_explicit_absence_visible: true
scar_scope_visible: true
future_reader_consumes_callback_state: true
no_fixed_turn_trigger: true
no_dashboard_or_lens_health_trigger: true

Playable contract

• Docket: storyteller.card.state_scar_callback_docket.v1 records source scar row, current reader, attempted use, harmed reader/absence, proof bridge, scope, after-state, and future route effect.
• Rite: storyteller.rite.state_scar_callback_readback.v1 is a repeatable hearing/review shape with divergent postures: certify, narrow, bridge, split, quarantine, retire, and false-clean default.
• Event: storyteller.event.false_clean_scar_callback_default.v1 records the bad default when a scar is laundered into clean authority without a reader, proof bridge, or future cost.

Evidence

• Bound code sibling: wiki/content/lens/storyteller/state-scar-callback-readback.lens.ts
• Wiki content pack: storyline, mechanic, docket, rite, event pages.
• Durable gameplay evidence: lens/replays/state-scar-callback-readback.game-cli.replay.json, exported from a lens-scoped save (lens-state-scar-callback-readback-*).