Evidence Carryover Fork / 导出证据回流分岔线

This storyline covers the moment when a proof object that survived a previous crisis returns to the production floor and changes who can use a route asset now.

The returning proof may be an archive copy, fan oxygen receipt, black-box checksum, memorial air copy, sponsor counterclaim, consent receipt, proxy statement, or other custody object. It must arrive with a prior outcome and a present claimant conflict. Its purpose is not to summarize earlier play; it should force a new branch through 导出证据回流分岔机制.

Entry pressure

Open this storyline when current play contains all of:

• a proof object with a known earlier outcome such as protected, route_asset, hostile, captured, false_owner, split_canon, or recovery_only;
• a current claimant who wants to seat, hide, trade, expose, or deny the proof;
• a rival claimant, contradiction, or explicit missing claimant;
• an affected route asset, proxy, consent debt, archive docket, three-key custody row, or broadcast reality row that can mutate.

Do not open from a fixed numbered trigger.

Core cast and usable roles

The storyline can use any current actor who can actually alter the proof:

• Han Yanshuang can seat lawful cover, archive admissibility, or quarantine.
• Yu Lan can convert returned proof into public receipt or fan witness pressure.
• Baiya can verify, split, overwrite, or weaponize checksum/source custody.
• Shen Luo can trade the proof through sponsor settlement or contract capture.
• 海盗频段童声 can relay public/pirate versions when official channels suppress the proof.
• Mira Veil or an equivalent artist/refusal holder can contest voice, memory, consent, or memorial proof.
• 交接链跑腿 or another logistics carrier can physically move the returned object and inherit risk.

A named actor does not solve the branch by appearing. They must be assigned with a proof object, cover, cost, or explicit absence.

Storyline sequence

Beat 1 — Old proof knocks on a new door

Create or update 导出证据回流案卷. The card records what returned, its prior outcome, who claims it now, who contests it, what it contradicts, which route asset is affected, and what happens if ignored.

Possible openings:

• a fan oxygen receipt from a public vigil contradicts a sponsor ownership packet;
• a black-box checksum contradicts the clean edit that currently holds custody;
• a consent receipt returns after a folded contract tries to move the debt;
• a memorial air copy resurfaces after a lawful archive injunction;
• a proxy statement from a prior route asset contradicts current testimony.

Beat 2 — The current claimant demands a seat

The current claimant forces a decision. The player sees at least two non-equivalent options before committing.

Valid pressure sources include:

• archive or inspector demand for admissibility;
• sponsor demand for silence or naming control;
• fan public demand for public receipt;
• editor demand for checksum priority;
• artist or refusal holder demand for consent boundary;
• proxy, runner, witness, or pirate carrier demanding protection before use.

Beat 3 — Carryover hearing

Offer 导出证据回流听证 when the docket is concrete and branchy.

The rite chooses one branch:

• accept — seat the old proof into current custody and pay debt;
• quarantine — preserve proof without letting it decide current reality yet;
• overwrite — let the newer aired reality replace the old proof and create source scar;
• trade — give the proof to a claimant for relief, access, or delay;
• expose — publish the proof publicly with retaliation/protection cost;
• deny — reject the proof and arm aftershock pressure.

Beat 4 — Route asset state changes

After resolution, the affected route asset must change into a durable state such as:

• protected
• route_asset
• costlier
• hostile
• captured
• lawful_only
• public_only
• split_canon
• contradiction_pending
• recovery_only
• blocked

At least three counters or states should move, with at least one relief and one cost.

Beat 5 — Aftershock or recovery path

If the proof is denied, captured, overwritten cleanly, exposed without protection, traded cleanly, or accepted without debt, emit 导出证据回流反震.

If the player manages the branch responsibly, no clean ending is granted; instead the proof leaves one future scar such as inspection heat, sponsor retaliation, edit debt, fan resentment, proxy exposure, handler burden, consent debt, broadcast reality drift, or recovery route cost.

Branch matrix

Branch	Immediate relief	Cost/scar	Future state
Accept	custody, route, public receipt, or voice integrity improves	claimant retaliation, inspection heat, sponsor pressure, edit debt, handler burden	route open with debt
Quarantine	false owner, archive fraud, or voice violation prevented	schedule/audience/inspection/recovery pressure rises	contradiction pending or recovery-only
Overwrite	immediate contradiction or sponsor default drops	source ambiguity, archive debt, consent debt, public distrust	split canon, blocked, or hostile witness possible
Trade	immediate pressure, lawful use, room access, or sponsor delay improves	route capture, faction gate, contract capture, bureau favor debt	captured, lawful-only, public-only, or costlier
Expose	public receipt, fan legitimacy, or private capture resistance improves	inspection heat, sponsor pressure, proxy exposure, broadcast drift	public route with retaliation
Deny	none, or only short-term silence	hostile counterclaim, false owner, archive debt, route pressure	hostile, captured, recovery-only, contradiction pending, or blocked

Required content surfaces

• 导出证据回流分岔机制
• 导出证据回流案卷
• 导出证据回流听证
• 导出证据回流反震
• Route Assets and Custody

Counter surfaces

Use at least three relevant surfaces when a branch resolves:

• route_asset_pressure
• archive_debt
• archive_signature_legitimacy
• inspection_heat
• sponsor_stop_loss_pressure
• public_receipt_legitimacy
• fan_oxygen_resentment
• voice_integrity
• source_ambiguity
• edit_debt
• consent_debt
• handler_burden
• proxy_exposure
• broadcast_reality_drift
• false_custody_owner
• recovery_route_cost

Non-goals

• Not a recap of old sessions.
• Not a free continuity patch.
• Not a fixed-turn episode.
• Not a lore-only contradiction scene.
• Not valid unless returned evidence changes present route assets, claimants, counters, and future availability.