Phantom Route Rumor Pressure / 幻路线传言压力机制

Phantom Route Rumor Pressure models a branch that did not happen, but later becomes socially or commercially spendable as if it were a promise.

A phantom route is not a hidden ending and not a free teaser. It is an exposed absence with a claimant: a declined offer, a route that was eligible but not chosen, a route discontinued with notice, an unavailable option whose receipt was public, a cut fragment that implies another path, or a leaked loadout that makes an impossible route look promised.

Mechanical promise

When an unrealized route becomes claimable, the game must name:

• the absent route surface;
• the source of public knowledge;
• the reader trying to spend it;
• the claimant who says the route should have happened;
• the proof or leak that makes the rumor plausible;
• the future route or reader that will change if ignored.

The absence remains true. The player is not forced to canonize the phantom. The player must manage who is allowed to cite it.

Entry state

entry_state:
  trigger_kind: state_pressure
  unrealized_route_surface_present: true
  exposure_source_present: true
  claimant_or_claimant_public_present: true
  requested_reader_present: true
  proof_anchor_or_explicit_absence_visible: true
  future_route_or_reader_effect_present: true
  player_can_disavow_scope_publish_explain_compensate_quarantine_or_default: true
  no_fixed_turn_trigger: true
  no_fixed_day_or_week_trigger: true
  no_raw_rumor_count_trigger: true
  no_dashboard_or_lens_health_trigger: true

Valid exposure sources include a declined-offer receipt, branch eligibility receipt, route discontinuance register, cutroom leak, fan oxygen ledger post, sponsor copy line, public queue witness, inspector question, archive stub, route loadout manifest, or broadcast-reality drift artifact.

Phantom route states

State	Meaning	Required consequence
unexposed_absence	The route did not happen and no one can spend it yet.	No branch may depend on it.
exposed_absence	A receipt, leak, witness, or copy makes the absence visible.	Docket row can be created.
rumored_route	Public or faction pressure treats the route as plausibly promised.	At least one future reader changes acceptance.
scoped_disavowal	Production says what did not happen and why.	Rumor leverage drops, but public/sponsor/route cost rises.
countercopy_published	A public or lawful explanation is attached.	Claimant pressure changes, exposure rises.
compensated_without_canon	A claimant receives relief without making the route true.	Compensation debt or precedent pressure rises.
quarantined_phantom	The proof anchor cannot be cited until reviewed.	Current route is delayed or narrowed.
phantom_asset	The rumor becomes a managed route asset.	A future rite may assign it with scope and scar.
hardened_claim	The rumor becomes someone else’s claim of reality.	Future route becomes blocked, hostile, costlier, or recovery-only.

Branch families

• scope_disavowal — deny the phantom cleanly while naming source, claimant, and excluded reader.
• publish_countercopy — answer the rumor in public, archive, lawful, or fan-facing form.
• compensate_without_canon — pay or offer relief without admitting the route existed.
• quarantine_proof_anchor — hold leak/cut/receipt while preserving future review.
• convert_to_phantom_asset — make the rumor a scoped, assignable asset with maintenance cost.
• let_harden — allow claimant, sponsor, fan public, archive, inspector, or broadcast reality to author the missing route.

No branch may silently convert rumored_route into canon truth or delete it without cost.

Counters and durable surfaces

Every branch mutates at least three surfaces:

• phantom route state;
• claimant or public pressure;
• proof anchor state;
• future route acceptance;
• one cost or scar.

Useful counters:

• phantom_route_pressure
• rumor_claimant_leverage
• public_expectation_debt
• sponsor_copy_overclaim_pressure
• fan_oxygen_resentment
• inspection_heat
• archive_debt
• broadcast_reality_drift
• route_discontinuance_legibility
• declined_offer_legitimacy
• countercopy_exposure
• phantom_asset_maintenance
• future_route_acceptance

Integration boundaries

• 未采纳报价回执线 records a rejected or unchosen offer. This mechanism starts when someone later spends the rejection as a promise.
• 分支资格回执线 records what was or was not eligible. This mechanism starts when that receipt becomes public expectation.
• 路线停办登记线 closes or stops a route. This mechanism handles the rumor that the stopped route still exists.
• 路线装配兼容线 checks whether assets can be bundled. This mechanism handles a leaked impossible bundle being treated as promised.
• 冠名口播担保线 clears sponsor language. This mechanism blocks sponsor copy from citing a phantom route as delivered proof.

Replay evidence shape

mechanic_id: storyteller.mechanic.phantom_route_rumor_pressure.v1
session_id: lens-phantom-route-rumor-pressure-v1-<timestamp>
seed: <deterministic-seed>
entry_state:
  trigger_kind: state_pressure
  unrealized_route_surface_present: true
  exposure_source_present: true
  claimant_or_claimant_public_present: true
  requested_reader_present: true
  future_route_or_reader_effect_present: true
  no_fixed_turn_trigger: true
branch_runs:
  managed_branch:
    selected_posture: scope_disavowal | publish_countercopy | compensate_without_canon | quarantine_proof_anchor | convert_to_phantom_asset
    phantom_route_state_after: <state>
    claimant_state_after: <state>
    future_route_effect: <effect>
    counter_deltas:
      relief: []
      cost: []
      future: []
  default_branch:
    selected_posture: let_harden
    hardening_actor: <actor>
    hardened_claim: <claim>
    future_route_effect: blocked | costlier | hostile | sponsor_only | public_only | lawful_only | recovery_only | equivalent
assertions:
  - absence_remains_true_unless_explicitly_canonized_by_content
  - rumor_source_claimant_reader_and_future_effect_are_visible
  - managed_and_default_branches_diverge
  - success_has_cost
  - hardening_is_durable
  - no_fixed_turn_day_week_raw_count_dashboard_or_lens_health_trigger

Non-goals

• Not a hidden-route catalog.
• Not a teaser system.
• Not a generic reputation meter.
• Not a retcon tool.
• Not a fixed escalation phase.
• Not valid unless an unrealized route changes future playable state through a visible claimant, proof anchor, reader, and scar.