Storyteller Wiki

Claimant Briefing Order / 认领告知顺序线

8 min read

Claimant Briefing Order / 认领告知顺序线

Claimant Briefing Order is a pressure storyline for the moment before a public correction, edit priority, route-asset custody decision, witness move, public apology, stabilization handoff, or archive seal becomes visible.

The producer has enough information to act, but not enough trust to tell everyone safely. Telling sponsor first can buy time and capture wording. Telling inspector first can make proof admissible and arm injunction. Telling fan public first can block private capture and trigger panic. Telling artist or witness first can preserve consent and delay the slot. Telling nobody can keep the action quiet until someone else narrates it.

Primary playable question

When one pending action will harm several claimants, who receives advance notice first — sponsor, inspector, archive, fan public, artist, witness, editor, route claimant, production, or nobody — and what can the excluded claimants do because of that order?

Every answer must name:

  • pending action;
  • first briefed claimant or no-briefing choice;
  • excluded claimants;
  • proof anchor or explicit absence;
  • caller/handler or explicit absence;
  • notice terms;
  • claimant response;
  • leak/preemption/default risk;
  • future route effect.

Why this is the next useful expansion

The satisfied corpus already has strong choices for:

The remaining high-value gap is notice privilege. A claimant can win before a formal hearing if they learn early enough to file, leak, fund, injunct, countercopy, protect, or retaliate. Without this storyline, the engine can jump from private knowledge to public action as though every claimant learned at the same time.

Bound content pack

This storyline binds:

State-triggered entry

Open this storyline when all of the following are true:

  1. a pending action exists that will alter public reality, custody, correction, edit priority, witness safety, artist consent, stabilization liability, or route access;
  2. at least two claimant families are materially affected;
  3. first notice can change one claimant’s response before the action resolves;
  4. late or absent notice can harm another claimant;
  5. the player can choose first notice, counterbrief, no briefing, or explicit absence;
  6. notice order can mutate counters, route access, claimant posture, or future assignment.

This storyline must never open from a fixed numbered turn, arbitrary day count, or content-volume target.

Storyline spine

Beat 1 — A pending action cannot stay private

A prior surface creates something that must be acted on:

  • a correction row wants the public slot;
  • a cutroom row wants source custody;
  • a route asset is about to be released, seized, split, or burned;
  • a witness or artist is about to become visible;
  • an apology or refusal note will name or omit harm;
  • a stabilization ticket is about to choose its carrier;
  • an archive seal or lawful quarantine will narrow public use.

The player receives or updates 认领告知案卷.

Beat 2 — The notice advantage is named

The docket must show what the first claimant can do with advance knowledge.

Common notice advantages:

  • sponsor can file countercopy, stop-loss hold, clean wording, relief funding, or private review;
  • inspector/archive can file injunction, admissibility lock, quarantine, lawful-only order, or seal condition;
  • fan public, Yu Lan, or pirate relay can leak, counterbrief, mobilize receipts, or block private capture;
  • artist, witness, or proxy can refuse, consent, defect, demand protection, or expose omission;
  • editor/black-box/archive source holder can capture source custody or split a version before public correction.

Beat 3 — The briefing call assigns proof and caller

The player runs 认领告知电话.

The rite requires:

  • selected first claimant or no-briefing choice;
  • excluded claimant list;
  • proof anchor or absence;
  • caller/handler or absence;
  • terms of notice;
  • accepted cost.

A famous character alone is insufficient. A branch must show why the notice is credible or why absence matters.

Beat 4 — First notice changes the pending action

The recipient response mutates the pending action before it resolves.

Possible responses:

  • protect, fund, preempt, file injunction, leak, counterbrief, delay, defect, refuse, seize source, or stay silent.

The selected claimant gains leverage, while an excluded claimant’s future pressure becomes visible.

Beat 5 — Leak, preemption, or recovery-only scar

If the player gives unsafe first notice, hides a harmed claimant, breaks terms, lacks proof, or gives no briefing, 告知泄漏抢跑 fires or becomes default-ready.

The result does not erase the pending action. It changes how that action can now resolve: public-only, lawful-only, sponsor-captured, delayed, hostile, captured, blocked, costlier, split, contradiction-pending, or recovery-only.

Branch map

Branch A — Sponsor-first review

The player briefs sponsor, management, Orion Breath, Shen Luo, or a stop-loss/countercopy holder before public or lawful notice.

Expected outcomes:

state_after_any: [briefed, embargoed, preempted, sponsor_captured]
relief_any: [budget_strain_down, sponsor_stop_loss_pressure_down, slot_pressure_down]
cost_any: [sponsor_preemption_up, contract_capture_up, public_receipt_distrust_up, fan_oxygen_resentment_up]
future_route_effect_any: [sponsor_captured, public_audit_required, clean_version_blocked, recovery_only]

Branch B — Inspector/archive-first lawful notice

The player briefs inspector, archive, Han Yanshuang, Inspector Rhee, or lawful caller first.

Expected outcomes:

state_after_any: [briefed, injuncted, lawful_only, quarantined]
relief_any: [lawful_use_unlocked, archive_fraud_down, custody_clarity_up]
cost_any: [inspection_heat_up, lawful_injunction_risk_up, bureau_favor_debt_up, public_delay_up]
future_route_effect_any: [lawful_only, appeal_required, public_route_costlier, recovery_only]

Branch C — Public/fan warning first

The player briefs fan public, Yu Lan, public receipt holders, pirate relay, or audience witnesses first.

Expected outcomes:

state_after_any: [briefed, leaked, public_only, counterbriefed]
relief_any: [public_receipt_legitimacy_up, private_capture_blocked, fan_trust_up]
cost_any: [public_panic_up, sponsor_stop_loss_pressure_up, witness_exposure_up, inspection_heat_up]
future_route_effect_any: [public_only, sponsor_retaliation, witness_route_costlier, blackout_pressure_up]

Branch D — Artist/witness/refusal first

The player briefs the harmed artist, witness, proxy, refusal holder, protected carrier, or safehouse first.

Expected outcomes:

state_after_any: [briefed, refusal_preserved, protected_notice, delayed]
relief_any: [artist_trust_up, witness_safety_up, consent_legitimacy_up, false_consent_blocked]
cost_any: [schedule_pressure_up, sponsor_delay_up, witness_exposure_up, handler_burden_up]
future_route_effect_any: [unlocked_with_notice, delayed, refusal_route_preserved, recovery_only]

Branch E — Editor/source/archive first

The player briefs Baiya, Han Cutroom, archive source holder, black-box holder, checksum keeper, or source custodian first.

Expected outcomes:

state_after_any: [briefed, split_notice, source_captured, contradiction_pending]
relief_any: [slot_legibility_up, continuity_hazard_down, source_integrity_up]
cost_any: [edit_debt_up, archive_debt_up, source_ambiguity_up, public_distrust_up]
future_route_effect_any: [split_canon, lawful_only, contradiction_pending, recovery_only]

Branch F — Counterbrief or split notice

The player tells a second claimant to offset the first notice advantage.

Expected outcomes:

state_after_any: [counterbriefed, split_notice, embargoed]
relief_any: [private_capture_blocked, lawful_overreach_blocked, public_panic_softened]
cost_any: [source_ambiguity_up, claimant_retaliation_up, future_correction_cost_up]
future_route_effect_any: [split_canon, costlier, public_audit_required, lawful_appeal_required]

Branch G — No briefing, broken briefing, or absent proof

The player proceeds silently, cannot name proof/caller, hides excluded claimants, or breaks terms.

Expected outcomes:

event_seen: storyteller.event.briefing_leak_preemption.v1
state_after_any: [no_notice_default, leaked, preempted, hostile, captured, recovery_only]
cost_any: [claimant_retaliation_up, public_panic_up, sponsor_preemption_up, inspection_heat_up, route_asset_capture_up]
future_route_effect_any: [blocked, hostile, captured, public_only, lawful_only, recovery_only]

Character hooks

  • Orion Breath can turn first notice into relief funding or countercopy capture.
  • Shen Luo can phrase sponsor notice, but contract capture or manager debt rises.
  • Han Yanshuang can make lawful notice survivable, but inspection heat or bureau debt rises.
  • Inspector Rhee Archive can preserve admissibility, but can also narrow the action into lawful-only quarantine.
  • Yu Lan can carry public notice, but witness exposure and public panic become live.
  • Baiya can protect source legibility, but source ambiguity or edit debt rises.

Missability and recovery

This storyline is missable when the implementation:

  • jumps from private knowledge to public action without notice order;
  • allows all claimants to be briefed safely for free;
  • records no excluded claimant;
  • omits proof anchor or caller/absence;
  • lets broken embargo disappear as flavor;
  • treats late consent, witness refusal, sponsor countercopy, or lawful injunction as unrelated events.

Recovery is allowed only with scar:

  • public audit after sponsor preemption;
  • lawful appeal after public leak;
  • sponsor buyback after fan warning;
  • witness protection after exposed notice;
  • artist refusal preservation after false consent;
  • split source copy after editor capture;
  • recovery-only correction after no-notice default.

Replay/session evidence shape

storyline: storyteller.storyline.claimant_briefing_order.v1
session_id: lens-claimant-briefing-order-v1-<timestamp>
seed: <deterministic-seed>
entry_state:
  source_surface: correction_slot | cutroom_priority | claimant_collision | public_contrition | stabilization_liability | protected_witness | production_triage | route_asset | equivalent
  pending_action: <action id>
  affected_claimants:
    - <claimant a>
    - <claimant b>
  first_notice_can_change_response: true
  proof_anchor_or_absence: <anchor>
  caller_or_absence: <handler or absence>
  no_fixed_turn_trigger: true
offered:
  card: storyteller.card.claimant_briefing_docket.v1
  rite: storyteller.rite.claimant_briefing_call.v1
branch_runs:
  sponsor_first:
    first_briefed_claimant: sponsor
    excluded_claimants: []
    recipient_response: <response>
    state_after: <state>
    counter_deltas: {}
  inspector_first:
    first_briefed_claimant: inspector
    state_after: <state>
    counter_deltas: {}
  public_first:
    first_briefed_claimant: fan_public
    state_after: <state>
    counter_deltas: {}
  no_notice_or_broken_terms:
    event: storyteller.event.briefing_leak_preemption.v1
    state_after: <state>
    counter_deltas: {}
assertions:
  - state_triggered_entry
  - first_briefed_claimant_visible
  - excluded_claimants_visible
  - proof_anchor_or_absence_named
  - caller_or_absence_named
  - branch_outcomes_diverge
  - leak_or_preemption_changes_future_route

Non-goals

  • Not a new chapter phase.
  • Not a turn-count progression.
  • Not a generic relationship scene.
  • Not a governance/process page.
  • Not a universal notification checklist.
  • Not a replacement for correction slots, cutroom priority, claimant collision, public contrition, protected witness payroll, stabilization liability, or handler burden.
  • Not a way to tell every claimant safely and avoid all consequences.

Graph View

Backlinks