Archive Enforcement Breach / 归档执行破口

Archive Enforcement Breach is the visible event that fires when an enforceable archive order is resisted, voided, delayed too long, publicly countered without enough legal support, or physically obstructed by a claimant who should have complied.

The event exists to prevent archive enforcement from becoming invisible bookkeeping. When execution fails or mutates, route assets, followers, public legitimacy, and future rites must change.

Fires from state

Fire this event when 归档执行案卷 or equivalent reaches one of these states:

  • blocked
  • hostile
  • voided
  • hardened
  • appealed with no bridge or expiry condition
  • delayed while another claimant narrates first
  • publicly_countered without proof chain
  • editorial_patch_compliance contradicted by source proof
  • served but the obligated party refuses physical handover

It may also fire as a partial breach from 归档执行复核 when a branch succeeds on one surface and fails on another.

Required payload

A valid breach event must record:

  • source_docket: the enforcement docket or equivalent state;
  • source_ruling_id: the prior ruling being enforced;
  • obligated_party: who resisted or complied only partially;
  • failed_slot: actor, proof chain, bridge/cost, resistance target, physical handover, public witness, or boundary object;
  • breach_mode: refusal, stay abuse, counterfeit compliance, public split, edit contradiction, carrier intimidation, false owner hardening, sponsor injunction, or archive seizure;
  • visible_victim: route asset, follower, fan queue, artist boundary, custody copy, public witness, carrier, or broadcast reality;
  • counter_deltas: at least three deltas with relief/cost when partial success exists;
  • future_route_effect: blocked, costlier, hostile, captured, recovery-only, split, quarantined, or hardened.

Breach modes

Refusal after service

The order was served but the obligated party refuses the handover or compliance.

Expected effects:

  • enforcement_state = hostile or served_refused;
  • custody_gap +1, inspection_heat +1, or archive_debt +1;
  • the resisting claimant becomes a future opponent, not ambient flavor.

Stay abuse

An appeal or sponsor stay pauses pressure but is used to erase the public reason for the ruling.

Expected effects:

  • enforcement_state = delayed or stay_abused;
  • immediate sponsor or legal pressure may drop;
  • public_receipt_distrust +1, fan_oxygen_resentment +1, or false_owner_hardening_risk +1.

Counterfeit compliance

The obligated party hands over a sanitized, edited, duplicate, or false-owner copy.

Expected effects:

  • enforcement_state = counterfeit_compliance or false_owner_hardened;
  • reality_drift +1, future_fraud_cost +1, or archive_fraud +1;
  • recovery requires counterproof, public witness, or sacrifice.

Public split without lawful support

The public or fan side can prove the obligation morally but not legally.

Expected effects:

  • enforcement_state = publicly_split;
  • public_receipt_legitimacy +1 or fan legitimacy improves;
  • inspection_heat +1, sponsor_stop_loss_pressure +1, or pirate_exposure +1.

Carrier intimidation

A low-rank carrier, witness, courier, or custody staffer is threatened, bought, disappeared, or turned hostile.

Expected effects:

  • carrier state becomes hostile, captured, protected_under_oath, or missed;
  • route asset access becomes protected, blocked, costlier, or recovery-only;
  • field_carrier_risk, payroll_leak, custody_gap, or favor_debt changes.

Partial success rule

A breach may coexist with relief. For example, a public counter-enforcement can raise public legitimacy while increasing inspection heat; a formal service can protect an artist refusal while turning the sponsor hostile.

The event must preserve both facts. It cannot flatten the result into pure success or pure failure unless every surface clearly moved that way.

Follow-up hooks

  • rite.archive_enforcement_review may reopen the docket at higher cost.
  • a route asset may become hostile, captured, protected, or recovery_only.
  • a follower or low-rank carrier may become recruitable, missable, protected, or hostile based on who the player exposed.
  • a sponsor, inspector, or public claimant may gain a new blocking reason for future rites.

Non-goals

  • Not a random crisis.
  • Not a mood scene after a legal ruling.
  • Not a universal punishment for choosing public receipts.
  • Not a fixed-turn failure timer.
  • Not a retcon of prior relief.