Package Omission Counterclaim / 包装遗漏反诉线

Package Omission Counterclaim is a pressure-system storyline that begins after 稳播包装队列线 has produced a package with a recorded omitted frame. The official package may have stabilized broadcast reality, but the omission now has a carrier and a future reader.

The storyline makes the omitted truth playable instead of leaving it as a passive cost row.

Why this is the next useful expansion

The current mesh can already create package subjects, claimant frames, default authors, first-custody receipts, reader collisions, narration priority, public contrition, and correction-slot pressure. The weak afterlife is narrower: when a stability package survives by omitting a truth, the omitted frame needs a playable return path before it becomes just another remembered scar.

This storyline adds that return path through 包装遗漏反诉机制, 遗漏框架反诉, 遗漏框架应答, and 遗漏框架硬化默认.

State-triggered entry

Open this storyline only when all of the following are true:

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

The storyline does not open from a fixed turn, fixed day, chapter quota, raw page count, dashboard state, or generic upkeep phase.

Content pack

Mechanism

• 包装遗漏反诉机制 defines omitted-frame carriers, answer modes, hardening default, branch costs, and future-reader consequences.

Card

• 遗漏框架反诉 records the source package, selected frame, omitted frame, omitted truth, carrier, proof/channel/handler, requested answer, future reader, and default if unanswered.

Rite

• 遗漏框架应答 resolves addendum, retraction, buyout/release, split answer, escrow/delay, quarantine/refuse, and explicit no-answer branches.

Event

• 遗漏框架硬化默认 fires or arms when the counterclaim is hidden, underfilled, bought without release, escrowed without future reader, quarantined without reason, or treated as settled.

Storyline spine

Beat 1 — The package leaves an actionable omission

A prior stability package resolves immediate pressure but records an omitted truth.

package_omission_entry:
  source_package_slate: storyteller.card.stability_package_slate.v1
  source_subject: <subject_id>
  selected_frame: <frame>
  package_state_before: <state>
  omitted_frame: <frame>
  omitted_truth: <truth>
  future_reader: <reader>

Valid examples:

• sponsor-safe package omits fan oxygen debt;
• editor checksum package omits lawful timestamp or raw witness discomfort;
• inspector safety package omits sponsor promise and public relief expectation;
• fan-public package omits artist boundary or witness safety;
• management case package omits crew scar or false-clean metric;
• capture default omits excluded reader or counter-frame.

Beat 2 — A carrier makes the omission actionable

The omission must not become playable without a carrier. The carrier can be a fan witness, unauthorized historian, lawful notice, sponsor sideletter, cutroom checksum, artist boundary receipt, first-custody slip, route asset, or explicit absence.

Create 遗漏框架反诉:

counterclaim_card:
  omitted_claimant: <claimant>
  carrier_type: <carrier_type>
  proof_anchor_or_absence: <proof or explicit_absence>
  channel_or_absence: <channel or explicit_absence>
  handler_or_absence: <handler or explicit_absence>
  requested_answer: <answer>
  default_if_unanswered: <hardening_state>

Beat 3 — The player answers the omission

Offer 遗漏框架应答. The player chooses how to answer the omission and pays a finite cost.

The answer cannot make the source package clean. It can only make the scar legible, paid, scoped, delayed, quarantined, or hardened.

Beat 4 — Future readers accept, surcharge, or reject

The branch must alter a future reader:

• a public statement may require addendum;
• a lawful route may require appeal;
• a sponsor gate may accept only release clause;
• a correction slot may charge the package;
• a reader-collision row may reopen with split acceptance;
• a route asset may refuse transport without the omitted frame;
• a management metric may lose clean-yield status.

Beat 5 — Silence hardens the omission

If the player hides or underfills the card, treats omission as settled, buys without release, suppresses without record, or escrow-buries proof, 遗漏框架硬化默认 names who hardened the omission.

Default is not failure text. It mutates package state, omitted-frame state, future route access, and at least one cost surface.

Branch map

Branch	Immediate relief	Cost/scar	Future state
File addendum	public/lawful legitimacy rises	correction slot, sponsor pressure, edit debt, exposure	addendum_required, accepted_with_surcharge
Retract package	false-clean risk drops	stability, sponsor, schedule, or audience pressure worsens	scarred_acceptance_only, correction_required
Buyout / release	current broadcast pressure falls	contract capture, distrust, resentment, future claim cost	sponsor_only or accepted_with_release_clause
Split answer	selected and omitted frames both visible	handler burden, archive debt, source ambiguity	split_required, contradiction_pending
Escrow and delay	hardening delayed, safety preserved	public delay, inspection heat, claimant distrust	appeal_armed, correction_slot_due
Quarantine / refuse	false or unsafe counterclaim blocked	claimant hostility, route recovery cost	blocked_until_reproof, boundary_gated
Hardening default	immediate dispute may pause	hostile omission, capture, false-clean memory	public_only, lawful_only, sponsor_only, recovery_only

Character and faction hooks

• Yu Lan Storyline can carry unauthorized-history or public-table omissions.
• Huo Qian Storyline can carry fan-witness and oxygen-receipt omissions.
• Orion Breath Storyline can harden sponsor release, buyout, or stop-loss omissions.
• Han Cutroom Storyline can carry checksum omissions or patch over source ambiguity.
• 裁定读者冲突线 can consume split answer, addendum, or false universal hardening.
• 公开悔过账本 and 更正档期竞拍线 can consume addendum, retraction, or apology debt.

Missability

This storyline is missed when implementation:

• treats omitted truth as passive flavor;
• opens the branch from a fixed turn or fixed date;
• offers generic PR repair without source package, carrier, proof/channel, handler, and future reader;
• lets buyout delete discoverability;
• lets split answer become universal acceptance;
• lets default hardening change only mood or reputation;
• does not mutate future route, public statement, lawful use, sponsor gate, correction slot, route asset, or management metric.

Recovery is allowed only through cost: public addendum, correction slot, lawful appeal, split package, release proof, route recovery, or blackout/scar repair.

Replay evidence expectation

storyline_id: storyteller.storyline.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
offered:
  card: storyteller.card.omitted_frame_counterclaim.v1
  rite: storyteller.rite.omitted_frame_answer.v1
branch_runs:
  answered_branch:
    selected_answer: addendum | retraction | buyout_release | split_answer | escrow_delay | quarantine_refuse
    proof_anchor_or_absence: <proof or explicit_absence>
    channel_or_absence: <channel or explicit_absence>
    handler_or_absence: <handler or explicit_absence>
    package_state_after: <state>
    omitted_frame_state_after: <state>
    future_reader_effect: <effect>
    counter_deltas: {}
  default_branch:
    event_seen_or_armed: storyteller.event.omitted_frame_hardening_default.v1
    hardening_author: <author>
    hardening_reason: <reason>
    package_state_after: <state>
    omitted_frame_state_after: <state>
    future_reader_effect: <effect>
    counter_deltas: {}
assertions:
  - entry_is_state_triggered_from_omitted_package_frame
  - counterclaim_card_records_source_omission_carrier_requested_answer_and_future_reader
  - rite_requires_answer_mode_proof_channel_handler_cost_and_future_reader
  - answered_branches_diverge_by_package_state_omitted_frame_state_and_future_effect
  - default_hardening_names_author_missing_inputs_and_excluded_reader
  - no_fixed_turn_trigger

Non-goals

• Not raw content-count expansion.
• Not a generic backlash storyline.
• Not a dashboard or governance page.
• Not a second stability package queue.
• Not a replacement for reader collision or narration priority; it supplies a concrete omission answer that those systems may later consume.
• Not valid if the omitted frame cannot return with a carrier, proof/channel, handler/absence, future reader, and durable default.