Faction Commitment Ledger Lens / 派系承诺账本 Lens

Primary observation link

This lens observes 派系承诺账本, 派系承诺账本机制, Route Assets and Custody, Oxygen Claim Exchange Storyline, 归档执行案卷, 和解反震账本, and 认领撞锁.

It is observed through 派系承诺账本, 派系承诺听证, and 派系过度承诺破口.

Observable promise

Storyteller factions must spend finite leverage when they pressure a contested broadcast surface.

A pass cannot be achieved by giving sponsors, inspectors, fans, archives, editors, or pirate relays unlimited recurring pressure. A faction must declare what it commits, what control it demands, what proof anchors the demand, and what future posture changes if the commitment is accepted, split, frozen, countered, overcommitted, exhausted, or ignored.

This lens exists to make mid/late-game management pressure playable without adding filler crises or fixed turn-count triggers.

Scope

This lens covers:

• contested surfaces produced by oxygen exchange, archive enforcement, settlement aftershock, claimant collision, route-asset custody, public receipt, memorial right, witness payroll, edit custody, audience-stability scar, or equivalent;
• sponsor escrow, inspector lien, fan oxygen commitment, archive priority claim, editor cutroom hold, pirate relay pledge, and management bridge commitments;
• a ledger card that records claimant rows and spend state;
• an assignable hearing rite that forces ledger, claimant, counterweight, handler, and price slots;
• overcommitment and silent-capture consequences that mutate faction posture and future route costs.

It does not cover generic faction reputation or ambient pressure unless a concrete commitment row is visible.

State-triggered entry oracle

A valid replay or state inspection must open this lens from live commitment state, not from a fixed sequence. Minimum entry evidence:

1. a contested asset, ledger, docket, public receipt, oxygen row, settlement aftershock, archive order, route asset, witness, memorial right, edit contradiction, or audience scar exists;
2. at least two faction claimants can act on the surface, or one declared commitment has a plausible counterclaim;
3. at least one claimant row has a concrete reserve: escrow, lien, oxygen queue, edit hours, archive seal, legal threat, public vigil, silence retainer, seizure team, relay attention, or equivalent;
4. the player can choose acceptance, split, freeze, public countercommitment, baited overcommitment, or default;
5. the surface has not reached terminal settlement, terminal seizure, final public discharge, irreversible route lock, or clean disappearance.

Accepted source states include claim_window_open, archive_order_served, aftershock_unreviewed, commitment_declared, counter_commitment_open, public_receipt_contested, route_asset_claimed, witness_payroll_due, memorial_right_contested, edit_custody_contradiction, or equivalent.

Required observable content

Ledger card

派系承诺账本 or equivalent must record:

• contested surface id;
• source storyline or branch family;
• source session id and seed when available;
• at least one claimant row;
• faction identity and named actor when available;
• commitment type;
• offered relief;
• demanded control;
• spend state;
• proof anchor or explicit absence;
• current ledger state.

A ledger fails if it only says a faction is angry, supportive, or interested without recording what leverage was committed.

Assignable hearing rite

派系承诺听证 or equivalent must assign:

• one ledger or equivalent commitment state;
• one primary claimant or explicit claimant absence;
• one counterweight proof or explicit absence;
• one handler or explicit absence;
• one price, bridge, cost, or explicit no-price failure.

A hearing fails if a famous handler can erase faction pressure without a committed claimant row or counterweight.

Overcommit breach event

派系过度承诺破口 or equivalent must fire, resolve, or be recorded when a faction’s commitment becomes excessive, exposed, contradicted, or dishonestly captured.

The event must mutate a counter, faction posture, route asset state, future route availability, claimant hostility, schedule cost, or broadcast reality state. It cannot be mood text.

Required route states

A satisfying implementation must expose durable states equivalent to at least eight of:

• commitment_unopened
• commitment_declared
• counter_commitment_open
• commitment_accepted
• commitment_split
• commitment_frozen
• public_countercommitment
• faction_overcommitted
• faction_exhausted
• coalition_formed
• silent_capture
• faction_hostile

Branch divergence oracle

Branch A — Accept one faction commitment

Expected evidence:

• one claimant row is accepted;
• accepted row names faction, commitment type, offered relief, demanded control, and proof anchor;
• one immediate pressure improves;
• at least one rival faction posture, custody debt, public distrust, route cost, or future capture risk worsens.

Branch B — Split commitment between factions

Expected evidence:

• at least two claimant rows remain live;
• proof, payment, custody, publication, or route use is divided;
• one collapse, breach, or stop-loss surface may improve;
• ambiguity, aftershock, false-owner risk, public distrust, fan resentment, archive debt, or future fraud cost persists or rises.

Branch C — Freeze commitment under proof or quarantine

Expected evidence:

• hearing assigns audit proof, public proof, edit checksum, quarantine, archive copy, or equivalent counterweight;
• outcome sets commitment_frozen, audit_freeze, proof_hold, or equivalent;
• fraud, drift, false-owner pressure, or custody gap may improve;
• schedule pressure, audience churn, fan resentment, sponsor objection, or bureau favor debt rises.

Branch D — Public countercommitment

Expected evidence:

• public receipt, fan oxygen, Yu Lan, witness chain, pirate relay, or unauthorized history is assigned as counterweight or handler;
• outcome sets public_countercommitment, fan_queue_committed, counter_commitment_open, or equivalent;
• public receipt legitimacy, fan oxygen balance, audience stability, or public grief stability improves;
• sponsor stop-loss, inspection heat, witness retaliation risk, pirate exposure, or route asset pressure rises.

Branch E — Bait overcommitment

Expected evidence:

• a faction spends a concrete reserve into a contested surface;
• counterproof, incompatible promise, rival claim, or route asset state makes the commitment excessive;
• outcome sets faction_overcommitted, faction_exhausted, or equivalent;
• 派系过度承诺破口 or equivalent fires or is recorded;
• future clean pressure from that faction is blocked, costlier, delayed, hostile, or coalition-bound.

Branch F — Default into silent capture, coalition, or hostility

Expected evidence:

• no credible ledger, handler, price, counterweight, or public proof is recorded, or the player hides the surface;
• outcome sets silent_capture, coalition_formed, faction_hostile, commitment_default, or equivalent;
• one faction’s control hardens or two factions combine pressure;
• future route access becomes blocked, costlier, hostile, captured, or recovery-only;
• at least three relevant counters or durable states change.

Oracle assertions

A binding check should fail unless all assertions below are true.

1. Primary links exist — the lens has populated observes and observed_through arrays pointing to concrete Storyteller pages.
2. Entry is state-triggered — the surface opens from live commitment state, not fixed turn count.
3. Finite commitment exists — at least one faction row records what reserve was committed.
4. Demanded control exists — a commitment records what custody, wording, route access, proof control, public naming, or future claim it wants.
5. Counterweight exists or absence is explicit — the hearing records proof, public receipt, audit seal, fan queue, edit checksum, witness, route asset, or explicit absence.
6. Price exists or absence is explicit — the hearing records money, lien, public apology, edit hours, custody seal, oxygen refund, schedule scar, route asset exposure, or explicit no-price failure.
7. At least four branch families are playable — accept, split, freeze, public countercommitment, bait overcommitment, and default must not collapse into one result.
8. No infinite faction pressure — a faction that repeatedly pressures the same surface must spend a new reserve, reuse an unresolved row, become exhausted, or change posture.
9. Costed success — every accepted or split commitment improves one surface while worsening or spending another.
10. Overcommitment is visible — baited overcommitment or exposed contradiction changes event history, faction posture, route availability, or future cost.
11. Silent capture is durable — ignoring commitment can harden wrong ownership, private control, coalition pressure, or recovery-only route access.
12. Replay provenance survives — evidence can show the contested surface source, claimant rows, assignments, branch, deltas, and future route effects.

Progress metric

factionCommitmentLedgerProgress = 0..9:

• 0: no contested surface with faction commitment.
• 1: contested surface exists and at least two factions can claim it.
• 2: 派系承诺账本 or equivalent exists.
• 3: at least one claimant row records faction, commitment type, offered relief, demanded control, and spend state.
• 4: at least one counterclaim, counterweight, or explicit absence is visible.
• 5: 派系承诺听证 or equivalent offers ledger, claimant, counterweight, handler, and price slots.
• 6: at least three branch choices are visible and gated by assigned claimant rows or counterweights.
• 7: at least two successful branches produce distinct ledger states and at least three deltas.
• 8: overcommitment, silent capture, coalition, or hostility creates durable future cost or route change.
• 9: replay evidence proves source contested surface, claimant rows, assigned slots, branch choice, deltas, and future route effects.

Evidence shape

lens_id: storyteller.lens.faction_commitment_ledger.v1
session_id: lens-faction-commitment-ledger-v1-<timestamp>
seed: <deterministic-seed>
source_surface:
  source_session_id: <session_that_created_the_contested_surface_if_available>
  source_seed: <source_seed_if_available>
  source_storyline: oxygen_claim_exchange | archive_enforcement_docket | settlement_aftershock_ledger | claimant_collision_lock | route_assets_and_custody | equivalent
  contested_surface: <asset_or_ledger_id>
  state_before_commitment: <state>
ledger:
  card: card.faction_commitment_ledger
  ledger_state_before: commitment_unopened | commitment_declared | counter_commitment_open | equivalent
  claimant_rows:
    - faction: sponsor | inspector | fan_public | archive | editor | pirate | management | equivalent
      named_actor: <actor_or_absent>
      commitment_type: escrow | lien | oxygen_queue | edit_hours | archive_seal | legal_threat | public_vigil | silence_retainer | seizure_team | relay_attention | equivalent
      offered_relief: <state_or_counter>
      demanded_control: <custody_or_route_claim>
      spend_state: declared | invited | accepted | countered | split | frozen | overcommitted | exhausted | hostile | withdrawn
      proof_anchor: <receipt_or_docket_or_witness_or_explicit_absence>
assigned_hearing:
  rite: storyteller.rite.faction_commitment_hearing.v1
  ledger: card.faction_commitment_ledger
  primary_claimant: <faction_or_absent>
  counterweight: <proof_or_absent>
  handler: <handler_or_absent>
  price_or_bridge: <cost_or_absent>
branch_runs:
  accept_commitment:
    outcome: commitment_accepted
    counter_deltas: {}
    faction_postures: {}
  split_commitment:
    outcome: commitment_split
    counter_deltas: {}
    faction_postures: {}
  freeze_commitment:
    outcome: commitment_frozen
    counter_deltas: {}
    faction_postures: {}
  public_countercommitment:
    outcome: public_countercommitment
    counter_deltas: {}
    faction_postures: {}
  bait_overcommitment:
    outcome: faction_overcommitted
    events:
      - event.faction_overcommit_break
    counter_deltas: {}
    faction_postures: {}
  default_or_capture:
    outcome: silent_capture | coalition_formed | faction_hostile | equivalent
    counter_deltas: {}
    faction_postures: {}
future_route_effects:
  unlocked: []
  blocked_or_costlier: []
assertions:
  - commitment rows record finite leverage
  - branches do not collapse into clean universal appeasement
  - success has visible cost
  - overcommitment or default changes future route pressure
  - evidence comes from game CLI replay/session history

Anti-regression notes

• Do not satisfy this lens with raw faction count.
• Do not satisfy it with a static faction reputation page.
• Do not trigger it from a fixed numbered turn.
• Do not let a faction repeatedly apply the same pressure without spend state, exhaustion, coalition, hostility, or new reserve.
• Do not let a famous handler solve every faction row without ledger, counterweight, and price.

Non-goals

• Not a global economy simulator.
• Not filler escalation.
• Not governance or dashboard process.
• Not a universal negotiation minigame.
• Not a clean all-faction compromise.
• Not handwritten replay evidence; executable bindings should use durable game-CLI state, session id, assignments, outcomes, counter deltas, and future route effects.