Archive Enforcement Docket / 归档执行机制

Archive Enforcement Docket is the mechanism that turns a settled archive ruling into enforceable management pressure.

Existing Storyteller content can already create rulings, settlements, custody splits, public receipts, and aftershock debt. This mechanism covers the next playable gap: a ruling can be correct and still fail because nobody serves it, the obligated party resists, the proof chain is missing, the public receives the wrong copy, or a low-rank carrier becomes the only person who can prove handover.

Primary observed surface

This mechanism observes 归档托管体系, Route Assets and Custody, and 和解反震账本.

It is observed through 归档执行案卷, 归档执行复核, and 归档执行破口.

Design problem

A verdict is not execution.

If a branch says the archive copy belongs to the public, the sponsor still has lawyers. If a refusal receipt is protected, the editor still needs a cut that honors it. If an inspector seal says the archive desk must surrender a copy, someone still has to carry, witness, or serve it. If the player delays, the losing claimant may harden first.

This mechanism makes that enforcement layer playable instead of letting earlier success become clean closure.

State machine

State	Meaning	Required consequence
enforcement_absent	A ruling exists but no execution surface has been created.	No execution branch may resolve silently.
enforcement_pending	Docket exists and obligation is named.	Rite can serve, stay, counter-enforce, patch, or fail.
served	Actor and proof chain reached the obligated party.	Compliance, refusal, or partial breach must be determined.
complied	The obligated party performed enough of the order.	At least one relief improves and at least one cost remains.
appealed	Execution enters lawful delay.	Immediate pressure may fall; future debt rises.
delayed	Execution is postponed without clean legal closure.	A rival claimant may narrate first or harden.
publicly_countered	Public/fan witness chain pressures execution outside formal archive law.	Public legitimacy improves while legal/sponsor/inspection pressure rises.
editorial_patch_compliance	The broadcast cut is patched to make the order legible.	Continuity improves while edit/archive/public debt changes.
split	Formal and public enforcement produce separate usable copies.	More routes unlock, but drift/fraud/inspection costs rise.
blocked	Execution cannot proceed because a required slot is absent.	Future route becomes costlier or recovery-only.
hostile	Obligated party, carrier, or claimant turns against the producer.	Hostile witness, injunction, leak, capture, or faction retaliation enters play.
voided	The order loses force because proof, actor, or public anchor collapses.	Prior relief is weakened but not retconned; recovery requires sacrifice.
hardened	Wrong owner or refusal of execution becomes route law.	Clean success closes; only appeal, counterproof, or sacrifice can reopen.

Required slots

Every enforcement attempt must carry four playable slots:

1. docket: source ruling plus relief/debt memory;
2. actor: formal, logistical, public, editorial, managerial, or explicit absence;
3. proof_chain: admissible or public proof, or explicit missing proof;
4. bridge_or_cost: the payment, favor, risk, sacrifice, exposure, patch, stay, or apology that makes execution possible.

A fifth resistance_target is required whenever a breach, appeal, delay, or hostile branch is possible.

Branch families

Formal service

The player assigns inspector/archive authority, custody staff, or a carrier to serve the order.

Expected result:

• enforcement moves to served, complied, or partial breach;
• custody_clarity, archive_signature_legitimacy, or artist_refusal_respected improves;
• inspection_heat, bureau_favor_debt, field_carrier_risk, sponsor_stop_loss_pressure, or public_exposure rises.

Managed stay or appeal

The player delays execution through lawful appeal, sponsor pressure, or manager bridge.

Expected result:

• enforcement moves to appealed, delayed, or stay_granted;
• immediate legal, sponsor, or slot pressure may improve;
• archive_debt, public_receipt_distrust, fan_oxygen_resentment, future_enforcement_cost, or false_owner_hardening_risk rises.

Public counter-enforcement

The player makes enforcement legible through fan oxygen proof, public receipts, historian witness, or pirate relay.

Expected result:

• enforcement moves to publicly_countered, split, or public_receipt_enforced;
• public_receipt_legitimacy, fan_oxygen_balance, or route-asset witness strength improves;
• inspection_heat, sponsor_stop_loss_pressure, pirate_exposure, or artist boundary risk rises.

Editorial compliance

The player patches the broadcast artifact to reflect the order without losing continuity.

Expected result:

• enforcement moves to editorial_patch_compliance, served, or split;
• continuity_hazard or reality_drift decreases;
• edit_debt, archive_debt, public_receipt_distrust, or future_fraud_cost rises.

Hostile or hardened enforcement

The obligated party resists, the proof chain is weak, or the player hides the docket.

Expected result:

• enforcement moves to blocked, hostile, voided, or hardened;
• 归档执行破口 or equivalent fires;
• future route access changes: blocked, costlier, captured, hostile, recovery-only, split, or sacrificed.

Follower and NPC pressure

This mechanism must expose low-rank and NPC consequences. Enforcement should be able to change one of these states:

• runner_protected_under_oath
• runner_hostile_witness
• carrier_captured
• public_witness_recruited
• public_witness_missed
• inspector_favor_debt
• manager_sponsor_capture
• editorial_compliance_debt
• false_owner_hardened

A high-rank actor cannot erase physical chain-of-custody pressure without a carrier, witness, permit, proof object, or public trace.

Counter contract

Every resolved enforcement branch must move at least three counters or durable states. At least one must be relief and at least one must be cost.

Useful states include:

• enforcement_state
• custody_clarity
• archive_signature_legitimacy
• archive_debt
• archive_fraud
• inspection_heat
• bureau_favor_debt
• field_carrier_risk
• public_receipt_legitimacy
• public_receipt_distrust
• fan_oxygen_balance
• fan_oxygen_resentment
• sponsor_stop_loss_pressure
• contract_capture
• continuity_hazard
• reality_drift
• edit_debt
• future_fraud_cost
• route_asset_pressure
• false_owner_hardening_risk
• black_screen_slots

Evidence contract

A correct implementation must be replay-visible:

• source ruling id and source route asset;
• docket state before and after;
• assigned actor, proof chain, bridge/cost, and resistance target;
• branch choice and blocked reasons;
• breach event when execution fails, mutates, or hardens;
• counter deltas and future route effects;
• actor/follower state changes when a carrier, witness, inspector, editor, manager, or public historian is exposed.

Non-goals

• Not another first-order verdict fork.
• Not a free cleanup after settlement.
• Not a fixed-turn timer.
• Not a governance checklist.
• Not a hidden flag with prose callbacks only.