Receipt Packet Counterclaim Procedure Lens

Pollution diagnosis

Recent Storyteller intake accidentally promoted worker progress markers into canon identity. The useful thing was not “the next turn.” The useful thing was a reusable management/RPG procedure: a contested receipt packet can be defended, published, settled, suppressed, or allowed to harden into false custody.

The polluted pattern looked like this:

• page titles and ids began with turnXX;
• tags and rite ids repeated the same turn marker;
• gap diagnosis said “previous turn proves X, therefore next turn is Y”;
• replay turn range became the main design anchor rather than a provenance field;
• new content chained itself to previous lens pages more strongly than to durable systems, storylines, characters, counters, and route assets.

This lens rewrites that slice as a reusable procedure. Turn numbers may remain inside replay evidence, migration notes, or source provenance, but they must not be the canonical reason the content exists.

Design intent

Receipt counterclaims should be playable because they pressure custody, witnesses, sponsors, fan oxygen, archive law, and low-rank logistics. The player should feel that evidence handling is a management problem: assign a defender, protect or sacrifice a runner, publish or settle a receipt, and accept visible costs.

The procedure must be reusable whenever a chain-of-custody packet is disputed. It should work after inspection pressure, archive custody pressure, memorial custody pressure, fan oxygen pressure, or sponsor stop-loss pressure. It is not a numbered chapter beat.

Corrected identity

• Stable id: storyteller.receipt_packet_counterclaim_procedure.v1
• Canonical page: wiki/content/lens/storyteller/receipt-packet-counterclaim-procedure.lens.md
• Primary observed system: route-assets-and-custody
• Primary observed character surface: lin-qiao-chain-runner
• Primary observed event surface: shadow-crew-custody-leak

Trigger conditions

The procedure may be offered when all of the following are true:

1. a receipt packet, missing stub, custody copy, black-box fragment, fan oxygen queue receipt, or archive docket copy exists;
2. at least two factions can plausibly claim or contest the receipt;
3. the player has at least one assignable card who can defend, publish, negotiate, audit, transport, or suppress the chain;
4. at least one unresolved route pressure exists: custody_gap, archive_debt, inspection_heat, sponsor_stop_loss_pressure, fan_oxygen_resentment, public_receipt_legitimacy, or equivalent.

A replay turn number can help prove reachability, but the offer must be state-triggered, not turn-triggered.

Affected cards and route assets

Required or equivalent:

• 林乔 / 交接链跑腿 as recruited runner, missed runner, hostile witness, route asset, or explicitly unavailable state;
• one high-rank handler from the current management hand: 韩砚霜, 郁蓝, 沈洛, 白鸦, or equivalent;
• one contested proof object: receipt packet, missing stub, custody copy, black-box fragment, fan oxygen queue receipt, or archive docket copy;
• optional permit support from inspection-shadow-crew-permit.

Affected rites

Use reusable rite ids. A worker may keep legacy ids as aliases, but the canonical playable verbs should not be turn-prefixed.

Required or equivalent:

• rite.receipt_counterclaim_hearing
• rite.defend_chain_with_low_rank_runner
• rite.publish_counter_receipt
• rite.settle_duplicate_receipt
• optional cleanup: rite.quarantine_false_custody_owner

Affected events

Required or equivalent:

• event.receipt_packet_counterclaim
• event.runner_cross_examined_by_white_glove
• event.sponsor_files_duplicate_receipt
• event.fan_queue_identifies_missing_stub
• event.false_custody_owner_hardens

Affected counters and durable states

The replay must expose at least four counter/state deltas from this set:

• receipt_legitimacy
• custody_gap
• archive_debt
• inspection_heat
• sponsor_stop_loss_pressure
• fan_oxygen_resentment
• public_receipt_legitimacy
• runner_risk
• false_custody_owner

Durable tags or states should include at least four of:

• receipt_counterclaim_open
• counterclaim_dismissed
• receipt_publicly_split
• runner_cross_examined
• runner_protected_under_oath
• runner_sacrificed
• false_custody_owner_established
• sponsor_duplicate_receipt
• fan_stub_witnesses_mobilized

Playable branches

Defend the chain

The player assigns 林乔 with 韩砚霜, 郁蓝, 白鸦, 沈洛, or equivalent support. The procedure tests whether the receipt chain can survive cross-examination.

Expected outcome:

• receipt_legitimacy +1 or public_receipt_legitimacy +1;
• custody_gap -1 or archive_debt -1;
• at least one cost rises: runner_risk, inspection_heat, fan_oxygen_resentment, or sponsor_stop_loss_pressure.

Publish the counter-receipt

The player lets a public witness, historian, editor, or fan oxygen queue expose the disputed receipt. This can beat a sponsor duplicate, but it creates public pressure and may make the runner visible.

Expected outcome:

• public_receipt_legitimacy +1 or counterclaim_dismissed;
• fan_stub_witnesses_mobilized or equivalent route state;
• inspection_heat +1, runner_risk +1, or sponsor_stop_loss_pressure +1.

Settle quietly

The player uses 沈洛, sponsor leverage, or legal delay to settle the duplicate receipt without fully proving the chain.

Expected outcome:

• immediate sponsor_stop_loss_pressure pauses or decreases;
• public_receipt_legitimacy remains disputed;
• archive_debt, fan_oxygen_resentment, or custody_gap rises or is deferred as a marked follow-up risk.

Suppress, miss, or sacrifice

The player ignores the hearing, lacks a runner witness, suppresses the fan stub, or sacrifices a low-rank carrier to protect a stronger actor.

Expected outcome:

• false_custody_owner_established, receipt_publicly_split, runner_sacrificed, or runner_hostile_witness becomes durable;
• a later custody rite loses the low-rank defense option;
• custody_gap, archive_debt, or inspection_heat increases.

Oracle assertions

A worker-bound sibling lens should fail unless all assertions below are true.

1. State reachability, not turn identity — The procedure is offered from a valid custody-dispute state. A specific turn may appear in replay evidence, but no assertion may require the canonical page, id, title, tags, or rite names to be turn-prefixed.
2. Prior runner state matters — The procedure branches differently when 林乔 is recruited, route-asset, missed, hostile, or unavailable.
3. Assignable management action — At least one rite accepts assigned cards and records the defender, publisher, negotiator, carrier, or suppressor.
4. Success has cost — A defended or published counterclaim improves receipt/custody/public legitimacy while raising at least one cost counter.
5. Compromise is not victory — Quiet settlement may reduce immediate sponsor pressure, but must leave public legitimacy, fan oxygen, custody, archive, or runner risk unresolved.
6. Failure is durable — Ignoring, suppressing, or mishandling the counterclaim creates a persistent penalty state, lost option, hostile witness, or false custody owner.
7. No high-rank erasure — 韩砚霜, 沈洛, 郁蓝, 白鸦, or any high-rank actor cannot erase all receipt pressure in one clean action.
8. Replay provenance remains evidence only — Evidence must include seed/session id, turn range, offered choices, assigned cards, branch outcomes, and counter deltas; the turn range is proof metadata, not content identity.
9. Backlink health — The procedure must be linked from or to at least one system, one character/card surface, and one event/rite surface. It must not remain an isolated “next turn” page.

Progress metric

Satisfied progress is branch coverage and decontamination quality, not page count.

• 20%: canonical non-turn lens exists and no canonical ids are turn-prefixed.
• 40%: state-triggered receipt counterclaim offer exists with assignable cards.
• 60%: defended or published success branch mutates receipt/custody/public counters and carries a visible cost.
• 80%: compromise or suppression/failure branch creates a durable penalty or deferred route pressure.
• 100%: two divergent replay branches are proven with CLI provenance, and dashboard/lens output shows the non-turn canonical lens id.

Replay evidence shape

lens_id: storyteller.receipt_packet_counterclaim_procedure.v1
session_id: lens-storyteller-receipt-packet-counterclaim-procedure-v1-<timestamp>
seed: <deterministic-seed>
turn_range: <provenance-only, not canonical identity>
preconditions:
  - contested receipt, missing stub, custody copy, fan oxygen queue receipt, or archive docket copy exists
  - prior runner state is recruited, route_asset, missed, hostile, unavailable, or explicitly absent
  - at least one handler can defend, publish, negotiate, audit, carry, or suppress the counterclaim
offered_choices:
  - rite.receipt_counterclaim_hearing
  - rite.defend_chain_with_low_rank_runner
  - rite.publish_counter_receipt
  - rite.settle_duplicate_receipt
  - rite.quarantine_false_custody_owner
assigned_cards:
  defended_or_published_branch:
    - card.lin_qiao_chain_runner or route_asset.lin_qiao_custody_runner or explicit unavailable_runner state
    - han_yanshuang or yu_lan or baiya or shen_luo or equivalent
  compromise_or_failure_branch:
    - sponsor negotiator, suppressing authority, none, or unavailable runner
branches:
  defended_or_published_counterclaim:
    outcome: counterclaim_dismissed or receipt_publicly_contained
    deltas:
      receipt_legitimacy: +1
      custody_gap: -1
      runner_risk: +1
  quiet_settlement:
    outcome: duplicate_receipt_deferred or sponsor_pressure_paused
    deltas:
      sponsor_stop_loss_pressure: -1
      public_receipt_legitimacy: -1
      archive_debt: +1
  suppressed_or_failed_counterclaim:
    outcome: false_custody_owner_established or receipt_publicly_split or runner_sacrificed
    deltas:
      custody_gap: +1
      archive_debt: +1
      inspection_heat: +1
assertions:
  - canonical id is not turn-prefixed
  - offer is state-triggered
  - prior runner state changes branch availability or difficulty
  - success branch has nonzero cost
  - compromise/failure branch has durable penalty
  - evidence is generated by game CLI, not handwritten narrative

Migration rule for turn-prefixed intake artifacts

Old turn-prefixed pages should be treated as archival provenance, not canonical design surfaces. Worker binding should prefer this lens id and reusable rite ids. Future content should create pages around durable procedures, route assets, factions, counters, recruitables, facilities, and failure states. Use turn numbers only to record where replay evidence was observed.

Non-goals

• Not a new numbered turn.
• Not a replacement for game CLI evidence.
• Not bulk filler.
• Not a generic court scene.
• Not a source-level satisfied marker.
• Not a free cleanup for archive custody debt.
• Not a design-process essay; this is a playable lens for a reusable receipt counterclaim procedure.