Proof Board Snapshot Custody / 证据板快照羁押线

Proof Board Snapshot Custody is a pressure storyline for the moment after multiple proof rows have become visible on a production board and a later route tries to cite that board as authority.

The current mesh already covers the neighboring problems:

• 制作分诊台 makes simultaneous crisis assignment finite.
• Replay Export Custody and 复盘接手包分诊线 keep durable replay and handoff rows scoped.
• 复盘接手冲突线 prevents replay capsules and resume packets from laundering each other.
• 导出证据回流分岔线 makes old proof return as a current route object.
• 复原追偿搁架线 names who carries recourse.
• 路线装配兼容线 prevents individually valid assets from becoming a clean bundle.

The remaining gap is the board snapshot itself. A board can pin some rows, hide others, summarize a contradiction, order rows to imply priority, or leave a stale proof visible. If a future reader consumes that snapshot as proof, the board becomes custody.

Primary playable question

When a future route cites a proof-board snapshot, does the producer certify the snapshot with scope, rebuild the board from source rows, seat an omitted row, split board versions by reader, quarantine the snapshot, publish a minority note, or let the stale board become the clean story?

Every answer must name board source, board custodian or absence, pinned and hidden rows, row states, harmed reader or explicit absence, selected posture, cost, and future route effect.

Content pack

This storyline binds:

• 证据板快照羁押机制;
• 证据板快照;
• 证据板羁押复核;
• 过期证据板快照默认.

State-triggered entry

Open this storyline only from state pressure.

entry_state:
  trigger_kind: state_pressure
  board_snapshot_present_or_claimed: true
  board_rows_min: 2
  board_used_as_proof_route_authority_report_or_annex: true
  future_reader_or_route_consumes_snapshot: true
  row_states_visible: true
  row_custodians_visible_or_explicit_absence: true
  hidden_stale_scoped_or_contested_row_visible_or_explicit_absence: true
  harmed_reader_or_claimant_visible_or_explicit_absence: true
  player_can_certify_rebuild_seat_split_quarantine_publish_or_default: true
  no_fixed_turn_trigger: true
  no_fixed_day_or_week_trigger: true
  no_raw_row_count_trigger: true
  no_dashboard_or_lens_health_trigger: true

Do not open from fixed turn count, day/week interval, chapter quota, raw board row count, dashboard status, lens-health state, or a board with no future reader.

Storyline spine

Beat 1 — A board becomes more than a board

A production board, replay export view, resume packet view, recovery shelf table, route loadout table, evidence carryover docket, or equivalent board has rows visible.

A future route, report, sponsor release, lawful annex, public statement, archive release, management closure, or broadcast-reality check wants to cite the board.

Beat 2 — The snapshot exposes board custody

Create or update 证据板快照.

The snapshot records row-by-row state:

• pinned rows;
• hidden rows;
• summarized rows;
• footnoted rows;
• redacted rows;
• absent rows;
• contested rows.

It also records board custodian, requested clean claim, hidden or harmed reader, and future consumer.

Beat 3 — The producer reviews the custody claim

Run 证据板羁押复核. The player chooses:

• certify with scope;
• rebuild board;
• seat omitted row;
• split board;
• quarantine snapshot;
• publish minority note;
• accept stale default.

A handler, sponsor seal, lawful stamp, editor checksum, public outrage, or management order cannot certify the board unless the row states and harmed reader remain visible.

Beat 4 — Board state changes route state

A successful branch may let a route proceed, but it cannot create universal board truth. The result must leave a future effect such as accepted with scope, public addendum required, lawful annex required, sponsor unwind required, proof-board rebuild required, split required, costlier, blocked, contradiction pending, hostile, or recovery-only.

Beat 5 — Stale snapshot becomes durable default

If the snapshot is consumed as clean, if row order substitutes for proof, if hidden rows are ignored, if scoped rows become universal, or if the custodian is absent without cost, 过期证据板快照默认 fires or arms.

The default names who filed the clean board, what false snapshot claim they made, which row or reader was hidden, and what future route changed.

Branch map

Branch	Immediate relief	Cost/scar	Future state
Certify with scope	board can be cited by one reader	addendum due, excluded-reader pressure, handler burden	accepted with scope
Rebuild board	stale/captured board risk drops	delay, archive debt, management pressure	proof-board rebuild required or costlier
Seat omitted row	hidden harm becomes legible	sponsor pressure, public distrust, inspection heat	contradiction pending or split required
Split board	incompatible readers keep scoped versions	source ambiguity, route delay, reconciliation cost	public-only, lawful-only, sponsor-only, split-required
Quarantine snapshot	false proof and false ownership are blocked	current route blocks, sponsor/fan pressure rises	blocked, lawful annex required, recovery-only
Publish minority note	dissent or harmed row remains visible	worker/operator exposure, public distrust, inspection heat	public addendum required or accepted with challenge
Stale default	fastest board story files first	false clean snapshot, hidden row hardens, hostile reader	blocked, contradiction pending, sponsor unwind, recovery-only

Character and desk hooks

• Yu Lan can force public board notes, but public distrust and sponsor retaliation rise.
• Han Yanshuang can demand lawful annex or quarantine, but bureau debt and public delay rise.
• Baiya can compare snapshot caption to checksum/source rows, but edit debt or source ambiguity rises.
• Shen Luo can broker sponsor-readable scope, but contract capture and excluded-reader pressure rise.
• Low-rank runners, operators, claimants, or artist-boundary holders can be protected only if the snapshot records their row state, not as invisible board consensus.

Missability and recovery

The storyline is missed when implementation lets a board snapshot unlock a route, satisfy a sponsor, file a public receipt, certify a lawful annex, or close a management report without recording row states, custodian, omitted row, harmed reader, and future effect.

Missed states:

• proof_board_snapshot_unopened;
• board_caption_false_clean;
• omitted_row_hardened;
• stale_row_loaded_as_fresh;
• scoped_row_universalized;
• hidden_reader_erased;
• captured_board;
• proof_board_recovery_only.

Recovery requires visible scar: rebuild the board, seat omitted row, publish minority note, split board by reader, quarantine the snapshot, add lawful annex, publish public addendum, sponsor unwind, or accept recovery-only proof.

Replay evidence expectation

storyline_id: storyteller.storyline.proof_board_snapshot_custody.v1
session_id: lens-proof-board-snapshot-custody-v1-<timestamp>
seed: <deterministic-seed>
entry_state:
  trigger_kind: state_pressure
  board_snapshot_present_or_claimed: true
  board_rows_min: 2
  board_used_as_proof_route_authority_report_or_annex: true
  future_reader_or_route_consumes_snapshot: true
  row_states_visible: true
  row_custodians_visible_or_explicit_absence: true
  hidden_stale_scoped_or_contested_row_visible_or_explicit_absence: true
  no_fixed_turn_trigger: true
snapshot:
  card: storyteller.card.proof_board_snapshot.v1
  snapshot_id: <snapshot>
  board_source: <source>
  board_custodian_or_absence: <custodian or explicit_absence>
  requested_clean_claim: <claim>
  future_reader: <reader>
  rows:
    - row_id: <row>
      row_state_before: <state>
      visibility: <visibility>
      citation_scope: <scope>
  hidden_or_harmed_reader: <reader or explicit_absence>
offered:
  rite: storyteller.rite.proof_board_custody_review.v1
branch_result:
  selected_posture: certify_with_scope | rebuild_board | seat_omitted_row | split_board | quarantine_snapshot | publish_minority_note | accept_stale_default
  snapshot_state_after: <state>
  future_route_effect: <effect>
  event_seen_or_armed: storyteller.event.stale_board_snapshot_default.v1 | explicit_absence
  counter_deltas:
    relief: []
    cost: []
    future: []
assertions:
  - entry_is_state_triggered
  - board_snapshot_is_custody_object
  - row_states_and_custodians_visible
  - hidden_or_harmed_reader_visible_or_explicit_absence
  - branch_postures_diverge
  - success_has_cost
  - stale_snapshot_default_is_durable
  - future_reader_consumes_snapshot_state
  - no_fixed_turn_day_week_raw_row_count_dashboard_or_lens_health_trigger

Non-goals

• Not a dashboard or project-board page.
• Not governance.
• Not a generic proof inventory.
• Not a raw row-count gate.
• Not a recap of old sessions.
• Not a replacement for production triage, replay export, resume triage, carryover, recovery indemnity, loadout, or reader collision.
• Not valid if a board snapshot can be treated as universal proof.