Ruling Enforcement Load / 裁定执行负荷机制

Ruling Enforcement Load is the mechanism for the operational afterlife of a ruling. Its top-level observable wrapper is 裁定执行负荷线.

A ruling can be valid and still unsafe to reuse. This mechanism asks whether its required enforcement rows have been staffed, served, bridged, protected, compressed, quarantined, or defaulted before a later route reads it.

Design problem

The corpus already supports verdicts, attachments, mandates, custody rows, management compression, floor intake, live crew load, and route asset maintenance. The remaining risk is a false universal key: once a ruling exists, later routes may cite it as if all notice, remedy, proof, boundary, carrier, and future-reader work happened automatically.

This mechanism prevents that. It turns the ruling into one or more load rows and makes the player choose which row can actually carry forward.

State-triggered entry

Open this mechanism when all are true:

entry_state:
  trigger_kind: state_pressure
  valid_ruling_or_equivalent_row_present: true
  ruling_has_operational_load: true
  load_row_pressure_present: true
  future_reader_reads_ruling: true
  player_can_assign_or_explicitly_absent_a_response: true
  no_fixed_turn_trigger: true
  no_fixed_day_or_week_trigger: true

Valid source rows include served rulings, archive orders, proof-burden shifts, custody decisions, public receipts, settlement rows, legality conversions, attachment compliance rows, and enforcement mandate rows.

Core objects

• 裁定执行负荷案卷 stores the source ruling, load rows, carriers, boundaries, future readers, and defaults.
• 裁定执行负荷复核 resolves one selected row through lawful roster, public receipt, proof chain, sponsor compression, boundary protection, or default.
• 执行负荷违约 fires or arms when a future reader uses the ruling while its load row is absent, underfilled, falsely served, or captured.

Load kinds

Load kind	What must be visible	Common default if hidden
notice	who was told, through which surface, and who was omitted	public or claimant row narrates first
remedy	who pays or repairs the harm	fan, sponsor, or claimant debt hardens
exclusion	who is barred from using the ruling	false owner or wrong claimant gains footing
monitor	who watches the ruling stay served	inspector freeze or breach risk rises
proof_chain	what proof bridge carries the ruling forward	editor/archive contradiction appears
public_receipt	what public proof makes service legible	public distrust or pirate relay rises
artist_boundary	what refusal / boundary is protected	refusal violation or recovery-only scar
sponsor_carveout	what private relief cannot count as public service	contract capture or public audit cost
custody_shift	who physically or operationally keeps the order alive	floor overrun or carrier loss
route_asset_hold	what asset state the ruling can actually support	asset staleness or false-fresh use

State machine

states:
  - load_unopened
  - load_row_present
  - load_rostered
  - load_understaffed
  - lawful_rostered
  - public_receipt_rostered
  - proof_chain_sealed
  - sponsor_compressed
  - boundary_protected
  - quarantine_pending
  - split_enforcement
  - false_served_ruling
  - enforcement_load_overrun
  - recovery_only_enforcement

State transitions must preserve the source ruling. A false-served ruling is not erased; it becomes dangerous to reuse.

Branch families

Lawful roster

Improves attachment compliance, custody clarity, or archive signature legitimacy. Costs inspection heat, bureau debt, public distrust, schedule pressure, or route narrowing.

Public receipt roster

Improves public receipt legitimacy, fan-facing notice, or private-capture resistance. Costs sponsor pressure, inspection heat, public exposure, witness exposure, or pirate risk.

Proof-chain service

Improves proof chain integrity, continuity, or custody gap. Costs edit debt, archive debt, source ambiguity, or later contradiction.

Sponsor / management compression

Improves sponsor, budget, schedule, or management pressure. Costs contract capture, public distrust, fan refund debt, artist boundary risk, or future audit.

Boundary protection / quarantine

Improves artist refusal, witness safety, breach risk, or claimant exclusion. Costs route access, schedule pressure, sponsor pressure, or recovery-only narrowing.

Default / overrun

Creates short relief or forced narration, then hardens a false-served, public-only, sponsor-only, lawful-only, hostile, blocked, contradiction-pending, or recovery-only future reader.

Counter contract

Every branch must mutate at least three surfaces:

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

Primary surfaces:

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 rules

• With 裁定附条件履行线, this mechanism executes the operational load after an attachment row exists or is contested.
• With 执行授权枯竭线, finite mandates can become load rows instead of abstract authority.
• With 经营压缩台, false-served rows become metric capture or greenwash pressure.
• With 认领人现场接待线, unserved rows can reach the floor as named claimants.
• With 直播现场班组负荷线, custody shifts require real carrier or crew capacity.
• With 路线资产维护分诊线, a ruling can support an asset only if its load state is accepted by the future route.
• With 处理人负荷账本, a repeated carrier or authority can become strained, captured, hostile, or unavailable.
• With 派系承诺账本, factions must spend finite leverage to service or capture a load row.

Replay evidence shape

mechanic: storyteller.mechanic.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: <state>
  load_rows_min: 1
  future_reader_reads_ruling: true
  no_fixed_turn_trigger: true
  no_fixed_day_or_week_trigger: true
docket:
  card: storyteller.card.ruling_enforcement_load_docket.v1
  rows: []
review:
  rite: storyteller.rite.ruling_enforcement_load_review.v1
  selected_row: <row id>
  selected_branch: lawful_roster | public_receipt | proof_chain | sponsor_compression | boundary_protection | default
result:
  row_state_after: <state>
  event_seen_or_armed: storyteller.event.enforcement_load_default.v1 | none
  future_reader_effect: <effect>
  counter_deltas:
    relief: []
    cost: []
    future: []
assertions:
  - source_ruling_preserved
  - load_row_visible
  - carrier_or_explicit_absence_visible
  - boundary_or_explicit_absence_visible
  - future_reader_mutated
  - branch_has_relief_and_cost
  - default_durable
  - no_fixed_turn_trigger

Non-goals

• Not a week, turn, timer, or upkeep phase.
• Not a new court case.
• Not a legal checklist without play.
• Not a dashboard or governance page.
• Not a clean compliance stamp.
• Not a way to satisfy every sponsor, fan, inspector, artist, archive, and route pressure at once.