Recognized Broadcast Basis / 播出确认基准机制

Recognized Broadcast Basis is the mechanism for making corporate, public, lawful, editor, and route-asset recognition disagree after a result has already happened.

The current mesh can already make success scarce through dividend allocation, unpaid debt, legality conversion, claimant conversion, replay carryover, and route-asset custody. The missing pressure is narrower: which version of the result is allowed to count. If that basis is not stateful, management can report a clean outcome while the sponsor, archive, fans, cutroom, and route assets each rely on incompatible evidence.

Core rule

A recognized basis exists only when a prior result remains true but has multiple valid or contested counting channels.

basis_valid_when:
  source_result_kept_true: true
  recognition_channels_min: 2
  basis_rows_visible: true
  claimant_or_excluded_reader_present: true
  future_route_or_counter_can_change: true
  no_fixed_turn_trigger: true

The mechanism is invalid if it merely lowers a pressure number, pays a reward, or labels a result complete without a basis row and future consequence.

Recognition channels

A result may be recognized through one or more channels:

• sponsor_basis: contract delivery, commercial harvest, stop-loss relief, slot package.
• lawful_basis: archive seal, inspector certification, legal channel, lawful-only route.
• public_basis: fan receipt, oxygen queue proof, public correction, memorial acceptance.
• editor_basis: checksum, final cut, black-box output, continuity patch.
• route_asset_basis: protected use, survivor testimony, staff/handler custody, safe follow-up assignment.
• producer_reserve_basis: delayed recognition held as a resource with named excluded claimant.

A channel must have a proof anchor or explicit absence. Replay-derived evidence may support a basis only when it is embedded in-world as a receipt, copy, checksum, witness row, ledger row, route asset, or docket.

State machine

State	Meaning	Required consequence
unseen	A source result exists but no recognition dispute is exposed.	No future branch may use recognition yet.
basis_offered	recognized-basis-ledger has at least two rows.	basis-recognition-hearing must be offerable or explicitly blocked.
recognized_single	One channel counts as official.	That channel gains relief; a rival or excluded reader gains cost.
split_basis	Channels count different versions.	Future use must name channel and source ambiguity or collision rises.
escrowed_basis	Recognition is held pending proof or claimant response.	Immediate relief is partial and state-driven default pressure is armed.
reaudit_open	Proof is assigned to contest the basis.	Inspection, schedule, burden, or exposure pressure rises.
misrecognized	A wrong or private basis is booked.	misrecognized-basis-default mutates future route state.
recovery_only_basis	Recognition can only be repaired through a scarred route.	Clean certification, clean sponsor payment, or clean public receipt is blocked.

Branch contract

Every branch must preserve the source result. The mechanism changes recognition and future acceptance, not what happened.

Recognize single basis

• Relief: selected channel becomes usable.
• Cost: excluded reader, rival channel, or route asset gains debt, hostility, ambiguity, burden, or narrower access.
• Future: later rites must check the recognized channel.

Split basis

• Relief: two or more channels gain weaker use.
• Cost: source_ambiguity, claimant_collision, archive_debt, public_receipt_distrust, or future_arbitration rises.
• Future: clean use requires selecting channel or reconciling the split.

Escrow basis

• Relief: immediate false booking is delayed.
• Cost: resource, schedule, pressure, or excluded-reader resentment rises.
• Future: if proof, claimant, or route asset moves first, default booking can occur.

Force re-audit

• Relief: false basis pressure decreases.
• Cost: inspection heat, handler burden, source exposure, or schedule pressure rises.
• Future: a later branch must consume the re-audit result.

Refuse recognition

• Relief: the player blocks a bad basis from becoming official.
• Cost: budget, sponsor, public, lawful, or route pressure rises now.
• Future: affected route may become public-only, lawful-only, disputed, or recovery-only.

Let default book

• Relief: none required, although a faction may get short-term advantage.
• Cost: a claimant counts the result first.
• Future: misrecognized-basis-default fires or is armed.

Counter surfaces

Use at least three durable surfaces per resolved branch:

• basis_state
• recognized_channel
• basis_split
• basis_escrow
• basis_reaudit_open
• excluded_reader_hostility
• budget_pressure
• sponsor_stop_loss_pressure
• contract_capture
• lawful_buffer
• inspection_heat
• bureau_favor_debt
• archive_debt
• public_receipt_legitimacy
• public_receipt_distrust
• fan_oxygen_resentment
• edit_lane_credit
• edit_debt
• source_ambiguity
• handler_burden
• route_asset_pressure
• future_route_acceptance
• recovery_route_cost

Integration rules

• With 播出合约回读线, a contract clause can demand a basis, but cannot erase public, archive, or route-asset disagreement.
• With 播出盈余认领线, a dividend cannot be allocated until the source result has a countable basis or an explicit split/escrow state.
• With 播出破产账本线, a misrecognized basis can become a payable promise or disputed creditor row.
• With 播出合法性转轨线, lawful recognition can narrow public or sponsor use instead of cleaning all channels.
• With 导出证据回流分岔线, replay provenance supports recognition only as an in-world proof object.
• With Route Assets and Custody, a route asset can be protected by one basis and endangered by another.

Replay evidence shape

mechanic_id: storyteller.mechanic.recognized_broadcast_basis.v1
session_id: lens-storyteller-recognized-broadcast-basis-v1-<timestamp>
seed: <deterministic-seed>
source_result:
  source_surface: <source>
  source_session_id: <session or explicit_absence>
  source_result_kept_true: <result>
entry_state:
  trigger_kind: state_pressure
  recognized_basis_ledger: storyteller.card.recognized_basis_ledger.v1
  basis_rows_min: 2
  proof_anchor_or_absence_visible: true
  excluded_reader_visible: true
  future_effect_if_unanswered_present: true
  no_fixed_turn_trigger: true
hearing:
  offered_rite: storyteller.rite.basis_recognition_hearing.v1
  selected_response: recognize_single_basis | split_basis | escrow_basis | force_reaudit | refuse_recognition | let_default_book
  assigned_inputs:
    basis_row: <basis id>
    proof_anchor_or_absence: <proof or explicit_absence>
    handler_or_absence: <handler or explicit_absence>
    support_or_absence: <support or explicit_absence>
outcome:
  basis_state_after: recognized_single | split_basis | escrowed_basis | reaudit_open | misrecognized | recovery_only_basis
  recognized_channel: <channel or none>
  excluded_reader_effect: <effect>
  future_route_effect: <effect>
  emitted_event: storyteller.event.misrecognized_basis_default.v1 | none
counter_deltas:
  relief:
    - <relief>
  cost:
    - <cost>

Non-goals

• Not a financial dashboard.
• Not a governance or implementation methodology page.
• Not a generic success state.
• Not a fixed-turn, fixed-day, chapter, or count trigger.
• Not a clean retcon.
• Not valid unless recognition state, claimant/excluded-reader state, and future playable state all change.