Archive Enforcement Docket / 归档执行案卷

Archive Enforcement Docket is a proof-and-pressure card for the moment when a prior ruling, settlement, quarantine, public receipt, or route-asset split becomes enforceable and therefore dangerous.

The earlier branch may already be correct. This docket asks a different question: who has the staff, warrant, receipt, public witness, and legal stomach to make the ruling hold after the losing side starts refusing compliance?

Card fields

• card_id: card.archive_enforcement_docket
• card_type: proof / pressure / enforcement-docket
• owner: producer desk until assigned, seized, published, or voided
• default_state: enforcement_pending
• durability: persists until execution is complied with, appealed, delayed, split, blocked, converted into hostile custody, or voided
• route_tags: archive-custody, enforcement, route-assets, inspector-pressure, settlement-aftershock, management-rpg

Enters play from state

Create this docket only when all of the following are true:

1. a prior ruling or settlement exists from archive custody, claimant collision, broadcast reality drift, settlement aftershock, fan oxygen receipt, memorial rights, or equivalent;
2. the prior result names an enforceable obligation: hand over a copy, respect a refusal, honor a public receipt, keep a quarantine, roster custody staff, pay a fan queue, preserve a route asset, or surrender a false owner;
3. at least one obligated party can resist, delay, counterfeit, sponsor-wrap, leak, appeal, or physically obstruct enforcement;
4. at least one enforcement actor, carrier, proof object, or public witness can be assigned or is explicitly absent;
5. the obligation has not already been executed, voided, or hardened into irreversible route law.

This card is state-triggered. It must not enter play from a fixed numbered turn.

Visible memory required

A valid docket must record:

• source_ruling_id: prior ruling, settlement, branch, or route-asset state;
• source_relief: what the prior branch successfully protected or unlocked;
• source_debt: what the prior branch left unpaid or contested;
• enforcement_order: copy handover, quarantine, roster, receipt payment, refusal boundary, claimant surrender, public correction, route asset protection, or equivalent;
• obligated_party: sponsor, archive desk, inspector, editor, manager, fan public, artist claimant, pirate relay, field carrier, or false owner;
• enforcement_actor: Han Yanshuang, Inspector Rhee, Yu Lan, Shen Luo, Baiya, Lin Qiao, route asset, public witness, or explicit absence;
• proof_chain: audit seal, receipt packet, black-box fragment, public witness, fan oxygen queue, refusal receipt, custody copy, or explicit missing proof;
• resistance_mode: comply, appeal, sponsor-delay, counterfeit, leak, physical obstruction, public refusal, route capture, or absence;
• enforcement_state: pending, served, complied, appealed, delayed, publicly_countered, split, blocked, hostile, voided, or hardened.

Assignable uses

Serve enforcement

The player assigns an enforcement actor plus proof chain to make the prior ruling operational.

Expected outcomes:

• enforcement_state = served or complied;
• custody clarity, archive signature legitimacy, refusal respect, or route asset protection improves;
• inspection heat, favor debt, public exposure, field carrier risk, or sponsor retaliation rises.

Appeal or stay

The player uses inspector process, manager negotiation, or sponsor leverage to delay execution without pretending the ruling vanished.

Expected outcomes:

• enforcement_state = appealed or delayed;
• immediate blackout, injunction, or sponsor pressure may decrease;
• archive debt, fan resentment, public receipt distrust, or false-owner hardening risk rises.

Public counter-enforcement

The player assigns Yu Lan, fan oxygen proof, public witnesses, or pirate relay to make enforcement legible outside formal custody.

Expected outcomes:

• enforcement_state = publicly_countered or split;
• public receipt legitimacy, fan oxygen balance, or route-asset witness strength improves;
• legal exposure, inspection heat, sponsor stop-loss pressure, pirate exposure, or artist boundary risk rises.

Editorial compliance patch

The player assigns Baiya, black-box proof, checksum, source tape, or redaction to make the enforcement order visible in broadcast reality.

Expected outcomes:

• enforcement_state = served, split, or editorial_patch_compliance;
• continuity hazard or reality drift decreases;
• edit debt, archive debt, public distrust, or future fraud cost rises.

Miss, obstruct, or hostile custody

The player lacks proof, hides the docket, lets the obligated party narrate first, burns the carrier, or allows a false owner to resist execution.

Expected outcomes:

• enforcement_state = blocked, hostile, voided, or hardened;
• at least one route action becomes blocked, costlier, recovery-only, or faction-hostile;
• custody gap, archive debt, black screen slots, false owner hardening, fan resentment, or route asset pressure rises.

Blocked reasons

Blocked or weak branches should be visible:

• source_ruling_missing
• enforcement_order_missing
• proof_chain_missing
• enforcement_actor_absent
• obligated_party_unknown
• obligated_party_already_hardened
• artist_refusal_conflict
• public_witness_absent
• sponsor_stay_active
• field_carrier_at_risk

Non-goals

• Not a new verdict.
• Not a generic audit card.
• Not a free cleanup for archive, sponsor, fan, editor, inspector, and artist pressure.
• Not a turn-count trigger.
• Not a retcon of the prior branch; the earlier relief remains true while execution creates new risk.