Recognized Basis Ledger / 确认基准账本

Recognized Basis Ledger is a board card for a result that happened in play but is counted differently by different factions. The card stores which version of a broadcast, correction, custody proof, settlement, memorial copy, or route-asset rescue is being treated as the recognized result.

This is a playable state object, not a score screen. The recognized basis decides which faction can certify delivery, claim a route gate, demand payment, request correction, or use replay-derived proof in a later branch.

Entry

Create or update this card only from state pressure:

entry_required:
  trigger_kind: state_pressure
  source_result_exists: true
  source_result_can_be_counted_more_than_one_way: true
  recognition_claimants_min: 2
  future_route_or_counter_can_change: true
  no_fixed_turn_trigger: true

Required row shape

recognized_basis_row:
  basis_id: <stable id>
  source_surface: <storyline rite event card replay source or in-world proof>
  source_result_kept_true: <what really happened>
  basis_claimant: sponsor | archive | inspector | fan_public | editor | artist | handler_staff | producer | route_asset_holder | equivalent
  basis_kind: contract_delivery | lawful_certification | public_receipt | archive_canon | edit_checksum | memorial_copy | route_asset_use | settlement_basis | equivalent
  demanded_recognition: <what must count>
  proof_anchor_or_absence: <receipt seal checksum voice proof ledger row replay-derived proof or explicit_absence>
  excluded_reader: <who becomes harmed or invisible if this basis wins>
  payable_or_gate_created: <certification route gate reserve correction right or default right>
  default_if_unanswered: misrecognized | sponsor_booked | archive_sealed | public_only | lawful_only | disputed | route_gate_hardened | recovery_only | equivalent

Claimant families

• Sponsor basis: counts the result as delivered or ready for commercial harvest; reduces immediate budget pressure while increasing contract capture or public distrust.
• Archive or inspector basis: counts the result as lawfully certified; reduces lawful pressure while increasing archive debt or public resentment.
• Fan/public basis: counts the result as public receipt or queue proof; increases public legitimacy while raising sponsor or inspection pressure.
• Editor/checksum basis: counts a cut, checksum, or patched copy as the artifact; improves continuity while raising source ambiguity.
• Artist, handler, or route-asset basis: counts survival, refusal, recovery, safe custody, or follow-up use as the result; protects a route while raising schedule, burden, or contract pressure.

State machine

State	Meaning	Required consequence
unseen	Source result exists but no recognition dispute is surfaced.	No branch may depend on the basis yet.
offered	At least two basis rows are visible.	Player can recognize, split, defer, re-audit, or refuse.
recognized	One basis counts for a channel.	A certification, payment claim, route gate, correction right, or route effect changes.
split_basis	Different channels count different versions.	Source ambiguity, claimant collision, or later arbitration is armed.
escrowed	Recognition is delayed into a reserve.	Relief is limited and default pressure narrows by state, not by turn count.
misrecognized	A wrong basis is booked.	The excluded reader or route asset gains hostile, costlier, or recovery-only pressure.
default_booked	A claimant counted first while the producer did not resolve the row.	A default event must fire or be recorded.

Counter contract

Resolving a row must mutate at least three durable surfaces:

• recognition state: basis_state, recognized_channel, basis_split, or basis_escrow;
• relief: budget_pressure, lawful_buffer, public_receipt_legitimacy, edit_lane_credit, route_asset_pressure, or equivalent;
• cost: contract_capture, archive_debt, inspection_heat, fan_oxygen_resentment, source_ambiguity, handler_burden, excluded_reader_hostility, or equivalent.

Non-goals

• Not a money score.
• Not a passive accounting screen.
• Not a governance page.
• Not a fixed-turn reconciliation step.
• Not a clean retcon.
• Not valid unless recognition changes future playable state.