Missing Roll-Call Reconciliation / 漏点名复核线

Missing Roll-Call Reconciliation is the pressure storyline that follows successful movement, service, caption, payroll, promise, or custody routing when a later reader discovers that the expected subject does not reconcile.

The line answers the strongest next gap after the current live-floor and liability surface: the desk can prove that a flow moved, but it still has to prove that the right person, witness, body, source, or route asset is actually accounted for.

This storyline binds 漏点名复核机制, 漏点名账本, 漏点名复核, and 漏点名默认.

Why this expansion matters

Recent content makes many strong first-order decisions playable:

• 直播现场通行瓶颈线 asks which flow moves through a finite passage.
• 容量告知送达队列线 asks who was warned and in what order.
• 字幕证词羁押线 asks whose caption witness record survives.
• 受保护证人薪册 asks whether a witness is paid and protected.
• 私约违背线 asks whether private material can be spent.

The missing second-order pressure is roll-call. A receipt can say safe exit, served notice, witness delivered, source anonymized, route asset escorted, or oxygen queue released. A later system can still ask: where is the actual subject, under what identity, under whose custody, and in what condition?

Bound content pack

• 漏点名复核机制 defines presence/identity/custody/condition separation.
• 漏点名账本 records the challenged receipt, expected subject, conflict reader, protection scope, selected posture, and future route consumer.
• 漏点名复核 lets the player search, seal-match, publicize, quietly check, substitute receipt, quarantine, accept absence scar, or default.
• 漏点名默认 fires or arms when the roll-call contradiction is hidden or falsely cleared.

State-triggered entry

Open only from a live contradiction:

entry_state_required:
  trigger_kind: state_pressure
  prior_receipt_any:
    - live_floor_egress
    - capacity_notice_service
    - caption_witness_custody
    - protected_witness_payroll
    - confidant_promise
    - fan_oxygen
    - route_asset_custody
    - broadcast_reality
  receipt_claims_presence_or_safety: true
  later_reader_contradicts_receipt: true
  expected_subject_visible: true
  identity_or_seal_visible_or_explicit_absence: true
  protection_scope_visible_or_explicit_absence: true
  condition_visible_or_explicit_absence: true
  future_reader_or_route_consumes_roll_call_state: true
  no_fixed_turn_trigger: true
  no_fixed_day_or_week_trigger: true
  no_raw_missing_count_trigger: true
  no_dashboard_or_lens_health_trigger: true

The line fails if it opens from a fixed chapter phase, fixed turn number, day/week cadence, raw crowd count, raw attendance count, chapter quota, dashboard status, or lens health.

Storyline spine

Beat 1 — A receipt claims the subject is accounted for

A prior surface produces a receipt: an egress log, capacity notice, caption witness row, payroll token, private promise row, fan oxygen release, route asset bag, or broadcast-reality trace.

The receipt claims that a person, witness, source, body, proof bundle, or route asset is safe, present, served, anonymized, escorted, or withdrawn.

Beat 2 — A future reader cannot find the same subject

A later reader asks for the subject and fails to reconcile the row:

• fan public asks for a missing group after a safety release;
• access-caption class finds a reader absent from the certified path;
• protected witness payroll lacks the sealed token;
• archive receives a bag but not the human carrier condition;
• sponsor manifest counts a body that broadcast reality duplicated;
• private promise kept the source unnamed but public roll-call demands a name;
• route asset reader rejects custody condition even though an escort receipt exists.

Beat 3 — Presence, identity, custody, and condition split apart

The player must not answer with safe or missing. The row must distinguish:

• whether the subject is physically present;
• whether the identity or seal matches;
• who can vouch for the row;
• what condition the subject arrived in;
• which future route or reader will consume the result.

Beat 4 — The producer chooses a scarred reconciliation posture

Run 漏点名复核. Valid postures include physical search, sealed identity match, public roll-call, lawful quiet check, substitute receipt, route asset quarantine, accept absence scar, or false all-clear default.

Every branch must improve one pressure, cost another, and mutate future play.

Beat 5 — The resolved or false accounting becomes route state

Future content inherits sealed_identity_present, lawful_only_presence, public_roll_call_receipt_required, substitute_receipt_contested, route_asset_quarantined, identity_alias_contested, witness_hostile, character_unavailable, or recovery_only.

Branch map

Branch	Immediate relief	Cost/scar	Future state
Physical search	confirms presence and condition	search delay, live-floor hazard, public anxiety	condition receipt, route costlier, fan/access pressure
Sealed identity match	protected witness/source is counted without public name	public distrust, lawful notice burden, handler burden	sealed-present or lawful-only state
Public roll-call	clears false missing or locates a body	identity exposure, panic, sponsor/inspection heat	public receipt, reprisal or promise breach risk
Lawful quiet check	archive/inspector validates without public naming	public distrust, access pressure, route delay	lawful-only presence, appeal pressure
Substitute receipt	earlier receipt temporarily stands in	proof ambiguity, future contradiction, handler cost	contested receipt, contradiction pending
Route asset quarantine	asset/person mismatch cannot contaminate canon	route blocked, sponsor pressure, archive burden	quarantined asset, recovery-only risk
Accept absence scar	false all-clear is blocked	panic, ending scar pressure, safety legitimacy loss	recovery-only or scarred ending eligibility
False all-clear default	fastest narrator accounts everyone	hidden harm hardens	default event arms false accounting

No branch may turn a single movement, notice, caption, payroll, promise, or custody receipt into universal public/lawful/sponsor/route safety.

Character and route hooks

• 郁蓝未授权史官线 can protect a source whose sealed identity must still be counted.
• 白鸦黑箱补丁羁押线 can prove a bag arrived while its carrier condition remains contested.
• Shen Luo Storyline can draft substitute receipt terms, but contract capture rises if the receipt replaces a person.
• 韩砚霜白手套例外线 can perform lawful quiet checks that narrow public legitimacy.
• 艾笙海盗频段童声线 can force child-voice source protection against public roll-call.
• Mu Ning Storyline can be duplicated by broadcast reality while the physical body is no longer at the stage threshold.

Missability and recovery

This storyline is missed when a future route consumes safe, cleared, served, evacuated, delivered, anonymized, escorted, or withdrawn without reading or creating a roll-call row.

Missed states include false_all_clear, false_missing, sealed_identity_exposed, lawful_only_presence, sponsor_accounted_only, aired_duplicate, route_asset_quarantined, hostile_witness, character_unavailable, and recovery_only.

Recovery is allowed only with visible cost: late physical search, public correction, lawful quiet check, protected witness payroll repair, access-caption receipt, oxygen review, route asset re-quarantine, public contrition, or ending scar audit. Recovery cannot retroactively make the earlier receipt a universal all-clear.

Replay evidence expectation

storyline_id: storyteller.storyline.missing_roll_call_reconciliation.v1
session_id: lens-missing-roll-call-reconciliation-v1-<timestamp>
seed: <deterministic-seed>
entry_state:
  trigger_kind: state_pressure
  prior_receipt_claims_presence_or_safety: true
  later_reader_contradicts_receipt: true
  expected_subject_visible: true
  identity_or_seal_visible_or_explicit_absence: true
  protection_scope_visible_or_explicit_absence: true
  future_reader_or_route_consumes_roll_call_state: true
  no_fixed_turn_trigger: true
offered:
  card: storyteller.card.missing_roll_call_ledger.v1
  rite: storyteller.rite.missing_roll_call_reconciliation.v1
branch_result:
  selected_posture: physical_search | sealed_identity_match | public_roll_call | lawful_quiet_check | substitute_receipt | route_asset_quarantine | accept_absence_scar | false_all_clear_default
  expected_subject: <subject>
  conflict_reader: <reader>
  support_or_absence: <support>
  receipt_after_or_absence: <receipt or explicit_absence>
  presence_state_after: <state>
  identity_state_after: <state>
  custody_state_after: <state>
  condition_after: <state>
  future_reader_effect: <effect>
  counter_deltas:
    relief: []
    cost: []
    future: []
default_branch:
  event_seen_or_armed: storyteller.event.missing_roll_call_default.v1 | explicit_absence
  default_narrator: <narrator or explicit_absence>
assertions:
  - entry_is_state_triggered
  - prior_receipt_and_later_reader_visible
  - expected_subject_identity_scope_and_condition_are_separate
  - selected_posture_has_support_receipt_and_future_reader
  - branch_outcomes_diverge
  - no_universal_all_clear
  - default_mutates_future_play
  - no_fixed_turn_day_week_raw_count_dashboard_or_lens_health_trigger

Non-goals

• Not a generic attendance check.
• Not a death counter.
• Not a crowd mood meter.
• Not raw count expansion.
• Not a replacement for egress, capacity service, caption custody, protected witness payroll, private promise, fan oxygen, or route asset custody.
• Not valid unless the prior receipt, challenged subject, conflict reader, support, receipt-after, relief/cost/future deltas, and future route consumer are all playable.