Stability Package Queue / 稳播包装队列机制

Stability Package Queue makes corporate entertainment-stability pressure playable after a crisis becomes packageable. The archive may know what happened, the editor may know what can be shown, the sponsor may know what must sound safe, the inspector may know what can be lawful, and the fan public may know what must not be sanitized. The mechanism makes those frames compete before one becomes broadcast reality.

This is the strongest next gap because the vault already contains many rulings, custody transfers, stability prices, and management-compression surfaces. What remains under-specified is the public packaging step: who authors the watchable version when sponsor, editor, inspector, and fan public all demand a different frame?

Mechanism promise

When a prior resolution creates material that can be turned into a stable public package, the game must show:

• the package subject;
• at least two claimant frames;
• the input each frame needs;
• the truth each frame omits;
• a selected frame and counter-frame or explicit absence;
• a package handler and proof anchor or explicit absence;
• a future route, slot, or mechanism that reads the resulting package state.

A clean stabilization cannot mean every audience remembers the same harmless thing.

State-triggered entry

Open the queue when all of the following are true:

entry_state:
  trigger_kind: state_pressure
  source_crisis_or_resolution_present: true
  package_subject_present: true
  package_claimants_min: 2
  future_reader_present: true
  default_author_present: true
  no_fixed_turn_trigger: true

Valid source surfaces include Broadcast Stability Escrow, Public Contrition Ledger, Cutroom Priority Queue, Production Triage Desk, Management Compression Desk, a memorial copy, fan oxygen receipt, lawful hold, sponsor bridge, edit patch, or route asset.

Core object model

Object	Meaning	Required observable field
stability_package_slate	visible package queue card	source, subject, claimant rows, assignment, default author, future reader
package_subject	the event, person, proof, slot, or route asset being packaged	id, kind, current public state, source relief/debt
claimant_frame	sponsor/editor/inspector/fan/management package demand	desired frame, required input, omitted truth, future effect
package_assignment	selected public frame and counter-frame	handler, proof anchor, bridge/cost, explicit absence
package_capture_default	what happens when a frame files first or required inputs are absent	default author, missing inputs, package state after, future route effect
future_reader	route/slot/mechanic that reads package state	accepted states and rejected/costlier states

Claimant frame families

Sponsor frame

A sponsor frame uses relief money, naming rights, stop-loss language, or gratitude montage to lower immediate schedule and sponsor pressure.

It usually omits oxygen debt, consent boundary, public grief, witness discomfort, or source ambiguity. It risks contract_capture, public_receipt_distrust, and sponsor_only route state.

Editor frame

An editor frame uses checksum, montage, delay mask, or continuity smoothing to keep the package watchable.

It usually omits raw receipt, body/voice mismatch, edit debt, or source ambiguity. It risks edit_debt, reality_drift, and edit_checksum_required future state.

Inspector frame

An inspector frame uses lawful hold, safety notice, audit table, or admissible explainer.

It usually omits immediacy, emotional audience relief, sponsor schedule, or informal public truth. It risks inspection_heat, bureau_favor_debt, lawful_only, and schedule pressure.

Fan-public frame

A fan-public frame uses mourning receipt, oxygen ledger, public table, unauthorized historian proof, or pirate relay.

It usually omits witness privacy, sponsor comfort, lawful quiet, or corporate stability metrics. It risks fan_oxygen_liability, witness_exposure, public_only, and sponsor pressure.

Management frame

A management frame uses case-study language, efficiency metrics, liability cap, or success reporting.

It usually omits source debt and who paid it. It risks false_clean_metric, handler_burden, future claim cost, and metric appeal.

State machine

State	Meaning	Required consequence
queue_unopened	package pressure does not yet exist	no package branch is available
slate_open	package subject and claimant frames are visible	player can arbitrate, split, hold, refuse, or default
frame_selected	one frame receives handler/proof/bridge	omitted frame becomes cost or counter-package
split_package	two frames are made legible without pretending unity	future routes require bridge or split acceptance
package_held	false clean package is blocked	audience/schedule/sponsor pressure rises
package_captured	one claimant authors first	default event records author, missing inputs, future route effect
blackout_recovery_only	absence itself became the package	future route requires rebuild or blackout recovery

Branch contract

Branch A — Sponsor-safe package

The player chooses sponsor-safe public relief.

Expected outcome: sponsor or schedule pressure falls, while contract capture, public distrust, fan resentment, or sponsor-only routing rises.

Branch B — Editor checksum package

The player chooses a cutroom-stable version.

Expected outcome: attention and continuity improve, while edit debt, source ambiguity, reality drift, or checksum-required routing rises.

Branch C — Inspector safety package

The player chooses an audit-facing safety package.

Expected outcome: false-clean use is blocked and legality improves, while inspection heat, bureau debt, schedule pressure, or lawful-only routing rises.

Branch D — Fan-public package

The player chooses public grief, oxygen receipt, pirate relay, or unauthorized historian proof as the frame.

Expected outcome: private capture is blocked and public legitimacy rises, while exposure, sponsor pressure, oxygen liability, or public-only routing rises.

Branch E — Split package

The player makes two frames legible with a named bridge and records the contradiction.

Expected outcome: stability rises without pretending the frames are one; package complexity, handler burden, future clearance cost, or split-required routing rises.

Branch F — Refuse or hold package

The player blocks false clean packaging and accepts present instability.

Expected outcome: false clean package is prevented, while audience churn, schedule pressure, sponsor pressure, or lawful/public rebuild cost rises.

Branch G — Default author captures

The slate is hidden, underfilled, or ignored; one claimant authors first.

Expected outcome: 稳播包装捕获默认 fires or is armed with default author and future route effect.

Counter and durable-state contract

Every branch must mutate at least three values. One must be relief, one must be cost, and one must be future-route or slot state.

Primary values:

• package_legibility
• package_capture_pressure
• audience_stability
• audience_churn
• public_receipt_legitimacy
• public_receipt_distrust
• sponsor_stop_loss_pressure
• contract_capture
• edit_debt
• source_ambiguity
• inspection_heat
• bureau_favor_debt
• fan_oxygen_resentment
• fan_oxygen_liability
• reality_drift
• schedule_pressure
• black_screen_slots
• future_clearance_cost
• handler_burden
• false_clean_metric
• route_package_state

Integration rules

• Broadcast Stability Escrow prices whether a version can be held; this mechanism decides who authors the package once the version must be shown.
• Cutroom Priority Queue can supply or withhold edit checksum and montage capacity.
• Public Contrition Ledger can supply public admission or public anger as a package frame.
• Production Triage Desk can make packaging compete with other crisis tickets for handler, public, sponsor, edit, legal, schedule, or oxygen lanes.
• Management Compression Desk reads management packages as possible false-clean metric rows.
• Broadcast Reality reads which package hardened into public memory.

Replay evidence contract

mechanic: storyteller.mechanic.stability_package_queue.v1
session_id: lens-stability-package-queue-v1-<timestamp>
seed: <deterministic-seed>
entry_state:
  trigger_kind: state_pressure
  package_subject_present: true
  package_claimants_min: 2
  future_reader_present: true
  no_fixed_turn_trigger: true
offered:
  card: storyteller.card.stability_package_slate.v1
  rite: storyteller.rite.stability_package_arbitration.v1
slate:
  package_subject: <id>
  claimant_rows: []
assignment:
  selected_frame: <frame>
  counter_frame_or_absence: <frame_or_absence>
  package_handler_or_absence: <handler_or_absence>
  proof_anchor_or_absence: <proof_or_absence>
  bridge_or_cost: <bridge_or_cost>
result:
  package_state_after: <state>
  omitted_frame_cost_recorded: true
  future_route_effect: <effect>
  counter_deltas: {}
assertions:
  - entry_is_state_triggered
  - slate_records_subject_claimants_inputs_omissions_and_future_reader
  - rite_requires_selected_frame_counter_frame_handler_proof_bridge_or_absence
  - branches_diverge_by_package_state_cost_and_future_reader
  - success_has_visible_cost
  - capture_default_records_author_missing_inputs_and_future_effect
  - no_fixed_turn_trigger

Non-goals

• Not a PR simulator.
• Not governance.
• Not a popularity-meter wrapper.
• Not a raw count expansion.
• Not a fixed broadcast-calendar beat.
• Not a replacement for proof, custody, stability escrow, production triage, or management compression.
• Not valid if sponsor, editor, inspector, fan, and management frames all resolve to the same clean audience state.