Receipt Counterclaim Hearing

Why this gap is the next useful target

The vault already has a reusable receipt-packet-counterclaim-procedure.lens and a strengthened route-assets-and-custody state machine, but rites/storyteller only had the older shadow evidence transfer page. The current blocker for local play/build evidence is therefore a missing assignable rite: workers need a concrete hearing action that can accept a carrier, a handler, a disputed proof object, and a faction posture.

This rite is the bindable management action for receipt-packet-counterclaim. It turns a receipt dispute into playable cost, branch divergence, and durable custody state rather than another numbered-turn lens.

Affected wiki/source addresses

Primary new surface:

  • wiki/content/rites/storyteller/receipt-counterclaim-hearing.md

Triggered by:

  • wiki/content/events/storyteller/receipt-packet-counterclaim.md

Observed and constrained by:

  • wiki/content/lens/storyteller/receipt-packet-counterclaim-procedure.lens.md
  • wiki/content/systems/route-assets-and-custody.md
  • wiki/content/characters/storyteller/lin-qiao-chain-runner.md
  • wiki/content/storylines/characters/lin-qiao-chain-runner.md
  • wiki/content/cards/storyteller/inspection-shadow-crew-permit.md
  • wiki/content/events/storyteller/shadow-crew-custody-leak.md

Related prior transfer surface:

  • wiki/content/rites/storyteller/turn54-shadow-evidence-transfer.md

Rite identity

  • Canonical id: storyteller.rite.receipt_counterclaim_hearing.v1
  • Game id: rite.receipt_counterclaim_hearing
  • Role: state-triggered assignable management rite for a disputed proof object.
  • Availability: after event.receipt_packet_counterclaim or any equivalent contested custody proof event.
  • Duration band: same-day hearing or one-day emergency hearing; never a long-operation filler rite.
  • Slot pressure: consumes one management action and one legal/inspection/publicity posture.

Required inputs

The rite should not be offered unless the state contains all four inputs.

  1. Disputed proof — receipt packet, missing stub, fan oxygen queue receipt, archive docket copy, black-box fragment, memorial air receipt, voice custody receipt, inspection handoff note, or sponsor duplicate.
  2. Carrier state — 林乔 as card/route asset, another low-rank runner such as 岑微, or an explicit runner_missed, runner_hostile_witness, runner_sacrificed, or unavailable state.
  3. Handler or posture — 韩砚霜, 郁蓝, 沈洛, 白鸦, 黎星瞳, sponsor counsel, archive clerk, fan witness coordinator, or explicit no-show/suppression posture.
  4. Faction claim pair — at least two claimants among archive authority, inspector authority, sponsor stop-loss desk, fan oxygen public, black-box editor custody, memorial claimant, voice claimant, or low-rank service corridor staff.

Assignment slots

A replay should expose assignments or explicit absence for these slots:

SlotExamplesPurpose
carrier林乔, 岑微, route asset, hostile witness, missed runner, unavailable runnerDetermines whether the chain can be defended physically.
handler韩砚霜, 郁蓝, 沈洛, 白鸦, 黎星瞳, sponsor counselDetermines legitimacy, publication, settlement, edit, or suppression posture.
proofmissing stub, fan queue receipt, archive docket copy, black-box fragment, sponsor duplicateDetermines which counter and faction claims move.
costpetty cash, favor debt, payroll leak, inspection heat, fan resentment, sponsor retaliationMakes success non-free.

Stat and difficulty hooks

Implementation can use any equivalent stat names, but the rite should expose at least three checks or difficulty modifiers:

  • chain_legibility — improves with inspection permit, route asset carrier, or archive docket copy; worsens with missing/hostile carrier.
  • public_pressure — improves with 郁蓝 or fan witness proof; worsens sponsor retaliation and inspection visibility.
  • runner_risk — rises when a low-rank carrier testifies, is underpaid, or is sacrificed.
  • sponsor_leverage — rises when a duplicate receipt exists or when settlement posture is used.
  • archive_debt — rises when settlement or suppression preserves ambiguity.

Playable choices

Choice A — Defend chain with low-rank carrier

Assign a carrier plus handler to survive challenge.

Required: recruited/route-asset carrier or temporary runner plus a handler.

Expected effects:

  • receipt_legitimacy +1 or public_receipt_legitimacy +1;
  • custody_gap -1 or archive_debt -1;
  • runner_risk +1, inspection_heat +1, favor_debt +1, or payroll_leak +1;
  • durable state: runner_protected_under_oath, runner_cross_examined, or counterclaim_dismissed.

Choice B — Publish counter-receipt

Assign 郁蓝, 白鸦, a fan witness coordinator, or an equivalent publication actor to split the duplicate claim in public.

Expected effects:

  • public_receipt_legitimacy +1;
  • fan_stub_witnesses_mobilized or receipt_publicly_split;
  • sponsor_stop_loss_pressure +1, inspection_heat +1, runner_risk +1, or fan_oxygen_resentment +1.

Choice C — Settle duplicate receipt

Assign 沈洛, sponsor counsel, archive clerk, or equivalent negotiator to pause the fight without proving the chain.

Expected effects:

  • sponsor_stop_loss_pressure -1 or immediate legal/inspection pressure pauses;
  • archive_debt +1, custody_gap +1, or public_receipt_legitimacy -1;
  • durable state: sponsor_duplicate_receipt, duplicate_receipt_deferred, or receipt_counterclaim_open.

Choice D — Suppress, no-show, or sacrifice carrier

Use no carrier, suppress fan proof, sacrifice the low-rank runner, or allow a hostile/missed runner state to control the hearing.

Expected effects:

  • durable state: runner_sacrificed, runner_hostile_witness, false_custody_owner_established, or receipt_publicly_split;
  • suppress or raise difficulty on rite.chain_safe_small_delivery, rite.defend_chain_with_low_rank_runner, or any equivalent future custody action;
  • custody_gap +1, archive_debt +1, inspection_heat +1, or false_custody_owner +1.

Costs and failure pressure

A successful hearing must spend or risk at least one resource. Valid costs include:

  • money or petty cash;
  • favor debt with low-rank staff, fans, inspectors, sponsors, or archive clerks;
  • payroll leak;
  • fan oxygen resentment;
  • inspection heat;
  • sponsor retaliation;
  • runner risk;
  • public legitimacy exposure;
  • suppression of a future custody delivery.

Failure must be recoverable but non-cosmetic. A bad hearing should create a false owner, hostile witness, public split, higher archive debt, or a missing carrier option that later rites can observe.

Oracle assertions

A sibling executable check should fail unless all claims below are true.

  1. Event-gated offer — The rite is offered only after event.receipt_packet_counterclaim or an equivalent contested proof state.
  2. Assignments are explicit — Replay records carrier, handler/posture, proof object, and cost or explicit absence for each.
  3. Carrier state changes choices — Recruited/route-asset carrier, missed carrier, hostile carrier, sacrificed carrier, and unavailable carrier do not produce identical branch availability.
  4. Success has cost — Defend or publish improves custody/receipt/public legitimacy and increases or spends at least one pressure resource.
  5. Settlement is not clean success — Quiet settlement can pause one immediate pressure but must leave or create archive, custody, fan, public, or deferred duplicate debt.
  6. Failure is durable — Suppress/no-show/sacrifice creates a persistent tag, counter delta, lost option, false owner, or hostile witness.
  7. High-rank actors cannot erase logistics — 韩砚霜, 沈洛, 郁蓝, 白鸦, 黎星瞳, or sponsor counsel cannot satisfy the rite without a proof object and carrier/witness/explicit absence state.
  8. Evidence is replay-derived — Pass/fail evidence comes from CLI session history with seed, session id, offered choices, assignments, outcomes, and counter deltas.

Progress metric

Progress is measured by playable branch coverage, not number of pages or rites.

  • 20%: rite can be offered from a contested proof event/state.
  • 40%: replay records carrier, handler, proof, faction claim pair, and cost slot.
  • 60%: defend or publish branch resolves with legitimacy/custody improvement plus nonzero cost.
  • 80%: settlement or suppress/no-show/sacrifice branch creates durable deferred pressure or failure state.
  • 100%: at least two divergent CLI replays prove branch distinction, assignments, outcomes, and counter deltas under storyteller.receipt_packet_counterclaim_procedure.v1.

Replay/session evidence shape

rite_id: storyteller.rite.receipt_counterclaim_hearing.v1
game_id: rite.receipt_counterclaim_hearing
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>
preconditions:
  event: event.receipt_packet_counterclaim
  disputed_proof: missing_stub | fan_queue_receipt | archive_docket_copy | black_box_fragment | sponsor_duplicate | memorial_air_receipt | voice_custody_receipt
  carrier_state: recruited | route_asset | temporary_runner | missed | hostile | sacrificed | unavailable
  claimant_factions:
    - archive_authority_or_equivalent
    - sponsor_or_inspector_or_fan_public_or_equivalent
offered_choices:
  - defend_chain_with_low_rank_carrier
  - publish_counter_receipt
  - settle_duplicate_receipt
  - suppress_no_show_or_sacrifice_carrier
assigned_slots:
  carrier: card.lin_qiao_chain_runner | route_asset.lin_qiao_custody_runner | cen_wei | missed_runner | hostile_runner | none
  handler: han_yanshuang | yu_lan | shen_luo | baiya | li_xingtong | sponsor_counsel | archive_clerk | none
  proof: <proof-id-or-type>
  cost: petty_cash | favor_debt | payroll_leak | inspection_heat | fan_oxygen_resentment | sponsor_retaliation | runner_risk
branches:
  defend_or_publish:
    outcome: counterclaim_dismissed | receipt_publicly_contained | runner_protected_under_oath
    deltas:
      receipt_legitimacy: +1
      custody_gap: -1
      runner_risk: +1
  settle:
    outcome: duplicate_receipt_deferred | sponsor_pressure_paused
    deltas:
      sponsor_stop_loss_pressure: -1
      archive_debt: +1
      public_receipt_legitimacy: -1
  suppress_or_fail:
    outcome: false_custody_owner_established | runner_sacrificed | runner_hostile_witness | receipt_publicly_split
    deltas:
      custody_gap: +1
      archive_debt: +1
      false_custody_owner: +1
assertions:
  - rite is event-gated
  - carrier state changes branch availability or difficulty
  - positive branch has nonzero cost
  - settlement or failure leaves durable pressure
  - evidence is generated by game CLI replay/session history

Non-goals

  • Not a new numbered turn continuation.
  • Not bulk filler.
  • Not raw scale-count satisfaction.
  • Not a central/manual lens registry.
  • Not a generic legal scene.
  • Not a free archive custody cleanup.
  • Not handwritten replay/session evidence.
  • Not a replacement for receipt-packet-counterclaim; this is the assignable rite that resolves or worsens that event.