Ruling Enforcement Load / 裁定执行负荷线

Ruling Enforcement Load replaces the older enforcement-week framing. The file path remains legacy-compatible, but the canonical storyline is state-triggered operational load, not a week, turn window, day count, or fixed aftermath timer.

A ruling may already be valid. A custody order may already have been served. A proof-burden shift, settlement, legality conversion, public receipt, or archive mandate may already be true. This storyline begins when a later route tries to rely on that result and the game must prove whether its enforcement work was actually carried.

Gap this revision fixes

The surrounding corpus already covers verdicts, mandate exhaustion, attachment compliance, archive enforcement, management compression, claimant intake, live floor load, asset maintenance, handler burden, and faction commitment.

The old gap was described as “post-ruling work over several days.” That phrasing invites turn-count and calendar-window design. The actual game need is sharper:

a valid ruling must not become a clean universal key unless its operational load rows have been assigned, served, protected, and accepted by the future reader.

This storyline makes that load playable.

Primary playable question

When a valid ruling carries unresolved enforcement load, which row does the producer roster, publish, seal, compress, quarantine, protect, or let default — and what future route now accepts, taxes, narrows, captures, or rejects the ruling?

The ruling remains history. The load decides whether history can be used.

State-triggered entry

Open this storyline when all are true:

entry_state:
  trigger_kind: state_pressure
  valid_ruling_or_equivalent_row_present: true
  source_result_not_cleanly_reusable: true
  enforcement_load_row_present_or_expected: true
  load_row_pressure_present: true
  future_reader_reads_ruling: true
  player_can_assign_or_record_explicit_absence: true
  no_fixed_turn_trigger: true
  no_fixed_day_or_week_trigger: true

Valid source results include:

• archive enforcement ruling;
• attachment compliance row;
• enforcement mandate row;
• custody decision;
• public receipt;
• proof-burden shift;
• settlement aftershock row;
• broadcast legality conversion;
• route asset ruling;
• artist refusal boundary;
• sponsor carve-out;
• fan oxygen refund or audit row.

Content pack

Mechanic

• 裁定执行负荷机制 defines load rows, state-triggered entry, branch families, counter contract, default narrators, and replay evidence.

Card

• 裁定执行负荷案卷 stores the source ruling, load rows, obligated parties, required surfaces, carriers, protected boundaries, future readers, and default if unworked.

Rite

• 裁定执行负荷复核 resolves one selected row through lawful roster, public receipt, proof-chain service, sponsor compression, boundary protection, quarantine, or default.

Event

• 执行负荷违约 fires or arms when a future reader uses the ruling while the load row is absent, underfilled, falsely served, or captured.

Storyline spine

Beat 1 — A valid result asks to be reused

A later route, rite, card, claimant row, schedule object, route asset, quote, or public statement attempts to cite a prior ruling.

The player does not re-litigate the old result. The game names it and asks what enforcement load it still carries.

Beat 2 — The docket creates load rows

Ruling Enforcement Load Docket enters play or updates. It must name at least one row that a later route reads.

Strong examples:

load_rows:
  - row_id: archive_notice_missing
    load_kind: notice
    source_ruling_or_row: archive_order_A
    required_surface: public
    carrier_or_authority: explicit_absence
    protected_boundary: claimant_row_B
    future_reader: claimant_floor_intake
    default_if_unworked: claimant_queue_first
  - row_id: sponsor_carveout_false_service
    load_kind: sponsor_carveout
    source_ruling_or_row: settlement_row_C
    required_surface: sponsor
    carrier_or_authority: shen_luo_or_sponsor_package
    protected_boundary: artist_refusal_receipt
    future_reader: management_compression
    default_if_unworked: management_false_clean

Beat 3 — The producer resolves one row and exposes another

The player opens Ruling Enforcement Load Review. The rite requires selected row, future reader, authority or explicit absence, carrier or explicit absence, proof bridge or explicit absence, protected boundary or explicit absence, and cost or scar.

A branch cannot say “law handles it,” “sponsor pays,” “archive stores it,” “Baiya edits it,” or “Yu Lan publishes it” unless the row and future reader change.

Beat 4 — The ruling becomes usable only through a scarred route

Valid branch families:

• roster lawful enforcement;
• publish public receipt enforcement;
• seal or split proof chain;
• sponsor / management compression;
• protect boundary and narrow use;
• quarantine the ruling;
• underfill, hide, or default.

Every branch preserves the source ruling while changing how it can be reused.

Beat 5 — A future reader consumes the load result

The storyline is not complete until at least one future reader changes acceptance because of the selected row state.

Future reader effects include:

• accepted_with_cost;
• lawful_only;
• public_only;
• sponsor_only;
• narrowed;
• blocked;
• hostile;
• contradiction_pending;
• public_audit_required;
• recovery_only.

Branch map

Branch	Relief	Cost	Future reader effect
Lawful roster	attachment compliance, custody clarity, archive legitimacy	inspection heat, bureau debt, public distrust, route narrowing	lawful-only or accepted with cost
Public receipt roster	private capture blocked, fan/public notice visible	sponsor pressure, witness exposure, pirate exposure, inspection heat	public-only or counterbroadcast-ready
Proof chain service	proof legibility, continuity, custody gap improves	edit debt, archive debt, source ambiguity, contradiction risk	editor-only, accepted with cost, or contradiction-pending
Sponsor compression	stop-loss, budget, or schedule pressure falls	contract capture, public distrust, fan refund debt, artist boundary risk	sponsor-only, audit-required, or recovery-only
Boundary protection	artist/witness/claimant harm decreases	route asset pressure, schedule pressure, sponsor pressure, recovery cost	narrowed, blocked, lawful-only, or recovery-only
Quarantine use	false service and breach risk drop	current route delay, asset pressure, claimant hostility	blocked or recovery-only
Default	a narrator moves first	false-served, captured, hostile, or public-only state hardens	blocked, hostile, contradiction-pending, or recovery-only

Counter contract

Every branch must mutate at least three surfaces:

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

Primary surfaces:

• enforcement_load
• custody_shift_coverage
• attachment_compliance
• attachment_breach_risk
• archive_signature_legitimacy
• archive_debt
• public_receipt_legitimacy
• public_receipt_distrust
• fan_refund_debt
• fan_oxygen_resentment
• sponsor_stop_loss_pressure
• contract_capture
• inspection_heat
• bureau_favor_debt
• proof_chain_integrity
• edit_debt
• source_ambiguity
• artist_refusal_respected
• witness_exposure
• crew_refusal_risk
• handler_burden
• route_asset_pressure
• future_route_acceptance
• producer_license_pressure
• management_pressure

Integration notes

• With 裁定附条件履行线, attachment rows become load rows when later routes try to rely on them.
• With 执行授权枯竭线, finite mandates become operational load instead of infinite authority.
• With 归档执行案卷, archive rows gain carriers, protected boundaries, and future readers.
• With 经营压缩台, a false-served load row can be counted as a false clean metric.
• With 认领人现场接待线, unserved notice or remedy rows can reach the floor as named claimant rows.
• With 直播现场班组负荷线, custody shifts require real floor capacity and can overrun.
• With 路线资产维护分诊线, a route asset can cite a ruling only if the load state is accepted.
• With 处理人负荷账本, a repeated authority or carrier can become strained, captured, hostile, or unavailable.
• With 派系承诺账本, sponsor, archive, public, editor, or inspector pressure must spend finite leverage to service a row.

Missability and recovery

The storyline is missed when the implementation treats a served ruling as permanently reusable without load row, carrier / absence, protected boundary / absence, and future reader effect.

Missed states:

• load_unopened
• carrier_absent_unrecorded
• false_served_ruling
• sponsor_compressed_without_public_service
• public_notice_missing
• artist_boundary_break
• proof_chain_gap
• enforcement_load_overrun
• recovery_only_enforcement

Recovery requires visible scar:

• reopen the docket and serve the missing row;
• publish omitted notice and accept sponsor or inspection heat;
• appoint a monitor and accept bureau debt;
• quarantine the ruling and lose a clean route;
• route through claimant intake with named hostility;
• accept lawful-only, public-only, sponsor-only, or recovery-only future use;
• repair proof chain through edit or archive debt;
• protect artist boundary and sacrifice route convenience.

Replay/session evidence shape

storyline: storyteller.storyline.ruling_enforcement_load.v1
session_id: lens-ruling-enforcement-load-v1-<timestamp>
seed: <deterministic-seed>
entry_state:
  trigger_kind: state_pressure
  source_ruling_or_row: <id>
  ruling_state_before: served | complied_partial | converted | mandate_assigned | custody_order_live | settlement_active | equivalent
  load_rows_min: 1
  load_row_pressure_present: true
  future_reader_reads_ruling: true
  no_fixed_turn_trigger: true
  no_fixed_day_or_week_trigger: true
offered:
  card: storyteller.card.ruling_enforcement_load_docket.v1
  rite: storyteller.rite.ruling_enforcement_load_review.v1
branch_runs:
  served_branch:
    selected_branch: lawful_roster | public_receipt | proof_chain | boundary_protection
    selected_row: <row id>
    handler_or_absence: <handler or explicit_absence>
    carrier_or_absence: <carrier or explicit_absence>
    proof_bridge_or_absence: <proof or explicit_absence>
    protected_boundary_or_absence: <boundary or explicit_absence>
    row_state_after: <state>
    future_reader_effect: <effect>
    counter_deltas: {}
  default_branch:
    selected_branch: default | sponsor_compression | quarantine
    event_seen_or_armed: storyteller.event.enforcement_load_default.v1 | none
    default_narrator_or_capture: <actor/state>
    row_state_after: <state>
    future_reader_effect: <effect>
    counter_deltas: {}
assertions:
  - source_ruling_preserved
  - entry_is_state_triggered
  - load_row_visible
  - future_reader_reads_result
  - carrier_or_explicit_absence_visible
  - boundary_or_explicit_absence_visible
  - branch_has_relief_and_cost
  - default_durable
  - no_fixed_turn_trigger
  - no_fixed_day_or_week_trigger

Non-goals

• Not a week, day, turn, timer, or fixed aftermath window.
• Not bulk filler.
• Not raw count satisfaction.
• Not a governance or dashboard page.
• Not a new verdict.
• Not a clean-up card that clears archive, sponsor, fan, inspector, artist, route asset, and management pressure at once.
• Not valid if a future route can cite a ruling without load row, carrier / absence, protected boundary / absence, cost, and future reader effect.