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

Proof Board Snapshot Custody defines how a visible board of proof rows becomes a custody object when later play cites it as proof, route authority, or management closure.

The mechanism fills a seam between existing surfaces. 制作分诊台 can list live tickets. Replay Export Custody and 复盘接手包分诊线 keep replay and resume evidence scoped. 导出证据回流分岔线 makes old proof return. 复原追偿搁架线 names recourse. 路线装配兼容线 checks bundled route assets.

This mechanism asks a narrower question: when those rows are pinned to one board and somebody cites the board, does the board preserve custody or launder stale and omitted rows into clean proof?

State model

proof_board_snapshot_custody:
  board_snapshot_state:
    - draft_board
    - scoped_snapshot
    - rebuilt
    - row_seated
    - split_required
    - quarantined
    - minority_note_published
    - false_clean_snapshot
    - stale_board_hardened
    - captured_board
    - contradiction_pending
    - recovery_only
  row_state:
    - fresh
    - scoped
    - stale
    - omitted
    - quarantined
    - public_only
    - lawful_only
    - sponsor_only
    - split_required
    - contradiction_pending
    - captured
    - false_owner
    - recovery_only
  board_visibility:
    - pinned
    - hidden
    - summarized
    - footnoted
    - redacted
    - absent
    - contested

Entry conditions

The mechanism opens only from state pressure.

entry_state_required:
  trigger_kind: state_pressure
  board_snapshot_present_or_claimed: true
  board_rows_min: 2
  future_reader_or_route_consumes_snapshot: true
  board_used_as_proof_route_authority_report_or_annex: true
  at_least_one_row_state_visible: true
  custodian_or_explicit_absence_visible: 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

Invalid entry sources: fixed sequence number, upkeep timer, raw board row count, dashboard status, lens-health state, generic evidence review, or a board with no downstream reader.

Bound surfaces

• 证据板快照 records the board, rows, visibility, custodian, harmed reader, selected posture, and future effect.
• 证据板羁押复核 assigns how the snapshot may be cited.
• 过期证据板快照默认 fires or arms when the snapshot is consumed as clean.

Branch families

Branch	Relief	Cost	Future effect
Certify with scope	a reader can cite the board narrowly	addendum due, excluded-reader pressure, handler burden	accepted with scope
Rebuild board	stale or captured board risk drops	delay, archive debt, management pressure	proof-board rebuild required or costlier
Seat omitted row	hidden harm becomes legible	sponsor/public/inspection pressure rises	contradiction pending or split required
Split board	incompatible readers get scoped snapshots	source ambiguity and future reconciliation cost rise	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, worker, claimant, artist, or operator row remains visible	exposure, public distrust, inspection heat	public addendum or accepted with challenge
Stale default	fastest clean board files first	false-clean snapshot, hostile reader, stale board hardening	blocked, contradiction pending, recovery-only

No branch may create universal board truth across public, lawful, sponsor, archive, artist, worker, claimant, route-asset, management, and broadcast-reality readers.

Counter surfaces

Every resolved branch mutates at least one relief surface, one cost surface, and one future reader or route effect.

counter_surfaces:
  - proof_board_integrity
  - snapshot_custody_clarity
  - stale_row_pressure
  - omitted_row_erasure
  - hidden_reader_erasure
  - route_asset_integrity
  - proof_burden
  - source_ambiguity
  - archive_debt
  - inspection_heat
  - sponsor_stop_loss_pressure
  - public_receipt_distrust
  - fan_oxygen_resentment
  - artist_boundary_pressure
  - worker_or_operator_exposure
  - claimant_hostility
  - management_pressure
  - producer_license_pressure
  - broadcast_reality_drift
  - recovery_route_cost

Default rule

A stale board default occurs when the game lets a board caption, row order, pinned proof, or absent row substitute for custody review. The default must name default actor, false board claim, stale or omitted row, harmed reader, snapshot state after, and future route effect.

Non-goals

• Not a dashboard or project-board governance page.
• Not a generic evidence inventory.
• Not a raw row-count gate.
• Not a replacement for replay export, resume triage, evidence carryover, recovery indemnity, or route loadout.
• Not valid unless the snapshot changes future route access, reader acceptance, route-asset custody, or recovery-only state.