Basis Escrow Maturity Receipt

Basis Escrow Maturity Receipt opens when a recognized-basis escrow row matures, breaches, is released, or is cited as complete by a later reader.

Recognized Basis Escrow Triage already makes pending recognition carry a burden, carrier, maturity condition, breach condition, and harmed reader. The remaining gap is the later handoff. A desk can still treat maturity condition reached as if the pending basis became clean recognition for every reader.

This storyline makes maturity itself a receipt. The source basis row stays true, but the game must prove what matured, who carried it, who was released or harmed, and which future reader can consume the result.

Playable Question

When a basis escrow matures or breaches, does production certify a matured basis, release the carrier with receipt, split maturity by reader, reopen the basis hearing, convert the burden into capacity or appeal residue, quarantine the maturity claim, or let a false maturity default harden?

Every answer must name source escrow row, source basis row, maturity or breach condition, burden carrier, requested matured use, future reader, harmed or excluded reader, proof or release receipt, selected posture, maturity state after, basis state after, and future route effect.

Entry

Open this storyline only from live state pressure:

entry_state:
  trigger_kind: state_pressure
  source_basis_escrow_row_visible: true
  source_basis_row_visible: true
  maturity_or_breach_condition_reached_visible: true
  burden_carrier_or_explicit_absence_visible: true
  requested_matured_use_visible: true
  future_reader_consumes_maturity_state: true
  harmed_or_excluded_reader_visible_or_explicit_absence: true
  player_can_certify_release_split_reopen_quarantine_or_default: true
  no_fixed_turn_trigger: true
  no_fixed_day_or_week_trigger: true
  no_raw_maturity_count_trigger: true
  no_dashboard_or_lens_health_trigger: true

Invalid entry includes a raw count of escrow rows, a calendar maturity reminder, a dashboard flag, or a maturity condition with no future reader trying to use it.

Bound Content

Storyline Spine

Beat 1 - A pending basis reaches a condition

The source escrow row may mature because proof arrived, a reader objected, a sponsor called makegood, an appeal stay was consumed, an oxygen claim matured, a capacity row became needed, or a route asset demanded release. The condition can also breach.

Beat 2 - The maturity docket separates condition from recognition

Create Basis Escrow Maturity Docket. The docket must preserve:

  • source basis escrow row;
  • source basis row;
  • maturity or breach condition;
  • burden carrier or explicit absence;
  • requested matured use;
  • future reader;
  • harmed or excluded reader;
  • proof or release receipt;
  • selected maturity posture;
  • after-state and future effect.

Beat 3 - Review prices the handoff

Run Basis Escrow Maturity Review. Matured escrow can become usable, but only inside the named scope. A sponsor-carried maturity cannot become public proof for free; a lawful hold cannot become fan consent; a route pledge cannot become clean release while the carrier remains unpaid.

Beat 4 - Future play reads maturity state

Later content consumes maturity_state_after, not condition reached. A basis can be recognized, released, split, reopened, converted, quarantined, or recovery-only. That after-state must drive future reader acceptance.

Branches

BranchReliefCost or scarFuture state
certify_matured_basisnamed reader can use the matured basissource scope and proof remain visibleaccepted-with-maturity or costlier
release_carrier_with_receiptcarrier is released from the burdenrelease proof, compensation, or debt remainscarrier-released or release-addendum-required
split_maturity_by_readerincompatible readers stop overwriting itsplit upkeep and contradiction cost risepublic-only, lawful-only, sponsor-only, or split
reopen_basis_hearingweak maturity cannot file firsthearing delay, proof burden, or schedule risesrehearing-required or basis-disputed
convert_to_capacity_or_appealunresolved burden moves to a fitting lanecapacity, appeal, or oxygen pressure risescapacity-bound, appeal-residue, or bridge-needed
quarantine_maturity_claimfalse clean maturity is blockedcurrent route loses shortcutblocked, quarantined, or recovery-only
false_basis_maturity_defaultfastest desk files maturity as proofhidden carrier or harmed-reader scar hardenshostile, costlier, sponsor-only, or recovery-only

Every non-default branch must mutate one relief surface, one cost surface, and one future reader or route effect.

Default

If later play consumes matured basis state without source escrow row, source basis row, maturity or breach condition, burden carrier, requested use, harmed reader, release proof, or future effect, False Basis Maturity Default fires or arms.

false_basis_maturity_default:
  false_clean_maturity_claim: true
  source_escrow_row_or_absence: <escrow row id or explicit_absence>
  hidden_or_invalid_maturity_scope: source_hidden | condition_hidden | carrier_hidden | proof_absent | harmed_reader_hidden | overbroad_maturity | release_unpaid | equivalent
  capturing_reader: sponsor | public | lawful_reader | archive | inspector | editor | route_asset | management | broadcast_reality | equivalent
  harmed_or_excluded_reader: <reader route claimant or explicit_absence>
  maturity_state_after: false_clean_matured | carrier_unreleased | sponsor_only | public_only | lawful_only | split_required | quarantined | blocked | recovery_only
  future_reader_effect: recognition_polluted | carrier_claim_reopens | capacity_costlier | appeal_reopened | route_asset_hostile | lawful_addendum_due | public_audit_required | recovery_only
  counter_deltas_min: 3
  durable_mutation: true

Non-Goals

  • Not a second recognition hearing.
  • Not a replacement for Recognized Basis Escrow Triage.
  • Not an archive-index afteruse packet.
  • Not valid when maturity is only a date, UI label, or raw pending count.