Recognized Basis Escrow Triage / 确认基准暂存分诊线

Recognized Basis Escrow Triage is the storyline for the moment after a recognition dispute has been escrowed, split, refused, or left recovery-only, but before a later reader spends that pending state.

The playable question is: who pays to keep an unresolved basis from becoming somebody else’s default?

Why this expansion is useful now

The current mesh already has strong local answers:

The gap is the seam between them: escrow in recognized-basis play can otherwise look like a cheap postponement. This storyline makes escrow a management decision with a carrier, harmed reader, maturity condition, and default.

Bound content pack

  • 确认基准暂存分诊机制 defines reserve surfaces, state transitions, branch families, counters, and default rules.
  • 基准暂存负担案卷 stores source basis row, future reader, reserve surface, carrier, harmed reader, maturity, breach, and future route effect.
  • 基准暂存分诊 lets the player fund escrow, split burden, post public notice, accept sponsor surety, hold lawfully, pledge a route asset, force immediate basis, abandon burden, or default.
  • 未供资基准暂存默认 hardens when the escrow burden is hidden, unfunded, double-spent, breached, or filed as universal recognition.

State-triggered entry

Open this storyline only when all are true:

entry_required:
  trigger_kind: state_pressure
  source_basis_ledger_present: true
  source_basis_row_present: true
  source_result_kept_true: true
  basis_state_before_any:
    - escrowed
    - split_basis
    - disputed
    - recognition_refused
    - recovery_only_basis
  pending_future_reader_present: true
  reserve_surface_candidates_present_or_explicit_absence: true
  player_can_assign_or_default: true
  future_route_or_reader_can_change: true
  no_fixed_turn_trigger: true
  no_fixed_day_or_week_trigger: true
  no_raw_pending_row_count_trigger: true
  no_dashboard_or_lens_health_trigger: true

Do not open it from numbered turns, day/week intervals, chapter cleanup, raw row counts, dashboard health, or generic late-game pacing.

Storyline spine

Beat 1 — A basis is held, but not paid for

The prior recognition dispute leaves a source basis row in escrow, split, disputed, refused, or recovery-only state. The result still happened. The problem is that a later sponsor, public, lawful, archive, editor, fan, route, or broadcast reader is about to consume the unresolved basis.

Beat 2 — The burden docket names the carrier

The player receives 基准暂存负担案卷. It must name:

  • source basis row;
  • future reader;
  • protected reader or route;
  • harmed reader or route;
  • reserve surface;
  • carrier or explicit absence;
  • proof/receipt/absence;
  • maturity condition;
  • breach condition;
  • default actor;
  • future route effect.

Beat 3 — The producer selects a burden posture

基准暂存分诊 offers at least five constructive branch families plus default or explicitly blocked state.

Valid postures include:

  • fund escrow with a concrete reserve;
  • split burden across two reader channels;
  • post public notice or fan oxygen bond;
  • accept sponsor surety;
  • hold lawfully through proof/archive window;
  • pledge a route asset, witness, carrier, or handler;
  • force immediate basis and end the escrow;
  • abandon burden or accept default.

Beat 4 — The future reader inherits the scar

Each branch must change the future reader or route. A sponsor surety may keep the broadcast alive but narrows later use to sponsor-only. A public notice bond may improve legitimacy but arms sponsor or lawful challenge. A route asset pledge may preserve a bridge but demands later release or becomes hostile.

Beat 5 — Unfunded escrow defaults

If the burden row is missing, the carrier is absent, the reserve is double-spent, the harmed reader is hidden, or the reserve is filed as universal basis, 未供资基准暂存默认 books the fastest claim and mutates future play.

Branch map

BranchReliefCost/scarFuture state
Fund escrowdefault pressure down; chosen reader protectedreserve surface occupied; budget/capacity/burden risesmaturity condition checked later
Split burdenuniversal false basis blockedambiguity, handler burden, or reconciliation cost risesfuture use must name channel
Public notice bondpublic receipt or fan oxygen legitimacy improvessponsor/lawful pressure, audit heat, or oxygen liability risespublic-only, public-audit-required, or split-required
Sponsor suretybudget or stop-loss pressure fallssponsor capture, public distrust, or contract capture risessponsor-only unless unwound
Lawful holdcertification or archive clarity improvespublic, artist, route, or sponsor pressure riseslawful-only, bridge-required, or rehearing-required
Route asset pledgeroute bridge survivesroute pressure, capture risk, handler burden, or release debt riseshostile, costlier, or recovery-only if release unpaid
Force immediate basisescrow no longer leaksprotected reader loses reserve; excluded reader explicitrecognized, refused, or recovery-only basis
Abandon/defaultimmediate burden drops or fastest desk files firstdefault actor books false/first claimblocked, costlier, sponsor-only, public-only, lawful-only, recovery-only, or contradiction-pending

Counter contract

Every non-default branch must mutate at least four surfaces:

  • basis_escrow_burden_state;
  • one relief surface;
  • one cost or harmed-reader surface;
  • one future reader or route effect.

Default must mutate at least three surfaces and cannot be only warning text.

Missability and recovery

The storyline is missed or defaults when implementation:

  • treats escrow as clean delay;
  • omits a burden docket;
  • hides carrier, maturity, breach, or harmed reader;
  • files sponsor, public, lawful, appeal, oxygen, capacity, or route reserve as universal recognition;
  • lets a later reader consume pending basis without burden state;
  • triggers by fixed turn, day/week, raw row count, dashboard state, or lens health.

Recovery is allowed only with scar:

  • reopen the burden docket and pay a late reserve;
  • route matured or breached escrow through Basis Escrow Maturity Receipt before any later reader spends maturity as recognition;
  • convert the burden to capacity liability;
  • split sponsor/public/lawful recognition and accept contradiction;
  • attach appeal afteruse residue;
  • refund or publicize fan oxygen exposure;
  • release or compensate a pledged route asset;
  • accept recovery-only use.

Replay evidence expectation

storyline_id: storyteller.storyline.recognized_basis_escrow_triage.v1
session_id: lens-recognized-basis-escrow-triage-v1-<timestamp>
seed: <deterministic-seed>
source_result:
  source_basis_row: <basis id>
  source_result_kept_true: <result>
entry_state:
  trigger_kind: state_pressure
  basis_state_before: escrowed | split_basis | disputed | recognition_refused | recovery_only_basis
  pending_future_reader_present: true
  reserve_surface_candidates_present_or_explicit_absence: true
  no_fixed_turn_trigger: true
offered:
  card: storyteller.card.basis_escrow_burden_docket.v1
  rite: storyteller.rite.basis_escrow_triage.v1
branch_result:
  selected_posture: fund_escrow | split_burden | public_notice_bond | sponsor_surety | lawful_hold | route_asset_pledge | force_immediate_basis | abandon_burden | accept_unfunded_default
  assigned_inputs:
    reserve_surface: <surface>
    carrier_or_absence: <carrier or explicit_absence>
    harmed_reader_or_route: <reader or route>
    maturity_condition: <condition>
    breach_condition: <condition>
  burden_state_after: funded | split | public_bond | sponsor_surety | lawful_hold | route_pledged | immediate_basis | abandoned | defaulted
  future_route_effect: <effect>
  emitted_event: storyteller.event.unfunded_basis_escrow_default.v1 | none
counter_deltas:
  relief: []
  cost: []
  future: []
assertions:
  - source_result_preserved
  - escrow_has_carrier
  - harmed_reader_visible
  - maturity_and_breach_visible
  - branches_diverge
  - default_mutates_future_play
  - no_fixed_turn_trigger

Non-goals

  • Not filler content.
  • Not a passive accounting dashboard.
  • Not governance/process content.
  • Not raw count satisfaction.
  • Not a fixed-turn trigger.
  • Not a clean ending repair.
  • Not valid unless deferred recognition changes future playable state.