Archive Enforcement Docket Storyline / 归档执行案卷

Archive Enforcement Docket is a non-character pressure storyline for the stage after a custody, settlement, receipt, quarantine, or broadcast-reality ruling has become enforceable.

The ruling is already history. The question now is whether anyone can make it hold.

A formal service can protect custody and create bureau debt. A sponsor stay can save the slot and harden public distrust. A public counter-enforcement can recruit witnesses and trigger inspection heat. An editorial patch can reduce drift and create edit debt. A weak proof chain can turn a carrier, witness, or obligated claimant hostile.

Primary playable question

When the show has a valid ruling but the losing side refuses the consequences, does the player serve it, delay it, expose it, patch it, split it, or let it harden into hostile custody?

Why this is the next useful expansion

Recent Storyteller content already supports rich first-order outcomes through 认领撞锁, 播出实在漂移审计, 和解反震账本, Oxygen Claim Exchange Storyline, and Memorial Rights Contempt Storyline.

The real gap is execution. A green branch can say the archive copy is split, the public receipt is valid, or the refusal boundary is protected; the game still needs to prove who serves the order, who carries the copy, who resists, and which route asset or follower changes state when enforcement fails.

This storyline makes enforcement a playable management/RPG layer rather than another verdict fork or filler escalation.

State-triggered entry

Open this storyline when all of the following are true:

1. a prior branch produced a ruling, settlement, receipt, quarantine, refusal protection, route asset split, custody seal, public witness chain, or equivalent enforceable outcome;
2. the prior branch recorded both relief and debt;
3. an obligated party can still comply, appeal, delay, counterfeit, leak, obstruct, or harden against the order;
4. the player can assign or explicitly lack an enforcement actor, proof chain, and bridge/cost;
5. at least one route asset, follower, public witness, carrier, artist boundary, sponsor claim, inspector claim, editor copy, or archive copy can change future state;
6. the enforcement has not already been complied with, voided, or hardened.

This storyline must never trigger from a fixed numbered turn. It is entered from enforceable-but-not-yet-executed state.

Content pack

Mechanism

• 归档执行机制 — defines enforcement states, slot requirements, branch families, follower pressure, and evidence shape.

Card

• 归档执行案卷 — stores source ruling, obligation, obligated party, proof chain, resistance mode, and enforcement state.

Rite

• 归档执行复核 — assignable management rite that serves, delays, publicly counter-enforces, patches, or fails enforcement.

Event

• 归档执行破口 — visible breach when enforcement is resisted, counterfeited, delayed into hardening, or partially executed.

Primary actors

• Han Yanshuang — formal service, bureau debt, lawful pressure, injunction risk.
• Inspector Rhee Archive — archive admissibility, seizure, compliance challenge, fraud pressure.
• Yu Lan — public counter-enforcement, receipt legitimacy, witness recruitment, legal exposure.
• Shen Luo — sponsor stay, manager bridge, fan distrust, contract capture.
• Baiya — editorial compliance patch, black-box contradiction, edit debt.
• 交接链跑腿 — physical handover, low-rank carrier risk, miss/recruit/hostile branch.

Core route states

Route state	Meaning	Required consequence
enforcement_pending	Ruling exists and obligation is named.	Review rite can be offered.
served	Actor and proof reached the obligated party.	Compliance/refusal/partial breach must resolve.
complied	Order is executed enough to hold.	Relief improves and a cost remains.
appealed	Lawful delay keeps order alive but unexecuted.	Immediate pressure may drop; debt rises.
delayed	Execution is postponed without clean legal cover.	Rival claimant can narrate first or harden.
publicly_countered	Public witness chain pressures execution.	Public legitimacy improves; legal/sponsor risk rises.
editorial_patch_compliance	Broadcast artifact reflects the order.	Drift improves; edit/archive debt rises.
split	Formal and public enforcement produce separate usable copies.	More routes unlock; drift/fraud/inspection risk rises.
blocked	Required actor, proof, cost, or target is absent.	Route becomes costlier or recovery-only.
hostile	Obligated party, carrier, or witness turns against the player.	Hostile witness, injunction, leak, capture, or retaliation enters play.
voided	Order loses force because proof or actor collapses.	Prior relief weakens; recovery requires sacrifice.
hardened	Wrong owner or resistance becomes route law.	Clean success closes without appeal/counterproof/sacrifice.

Branch model

Branch A — Formal service

The player assigns Han Yanshuang, Inspector Rhee, archive seal, custody staff, continuity law, or a protected carrier to serve the order.

Expected outcomes:

• enforcement_state = served or complied;
• custody_clarity, archive_signature_legitimacy, artist_refusal_respected, or route_asset_protected improves;
• inspection_heat, bureau_favor_debt, field_carrier_risk, sponsor_stop_loss_pressure, or public_exposure rises.

Branch B — Managed stay or appeal

The player assigns Shen Luo, sponsor leverage, legal delay, or manager bridge to keep execution from detonating immediately.

Expected outcomes:

• enforcement_state = appealed, delayed, or stay_granted;
• immediate blackout, injunction, sponsor pressure, or slot risk may decrease;
• archive_debt, public_receipt_distrust, fan_oxygen_resentment, future_enforcement_cost, or false_owner_hardening_risk rises.

Branch C — Public counter-enforcement

The player assigns Yu Lan, public receipt, fan oxygen queue, audience testimony, pirate relay, or public witness chain.

Expected outcomes:

• enforcement_state = publicly_countered, split, or public_receipt_enforced;
• public_receipt_legitimacy, fan_oxygen_balance, or route witness strength improves;
• inspection_heat, sponsor_stop_loss_pressure, pirate_exposure, or artist boundary risk rises;
• a witness or follower state can become recruited, protected, hostile, or missed.

Branch D — Editorial compliance patch

The player assigns Baiya, black-box fragment, checksum, source tape, redaction, or continuity patch.

Expected outcomes:

• enforcement_state = editorial_patch_compliance, served, or split;
• continuity_hazard or reality_drift decreases;
• edit_debt, archive_debt, public_receipt_distrust, or future_fraud_cost rises.

Branch E — Carrier protection or sacrifice

The player assigns or withholds protection from a carrier, low-rank witness, handover route, or custody staffer.

Expected outcomes:

• carrier state becomes protected_under_oath, recruited, hostile, captured, missed, or sacrificed;
• physical handover becomes possible, blocked, recovery-only, or publicly witnessed;
• field_carrier_risk, payroll_leak, favor_debt, custody_gap, or route_asset_pressure changes.

Branch F — Breach, hostile custody, or hardening

The player lacks actor/proof/cost, hides the docket, lets sponsor stay erase the public reason, accepts counterfeit compliance, or lets the obligated party narrate first.

Expected outcomes:

• enforcement_state = blocked, hostile, voided, or hardened;
• 归档执行破口 or equivalent fires;
• at least one future route becomes blocked, costlier, recovery-only, captured, hostile, or sacrifice-only;
• at least three counters or durable states change.

Counter contract

Every resolution, breach, or hardening must change at least three counters or durable states. At least one must be visible relief and at least one must be visible cost.

Primary states:

• 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

Multi-session continuity expectation

This storyline should be able to load an enforceable order created in an earlier replay and prove that later enforcement preserved the earlier relief/debt memory.

Expected evidence:

• source session id and seed that created the ruling;
• enforcement session id and seed;
• source ruling id and route asset;
• relief and debt carried into the docket;
• obligated party and resistance mode;
• assigned actor, proof chain, bridge/cost, and resistance target;
• selected branch;
• resulting counter deltas, follower state changes, and future route effects.

Missability and recovery

This storyline is missable when the player treats a ruling as self-executing, suppresses the public receipt, blocks inspector access, leaves the proof chain uncarried, delays through sponsor stay without expiry, or lets a false owner narrate compliance first.

Recovery is allowed only at higher cost:

• reopen service with stronger proof;
• protect a carrier under oath;
• publish public counterproof and accept sponsor/inspection backlash;
• patch editorial compliance and accept edit/archive debt;
• pay fan refund or public apology;
• sacrifice a route asset or favor to unwind hardened false ownership.

Integration notes

• With 和解反震账本, this storyline begins when aftershock debt becomes an enforceable obligation.
• With 认领撞锁, this storyline tests whether split, priority, or quarantine states can actually be served.
• With 播出实在漂移审计, this storyline tests whether a patched reality is enforceable against contradictory copies.
• With Oxygen Claim Exchange Storyline, fan oxygen receipts can become public counter-enforcement or resentment if delayed.
• With Memorial Rights Contempt Storyline, refusal and memorial custody can be protected formally or breached publicly.
• With Route Assets and Custody, enforcement changes route asset states, carrier risk, witness availability, and future route cost.

Non-goals

• Not a fixed-turn after-event.
• Not a new verdict fork.
• Not a generic epilogue.
• Not a governance/process page.
• Not filler escalation.
• Not a clean universal enforcement action.
• Not a retcon of earlier success; relief remains true while execution creates new pressure.