Enforcement Mandate Exhaustion / 执行授权枯竭线

This conditional storyline begins after Storyteller has already created more than one valid enforcement obligation. It is the pressure where the producer learns that winning several hearings does not create enough hands, seals, slots, public windows, editor lanes, or protected carriers to execute them all cleanly.

It deepens Post-Ruling Enforcement Week Storyline, 归档执行案卷, 认领撞锁, 播出合法性转轨线, and 举证负荷再分配线 without adding a new verdict. The dramatic question is: which already-valid order receives live mandate, and who becomes dangerous because their order was left unserved?

Enable condition

Enable this storyline from state only when all of the following are true:

enable_condition:
  enforceable_rows_min: 2
  shared_capacity_dimension_present: true
  source_relief_and_source_debt_visible: true
  at_least_two_claimant_families_live: true
  no_fixed_turn_trigger: true

Valid source rows include:

• an archive order that still needs service, proof, carrier, stay, or compliance;
• a claimant collision outcome that split, quarantined, captured, or prioritized a route asset;
• a broadcast legality conversion that made an asset usable only in one channel;
• a proof-burden reassignment row that changed who must prove or disprove;
• a cutroom priority row that stabilized one edit by starving another proof lane;
• a broadcast insolvency row that borrowed capacity from another claimant;
• a route asset custody row whose carrier, witness, permit, memorial copy, voice copy, or public receipt can be captured.

Core cast pressure

This storyline should usually put at least three authority styles in collision:

• formal inspector or archive service wants a clean order served;
• sponsor or manager pressure wants the order delayed, narrowed, or packaged;
• editor or black-box custody wants the order patched into continuity;
• public/fan/historian pressure wants the order witnessed publicly;
• artist, witness, runner, or route asset custody wants protection before reuse.

No authority style is allowed to be a free universal answer.

Play sequence

1. Mandate ledger appears

The player receives an enforcement mandate ledger summarizing at least two live rows. Each row shows the source relief that remains true, the debt still live, the needed mandate, the harmed claimant if prioritized, the harmed claimant if left unserved, and the future route effect.

Example rows:

rows:
  - row_id: archive_refusal_order
    source_relief_kept_true: [artist_refusal_recognized]
    source_debt_still_live: [sponsor_stop_loss_pressure]
    needed_mandate: inspector_service
    harmed_if_left_unserved: artist_or_public_witness
  - row_id: public_counter_receipt
    source_relief_kept_true: [public_receipt_legitimacy_up]
    source_debt_still_live: [inspection_heat]
    needed_mandate: public_receipt_window
    harmed_if_prioritized: sponsor_or_archive

2. Triage asks for a sacrifice

The playable rite must not ask only “which order succeeds?” It must also ask which order is explicitly left unserved, split, borrowed against, quarantined, or converted into recovery-only pressure.

Required assignment families:

• one ledger;
• one or more priority rows;
• one shared mandate pool;
• one actor, proof, carrier, public anchor, editor lane, sponsor bridge, or explicit absence;
• one sacrificed or deferred row;
• one cost or bridge.

3. The chosen mandate changes future access

A successful triage branch must change at least one later offer or acceptance rule:

• a formal route accepts the served order but a public route becomes costlier;
• a public route accepts the receipt but lawful use requires conversion;
• an editor route accepts the patched copy but raw-proof use is blocked;
• a sponsor route accepts the package but artist/public routes gain distrust;
• a quarantine protects the chain but blocks immediate use;
• a split mandate creates two copies with different future rights.

4. The unserved side responds

The unserved row must create a real future problem. It can become stale, counterfeited, captured, hostile, public-only, lawful-only, editor-only, sponsor-only, blacked out, or recovery-only. A route asset, witness, carrier, follower, artist boundary, public receipt, or black-box copy should be the visible body of the failure whenever possible.

Branch families

Branch A — Serve the formal order

Assign inspector/archive service, legal slot, seal, or custody proof.

Expected outcome:

• selected row becomes mandate_assigned, served, or complied;
• archive signature legitimacy, custody clarity, or lawful acceptance improves;
• unserved public, sponsor, editor, fan, witness, or route-asset pressure rises.

Branch B — Publish the enforcement gap

Assign historian, fan queue, public receipt, pirate relay, artist boundary, or public witness.

Expected outcome:

• public receipt legitimacy or witness pressure improves;
• sponsor pressure, inspection heat, pirate exposure, or lawful conversion cost rises;
• at least one future formal use becomes blocked or costlier until converted.

Branch C — Patch the order through cutroom

Assign editor custody, checksum, black-box fragment, redaction, or continuity patch.

Expected outcome:

• continuity hazard, route legibility, or audience stability improves;
• source ambiguity, edit debt, archive debt, or public distrust rises;
• raw-proof or public route use is narrowed.

Branch D — Borrow sponsor bridge

Assign manager/sponsor settlement, stop-loss bridge, naming-right clause, or schedule relief.

Expected outcome:

• immediate sponsor or schedule pressure drops;
• contract capture, public distrust, artist boundary risk, or recovery cost rises;
• a route asset may become sponsor-gated.

Branch E — Split mandate

Assign one finite mandate to two rows and accept partial service.

Expected outcome:

• both rows receive limited relief;
• neither row becomes clean universal success;
• route copies, legal classes, or public/formal acceptances diverge.

Branch F — Quarantine or blackout the mandate

Refuse execution because every available bridge would create false compliance.

Expected outcome:

• contempt, counterfeit, false-owner, or voice/body risk decreases;
• schedule, audience, sponsor, fan, or route access pressure rises;
• a future recovery action remains possible.

Branch G — Overdraw the mandate

Reuse the same authority, seal, public window, or carrier as if it could satisfy all rows.

Expected outcome:

• breach event fires or becomes armed;
• one row becomes stale, counterfeit_compliance, hostile_capture, mandate_default, or recovery_only;
• a visible asset or follower becomes harder to use later.

Counters and states

Suggested state keys:

• mandate_capacity
• mandate_overdraw
• enforcement_backlog
• source_relief_kept_true
• source_debt_still_live
• archive_signature_legitimacy
• custody_gap
• inspection_heat
• sponsor_stop_loss_pressure
• contract_capture
• edit_debt
• source_ambiguity
• public_receipt_legitimacy
• public_receipt_distrust
• fan_oxygen_resentment
• artist_boundary_risk
• witness_exposure
• field_carrier_risk
• route_asset_pressure
• future_recovery_cost
• black_screen_pressure

Failure states

Durable failure should use specific states rather than generic loss:

• mandate_left_unserved
• mandate_stale
• mandate_counterfeit_compliance
• mandate_hostile_capture
• mandate_recovery_only
• public_receipt_lawful_mismatch
• editor_patch_raw_proof_blocked
• sponsor_gate_hardened
• field_carrier_sacrificed
• witness_unprotected_after_service
• route_asset_enforcement_captured

Non-goals

• Not a new court case.
• Not raw lens-count satisfaction.
• Not a fixed turn or week trigger.
• Not a generic difficulty escalation.
• Not a governance page.
• Not a global cleanup for all post-ruling debt.
• Not valid unless the sacrificed or unserved row has future consequences.