Ending Scar Ledger / 结局伤痕账本线

Ending Scar Ledger is a pressure storyline for the moment when accumulated custody, liability, release, proxy, public-proof, and route-asset scars must decide which endings can still be true.

The current Storyteller mesh already creates rich mid/late-game consequences: stabilization tickets, clean-ending custody dockets, recourse release receipts, proxy posture rows, route assets, black-box contradictions, public receipts, and faction captures. The gap is terminal inheritance. Without an ending scar ledger, the game can prove branch consequences in replay and then forget them when selecting an ending.

This storyline makes terminal resolution a continuation of management/RPG state, not a separate score gate.

Primary playable question

When the broadcast is close enough to end, which scar is allowed to define the ending — public witness, private custodian, split copies, recovery-only survival, black-box contradiction, or no clean ending at all?

State-triggered entry

Open this storyline when all of the following are true:

  1. at least one durable scar exists from stabilization liability, clean-ending seizure, recourse release, proxy posture, route-asset custody, public receipt, black-box proof, broadcast reality drift, or equivalent;
  2. the scar names or can derive a source row, proof carrier, claimant privileged, claimant harmed, scar state, and route effect;
  3. at least two ending families could be affected by the scar;
  4. one proposed ending would become false-clean if the scar were ignored;
  5. at least one proof carrier is available or explicitly absent: public receipt, legal seal, edit checksum, sponsor contract, fan oath, proxy testimony, pirate relay, route asset, black-box copy, or absence.

This storyline is driven by scar state and claimant pressure. It has no fixed numbered trigger.

Content pack

Card

  • 结局伤痕账本 — records source scar, affected ending family, privileged claimant, harmed claimant, proof carrier, scar before/after, and route effect after terminal eligibility.

Rite

  • 结局资格听证 — assignable terminal hearing where the player seats public verdict, private capture, split canon, recovery-only, black-box reopening, or blocks false-clean.

Event

  • 结局伤痕审计 — audit event that fires when terminal resolution tries to ignore an active scar or overclaim exclusive truth.

Mechanic

Ending families

  • 公开伤痕裁决 — public proof keeps the wound visible and blocks private clean capture.
  • 私有洁净收编 — sponsor, inspector, archive, or editor custody stabilizes the ending by narrowing the public version.
  • 分裂托管正典 — incompatible copies survive as terminal canon.
  • 仅可复原播出 — clean closure is blocked, but a costly recovery hook remains.
  • Black Box Opened — legacy black-box proof can be re-read as terminal contradiction or causal exposure.

Existing pressure surfaces

Scar inheritance ladder

Scar sourceExample source stateEnding effect
Stabilization liabilitypublic_bonded, production_carried, recalled, recovery_onlyPublic verdict, recovery-only, or blocked false-clean.
Clean ending seizuresponsor_clean_cut_claimed, public_countercopy_live, asset_copy_split, clean_ending_false_ownerPrivate capture, public verdict, split canon, or audit.
Collection releasereleased_with_scar, public_only, lawful_only, mis_stamped, refusedCostlier ending, public-only, lawful-only, recovery-only, or audit.
Proxy posturerecruited, retained, exposed, faction_bound, hostile, missing, recovery_onlyProxy testimony carrier, private capture, public verdict, or recovery-only.
Route asset custodyroute_asset, protected, captured, false_owner, sacrificed, recovery_onlyEnding unlocked with scar, private capture, false-clean block, or recovery.
Black box / source proofcontradiction_pending, source_ambiguity, black_box_openedReopen black box, split canon, public audit, or contradiction-pending ending.

Branch model

Branch A — Public scar verdict

The player seats public receipt, fan oath, witness proof, artist refusal, pirate relay, route asset, or black-box copy as the terminal proof carrier.

Expected outcomes:

  • 公开伤痕裁决 becomes eligible;
  • private clean capture is blocked, public-audited, or made costlier;
  • public_receipt_legitimacy, fan_oxygen_balance, artist_trust, or public_grief_stability may improve;
  • fan_refund_trigger, witness_exposure, sponsor_stop_loss_pressure, inspection_heat, or public_audit_required remains visible.

Branch B — Private clean capture

The player seats sponsor contract, inspector seal, archive lock, edit checksum, or lawful release proof as the terminal proof carrier.

Expected outcomes:

  • 私有洁净收编 becomes eligible;
  • public countercopy, fan restitution, artist refusal, witness proof, or pirate relay route is blocked, made costlier, or recovery-only;
  • broadcast_version_stable, lawful_use, or sponsor_safe_closure may improve;
  • contract_capture, bureau_favor_debt, edit_debt, source_ambiguity, or public_receipt_distrust remains visible.

Branch C — Split custody canon

The player proves that exclusive terminal ownership would lie and seats two incompatible copies.

Expected outcomes:

  • 分裂托管正典 becomes eligible;
  • exclusive public verdict and exclusive private capture are blocked;
  • two future import states remain, one formal and one public/source/black-box;
  • source_ambiguity, archive_debt, public_receipt_distrust, false_owner_risk, or reality_drift remains visible.

Branch D — Recovery-only broadcast

The player admits that clean terminal closure is blocked and preserves only a costly recovery hook.

Expected outcomes:

  • 仅可复原播出 becomes eligible;
  • at least one clean ending is marked blocked or impossible;
  • a future hook remains: appeal, rescue, public correction, checksum release, substitute carrier, triage repair, or black-box reopening;
  • recovery_cost, hostile_claimant, route_blocked, black_screen_pressure, or production_scar remains visible.

Branch E — Reopen black box

The player seats black-box copy or equivalent causal proof as terminal carrier.

Expected outcomes:

  • Black Box Opened remains eligible under Storyteller scars;
  • hidden claimant, causal contradiction, or omitted source becomes visible;
  • the proposed ending becomes contradiction-pending, public-audited, split, or recovery-only;
  • source_ambiguity, archive_heat, or public_contradiction rises.

Branch F — Block false-clean

The player cannot seat a credible proof carrier, or the proposed ending would erase a durable scar.

Expected outcomes:

  • proposed clean ending is blocked;
  • 结局伤痕审计 emits or records contradiction;
  • false_owner_risk, public_receipt_distrust, route_blocked, or recovery_only_terminal rises;
  • the branch remains visible instead of silently dropping an ending.

Counter and state contract

Every branch must record:

  • one source scar row;
  • one scar_state_before;
  • one selected terminal posture;
  • one scar_state_after;
  • one proof carrier or explicit absence;
  • one privileged claimant;
  • one harmed claimant;
  • one ending family after;
  • at least three counter or durable-state deltas;
  • one route effect after.

Primary counters and states:

  • ending_scar_pending
  • ending_public_legitimacy
  • private_capture_pressure
  • public_audit_required
  • lawful_only_closure
  • public_only_closure
  • split_canon_pressure
  • source_ambiguity
  • archive_debt
  • contract_capture
  • bureau_favor_debt
  • edit_debt
  • fan_refund_trigger
  • witness_exposure
  • recovery_cost
  • false_owner_risk
  • black_box_contradiction

Missability and recovery

This storyline is missable when terminal resolution treats scar rows as flavor, resolves endings by global score, seats private clean capture while public proof survives, seats public verdict while lawful capture survives, collapses split copies into one truth, or upgrades recovery-only into a clean final screen.

Recovery is allowed through:

  • new public proof carrier plus audit cost;
  • legal seal appeal plus lawful-only scar;
  • split copy recognition plus reality-drift scar;
  • route-asset recovery plus release receipt;
  • proxy rescue plus protection debt;
  • black-box reopening plus contradiction.

Lens contract

The executable lens for this storyline should fail unless it proves:

  • entry comes from scar state, not a fixed numbered turn;
  • at least one Ending Scar Ledger row is concrete and inherited from a live source branch;
  • public verdict, private capture, split canon, recovery-only, black-box reopening, and false-clean block produce non-equivalent outcomes;
  • terminal resolution mutates ending eligibility, proof carrier, claimant privilege, harmed claimant, scar state, and route effect;
  • clean closure cannot erase an active scar;
  • Ending Scar Audit changes future terminal state when an active scar is ignored;
  • replay evidence records source session id, source seed, resolver session id, selected terminal posture, before/after scar state, and ending family after.

Non-goals

  • Not broad governance.
  • Not raw ending count satisfaction.
  • Not a fixed final-turn event.
  • Not a morality meter.
  • Not a way to make all endings available.
  • Not a cleanup layer that erases route-asset, liability, release, proxy, public, legal, edit, sponsor, or black-box scars.