Enforcement Load Default / 执行负荷违约
Enforcement Load Default fires or arms when a valid ruling is treated as usable while its enforcement load remains unassigned, underfilled, falsely served, or captured by the wrong narrator.
This is not a new verdict. It is the event that proves the old verdict has become operationally unsafe.
Entry condition
Fire or arm this event when all are true:
entry_state:
trigger_kind: state_pressure
valid_ruling_or_equivalent_row_present: true
enforcement_load_row_present_or_should_exist: true
row_unassigned_or_false_served: true
future_reader_attempts_to_use_ruling: true
no_fixed_turn_trigger: trueThe event can also be armed when a review rite is underfilled: no credible authority, no carrier, no protected boundary, no proof bridge, no future reader, or no cost surface.
Default narrators
Choose the default narrator from the missing or captured surface, not from a random table.
| Default narrator | When it selects the row | Durable effect |
|---|---|---|
management_false_clean | management reports the ruling as served without load rows | false_served_ruling, future audit cost, and possible false-service claimant if a row was omitted |
sponsor_compression_first | sponsor package counts private relief as full compliance | sponsor-gated route, public distrust, and possible sponsor counterclaimant row |
archive_stall_first | archive freezes use because proof bridge or seal is absent | lawful-only or blocked route |
inspector_freeze_first | inspector refuses acceptance due to missing monitor or notice | inspection heat, route delay |
claimant_queue_first | claimant intake receives a row before enforcement can serve it | named hostile or public row via false-service claimant escalation |
pirate_receipt_first | public/pirate relay preserves a missing notice outside license | public-only proof, enforcement heat, and pirate/public claimant row |
artist_boundary_break | ruling is reused while refusal or boundary check is absent | artist refusal violation, boundary claimant, recovery-only scar |
floor_overrun_first | carrier or live-floor capacity is absent | crew load, proof risk, route cost, and possible floor-carrier claimant row |
Event payload
event_payload:
event_id: storyteller.event.enforcement_load_default.v1
source_ruling_or_row: <source id>
missing_or_false_row: <row id or expected row>
default_narrator: <narrator>
attempted_future_reader: <route / rite / event / asset>
ruling_state_after: false_served | sponsor_gated | lawful_only | public_only | blocked | recovery_only | contradiction_pending
relief_delta: <what pressure temporarily improved, if any>
cost_delta: <what worsened>
future_reader_effect: <accepted_with_cost | blocked | narrowed | hostile | recovery_only | contradiction_pending>Claimant-facing escalation rule
If default_narrator is claimant-facing, the event must create or arm 误服裁定认领行, or record why no claimant row can exist.
false_service_claimant_escalation:
required_when_default_narrator_any:
- claimant_queue_first
- pirate_receipt_first
- artist_boundary_break
- floor_overrun_first
- management_false_clean
- sponsor_compression_first
card_or_explicit_absence: storyteller.card.false_service_claimant_row.v1 | explicit_absence
source_ruling_or_row: <source>
missing_or_false_load_row: <row>
named_claimant_or_absence: <claimant or explicit_absence>
demanded_control_or_absence: <control or explicit_absence>
intake_gate_or_absence: <gate/lane or explicit_absence>
future_route_effect_if_unanswered: <effect>
next_surface: storyteller.rite.false_service_claimant_escalation.v1 | storyteller.rite.claimant_intake_check.v1 | storyteller.rite.pressure_claimant_conversion_hearing.v1 | explicit_absenceA claimant-facing default fails validity if it only says “claimants are angry,” “public backlash rises,” or “a pirate relay moves first” without a false-service row or explicit absence.
Branch consequence
The default may give short relief: a slot can move, a sponsor can stop shouting, or a public row can finally be visible. It must also harden a cost.
A valid event changes at least three surfaces:
- ruling / row state;
- narrator posture;
- future reader access;
- at least one cost counter such as
inspection_heat,public_receipt_distrust,contract_capture,archive_debt,fan_refund_debt,crew_refusal_risk,artist_refusal_respected,route_asset_pressure, orproducer_license_pressure.
When a false-service claimant row is created, one additional surface must change:
false_service_claimant_rows_open;claimant_conversion_window;claimant_hostility;false_first_claimant;public_only_use;lawful_only_use;sponsor_only_use;recovery_only_claimant;coalition_seed_pressure.
Recovery hooks
Recovery requires a visible scar:
- reopen the load docket and serve the missing row;
- publish the omitted public receipt;
- appoint a monitor and accept inspection heat;
- quarantine the ruling for lawful-only use;
- return to claimant intake with a named hostile row;
- run 误服裁定认领升级 for a created false-service row;
- accept sponsor-gated route access;
- protect the artist boundary and lose a clean route;
- reroute the asset through maintenance or attachment compliance.
Replay evidence addition
claimant_escalation_evidence:
default_narrator_is_claimant_facing: true | false
false_service_claimant_row_created_or_absent: storyteller.card.false_service_claimant_row.v1 | explicit_absence | not_required
next_surface: false_service_claimant_escalation | claimant_floor_intake | pressure_claimant_conversion | none
downstream_reader_consumes_scar: true | falseNon-goals
- Not a random punishment.
- Not a fixed-time expiry.
- Not a new court result.
- Not a clean reset.
- Not valid unless the event records the missing row, default narrator, attempted future reader, and durable route consequence.
- Not valid if a claimant-facing default avoids row creation or explicit absence.