Storyteller Wiki

Ruling Enforcement Load Docket / 裁定执行负荷案卷

3 min read

Ruling Enforcement Load Docket / 裁定执行负荷案卷

Ruling Enforcement Load Docket is a hand / docket card for a ruling that is already valid but not yet operationally safe.

The card appears when a served ruling, converted legality state, archive order, proof-burden shift, custody decision, public receipt, or settlement row creates enforcement work that still has to be assigned. The ruling is real; this docket records why it is not a clean universal key.

Required row fields

Each docket must contain at least one enforcement row. A strong docket contains two or more rows that cannot all be served cleanly.

enforcement_load_row:
  row_id: <stable id>
  source_ruling_or_row: <ruling / settlement / order / proof-burden row>
  ruling_state_before: served | complied_partial | converted | mandate_assigned | custody_order_live | settlement_active | equivalent
  load_kind: notice | remedy | exclusion | monitor | proof_chain | public_receipt | artist_boundary | sponsor_carveout | custody_shift | route_asset_hold | equivalent
  obligated_party: <party or desk>
  required_surface: lawful | public | editor | sponsor | archive | floor | route_asset | production | equivalent
  carrier_or_authority: <handler / permit / proof / explicit_absence>
  blocking_pressure: <pressure that makes clean service false>
  protected_boundary: <artist / witness / claimant / route asset / explicit_absence>
  future_reader: <route / rite / event / asset / claimant system that will read this row>
  default_if_unworked: <default actor or failure state>

Playable card use

When assigned to a review rite, this card lets the player choose which enforcement row to roster, publish, seal, compress, quarantine, refuse, or leave to default.

The player is not choosing whether the old ruling happened. They are choosing which load row is credible enough to carry forward.

Valid row examples

  • A lawful archive order exists, but public notice is absent and Yu Lan can publish it only by raising inspection heat.
  • A sponsor settlement paused stop-loss, but the fan oxygen refund row has no receipt carrier.
  • A custody decision protected a proof object, but the live floor has no safe carrier or staffing lane.
  • A public contrition statement aired, but an artist refusal boundary was never checked.
  • A proof-burden shift names a holder, but the holder is already burdened, captured, or absent.
  • A quote or route asset can cite the ruling only if an attachment row is served.

Branch-facing states

docket_states:
  - load_unopened
  - load_rostered
  - load_understaffed
  - lawful_rostered
  - public_receipt_rostered
  - sponsor_compressed
  - proof_chain_sealed
  - boundary_protected
  - quarantine_pending
  - false_served_ruling
  - enforcement_load_overrun
  - recovery_only_enforcement

Cost contract

A row cannot resolve by declaring that management, law, sponsor, archive, edit, or public support handled everything. Resolution must alter:

  • one relief surface;
  • one cost surface;
  • one future reader.

Common surfaces include custody_shift_coverage, attachment_compliance, public_receipt_legitimacy, fan_refund_debt, sponsor_stop_loss_pressure, inspection_heat, archive_debt, edit_debt, artist_refusal_respected, proof_chain_integrity, route_asset_pressure, management_pressure, and producer_license_pressure.

Missability

The docket is missed when a valid ruling is reused by a later route while its enforcement row, carrier, protected boundary, and future reader are never recorded.

A missed docket should not erase the ruling. It should arm a false-served or recovery-only state that can later be exposed by claimant intake, management compression, asset maintenance, or attachment compliance.

Graph View

Backlinks