Package Omission Counterclaim / 包装遗漏反诉机制

Package Omission Counterclaim makes the hidden cost from 稳播包装队列机制 return as playable pressure. A stability package already records its omitted truth; this mechanism asks what happens when that omission gets a carrier, a receipt, and a demand before the package hardens into the only public version.

It exists to prevent a packaged branch from ending at omitted_frame_cost_recorded: true. The cost must be able to become a counterclaim, a correction debt, a custody dispute, a public addendum, a sponsor buyout, or a hardened default.

Mechanism promise

When a package result includes an omitted frame and at least one plausible carrier, the game must expose:

• the source package and selected frame;
• the omitted claimant and omitted truth;
• the carrier who can make the omitted frame actionable;
• the proof, channel, or explicit absence that makes the counterclaim credible;
• at least two answer paths that cannot both become clean;
• a default hardening if the player hides, buys, suppresses, or delays without a record;
• a future reader that consumes whether the omission was answered, bought, split, or hardened.

A package is not finished merely because it is watchable.

State-triggered entry

Open this mechanism only from state pressure:

entry_state:
  trigger_kind: state_pressure
  source_package_state_present: true
  omitted_frame_present: true
  omitted_truth_present: true
  omitted_claimant_or_public_present: true
  counterclaim_carrier_or_absence_visible: true
  future_reader_present: true
  no_fixed_turn_trigger: true
  no_fixed_day_or_week_trigger: true

Valid source packages include sponsor-safe recap, editor checksum package, inspector safety package, fan-public package, management case package, split package with under-scoped reader, and capture default from 稳播包装捕获默认.

Core object model

Object	Meaning	Required observable field
source_package_state	the package being challenged	selected frame, package state, default author if any
omitted_frame_counterclaim	the active counterclaim object	omitted claimant, omitted truth, carrier, proof/channel, requested answer
counterclaim_answer	the player’s chosen answer	addendum, retraction, buyout, split, escrow, quarantine, or refusal
hardening_default	what files first when omission is hidden or underfilled	hardening author, missing field, package state after, future effect
future_reader	route, slot, public statement, lawful use, sponsor gate, or management metric that consumes the result	accepted states and costlier/blocked states

Counterclaim carrier families

Public receipt carrier

A fan witness, unauthorized historian, oxygen ledger, mourning receipt, or pirate-visible proof can carry the omitted public frame. It improves public legitimacy or private-capture resistance, while raising witness exposure, sponsor pressure, fan oxygen resentment, or inspection heat.

Lawful notice carrier

An inspector, archive seal, white-glove notice, or first-custody proof chain can carry an omitted lawful frame. It improves admissibility and false-clean control, while raising bureau debt, schedule pressure, public delay, or lawful-only routing.

Sponsor objection carrier

A sponsor, manager, naming-rights clause, stop-loss note, or slot ledger can carry an omitted sponsor frame. It reduces immediate budget or slot pressure, while increasing contract capture, public distrust, or sponsor-only routing.

Editor checksum carrier

A cutroom checksum, black-box edit note, continuity patch, or version table can carry an omitted edit frame. It improves watchability and continuity, while increasing edit debt, source ambiguity, or reality drift.

Boundary carrier

An artist refusal, voice-body boundary, witness safety row, or consent receipt can carry an omitted boundary frame. It improves harm prevention and consent clarity, while delaying route unlocks and raising handler burden, sponsor pressure, or fan expectation cost.

State machine

State	Meaning	Required consequence
omission_dormant	omitted frame is only recorded as package cost	no counterclaim branch is available yet
counterclaim_armed	carrier, omitted truth, and future reader are visible	player must answer or record absence
addendum_filed	package keeps selected frame but appends omitted truth	package remains usable with future surcharge
package_retracted	selected frame is weakened or withdrawn	sponsor/editor/management relief can reverse
buyout_or_release	omitted claimant is paid, released, or contractually narrowed	capture and resentment scars remain visible
split_answer	selected and omitted frames both receive scoped readers	future routes require split acceptance
escrowed_counterclaim	proof is preserved but not yet aired	current relief persists, future appeal cost rises
hardening_default	omission is ignored, hidden, or cited as settled	omitted frame becomes hostile, public-only, lawful-only, sponsor-only, or recovery-only

Branch contract

Branch A — File addendum

The player keeps the original package but appends the omitted truth with a named carrier and proof/channel.

Expected outcome: public or lawful legitimacy improves; package legibility becomes costlier; sponsor, editor, or management cleanliness drops; future readers require addendum-aware acceptance.

Branch B — Retract or weaken package

The player admits the package cannot stand as framed.

Expected outcome: false-clean risk falls; immediate stability, sponsor confidence, schedule pressure, or audience churn worsens; future readers may accept only a scarred package.

Branch C — Buyout or release

The player pays, releases, narrows, or contractually settles the omitted claimant without making the omitted frame central.

Expected outcome: current broadcast pressure falls; contract capture, public distrust, fan resentment, or future claim cost rises; the omission remains discoverable.

Branch D — Split answer

The player scopes selected and omitted frames to different readers without pretending they are one truth.

Expected outcome: contradiction is legible; handler burden, archive debt, source ambiguity, or correction cost rises; future routes require split or bridge.

Branch E — Escrow and delay

The player preserves proof and delays public answer because the carrier is unsafe, proof is weak, or the channel would cause larger harm.

Expected outcome: hostile hardening is delayed; slot pressure, public delay, inspection heat, or witness distrust rises; future appeal remains armed.

Branch F — Quarantine or refuse

The player blocks the counterclaim because carrier/proof/channel is false, unsafe, or captured.

Expected outcome: fraud or boundary harm improves; claimant hostility, public distrust, or recovery-only routing rises.

Branch G — Hardening default

The player hides, underfills, suppresses, or treats the omitted frame as already settled.

Expected outcome: a hardening author is named; package state becomes false-clean, hostile, sponsor-only, lawful-only, public-only, contradiction-pending, or recovery-only.

Counter contract

Every resolved branch must mutate at least three durable surfaces: one relief, one cost, and one future-reader effect.

Relevant values:

• omitted_frame_pressure
• package_legibility
• package_integrity
• public_receipt_legitimacy
• public_receipt_distrust
• sponsor_stop_loss_pressure
• contract_capture
• edit_debt
• source_ambiguity
• inspection_heat
• bureau_favor_debt
• fan_oxygen_resentment
• witness_exposure
• artist_refusal_respected
• voice_integrity_risk
• handler_burden
• future_clearance_cost
• correction_slot_pressure
• reader_collision
• route_package_state

Integration rules

• Stability Package Queue creates the source package and omitted frame; this mechanism makes that omission actionable later.
• 裁定读者冲突 consumes the result if two readers disagree about whether the addendum, split, buyout, or default is acceptable.
• 叙述优先栈线 consumes the result if the omitted carrier can narrate before the official package answers.
• 公开悔过账本 consumes addendum, retraction, or apology debt.
• 更正档期竞拍线 consumes correction pressure when the answer needs airtime.
• Broadcast Reality reads whether the omission became addendum, split canon, false-clean memory, or recovery-only scar.

Replay evidence contract

mechanic: storyteller.mechanic.package_omission_counterclaim.v1
session_id: lens-package-omission-counterclaim-v1-<timestamp>
seed: <deterministic-seed>
entry_state:
  trigger_kind: state_pressure
  source_package_state_present: true
  selected_frame: <frame>
  omitted_frame: <frame>
  omitted_truth: <truth>
  carrier_or_absence: <carrier or explicit_absence>
  future_reader: <reader>
  no_fixed_turn_trigger: true
counterclaim:
  omitted_claimant: <claimant>
  requested_answer: addendum | retraction | buyout | split | escrow | quarantine | refusal
  proof_or_absence: <proof or explicit_absence>
  channel_or_absence: <channel or explicit_absence>
branch_run:
  selected_answer: <answer>
  package_state_after: <state>
  omitted_frame_state_after: <state>
  counter_deltas:
    relief: []
    cost: []
    future: []
assertions:
  - entry_is_state_triggered_from_omitted_frame
  - omitted_truth_and_carrier_are_visible
  - answer_requires_proof_channel_handler_or_explicit_absence
  - branches_diverge_by_package_state_and_future_reader
  - success_has_relief_cost_and_future_gate
  - hardening_default_is_durable
  - no_fixed_turn_trigger

Non-goals

• Not a generic backlash meter.
• Not a second PR recap.
• Not governance or dashboard content.
• Not raw lens-count growth.
• Not a fixed calendar correction beat.
• Not a replacement for 裁定读者冲突线; it creates the omission answer that later readers may accept or reject.
• Not valid if the omitted truth can be erased without a carrier, proof/channel, named hardening author, and future route mutation.