Producer Alibi Recall / 制作人抗辩召回线

Producer Alibi Recall is the pressure-system storyline for the moment a later reader asks why the producer made an earlier management choice.

The source action may already be replay-visible: the producer chose a sponsor package over a fan table, used a memorial voice under archive pressure, cut a public recap, sealed a proof, preserved a route asset, accepted a lawful narrowing, or let a hostile claimant speak first. This storyline binds the next layer: the stated reason for that action becomes a custody object.

Primary playable question

When an earlier management decision is recalled by an archive, voice, memorial, sponsor, fan, inspector, editor, broadcast-reality, or route reader, does the producer narrow the alibi, back it with witness proof, amend the archive reason, split public and internal wording, retract and pay, or let hostile intent become default truth?

The answer must be visible as alibi state, relying-reader state, harmed-reader state, counter deltas, and future route effect. No reason may become clean universal permission.

Gap diagnosis

The current mesh already has strong coverage for custody and consequence:

• 播出资产来源后生线 tracks derivative copies after broadcast.
• 路线资产维护分诊线 prevents earlier route assets from staying fresh forever.
• 跨台前例召回线 prevents scoped old results from becoming false policy.
• 未采纳报价回执线 preserves the material offers the player did not choose.
• 压力认领人转化链 converts default narrators into claimant rows before they harden.

The remaining high-value gap is management intent. Those systems can prove what was selected, what was declined, which copy survived, which precedent was cited, and which claimant appeared. They still do not always prove whether the reason attached to a source decision is scoped, supported, contradicted, or hostile-authored before a later voice, memorial, archive, or public reader consumes it.

This storyline makes early management rationale matter in late custody without creating morality, PR, or turn-count content.

Bound content pack

This storyline binds:

• 制作人抗辩召回机制;
• 制作人抗辩账本;
• 抗辩范围听证;
• 敌意意图默认.

State-triggered entry

Open this storyline only when all required live state is visible:

entry_state_required:
  trigger_kind: state_pressure
  source_decision_present: true
  source_decision_needed_reason: true
  source_branch_or_route_effect_visible: true
  alibi_present_or_required_absence_recorded: true
  relying_reader_present: true
  harmed_or_excluded_reader_present_or_explicit_absence: true
  proof_anchor_or_explicit_absence_visible: true
  future_route_or_custody_effect_possible: true
  player_can_accept_publish_amend_split_retract_or_default: true
  no_fixed_turn_trigger: true
  no_fixed_day_or_week_trigger: true
  no_raw_statement_count_trigger: true
  no_dashboard_or_lens_health_trigger: true

The storyline fails if it opens from fixed sequence position, calendar cadence, chapter quota, raw statement count, generic outrage, dashboard state, lens health, or private intent that no later reader can cite.

Storyline spine

Beat 1 — A source decision needed a reason

A branch resolved under pressure. The player may have used emergency care, lawful duty, sponsor continuity, fan safety, archive preservation, memorial respect, edit integrity, consent proxy, commercial rescue, silence, or a hostile claimant’s statement as the reason.

The game creates or updates 制作人抗辩账本.

source_decision:
  source_session_id: <session or explicit_absence>
  source_surface: schedule | archive | voice | memorial | fan_oxygen | sponsor | inspection | edit | broadcast_reality | route_asset | equivalent
  source_branch_id: <branch id>
  chosen_action: <action>
  declined_offer_receipt_or_absence: <receipt or explicit_absence>
  immediate_relief: <relief>
  immediate_cost: <cost>

Beat 2 — A later reader tries to consume the reason

A future archive, voice probate, memorial claimant, sponsor desk, fan public, inspector, editor, broadcast-reality check, or route gate cites the alibi.

The reader may accept it, narrow it, demand proof, expose contradiction, or punish a hidden harmed reader.

Beat 3 — Scope and proof become playable

The ledger must show:

• alibi kind;
• wording state;
• stated-by actor;
• proof anchor or explicit absence;
• relying reader;
• harmed or excluded reader;
• scope boundary;
• future route effect.

A famous handler can help, but cannot make the alibi universal. Shen Luo can draft a narrow sponsor-safe clause; Yu Lan can publish a witness-backed public version; Han Yanshuang can amend archive admissibility; Baiya can checksum the edit reason. Each produces cost.

Beat 4 — The player holds the alibi scope hearing

Run 抗辩范围听证.

Valid postures:

1. accept narrow alibi;
2. publish witness backing;
3. amend archive reason;
4. split public and internal alibi;
5. retract and pay;
6. let hostile intent default.

Beat 5 — Hostile intent becomes durable if ignored

If a future reader consumes an unscoped, unsupported, missing, contradicted, or hostile-authored reason, 敌意意图默认 fires or arms. The event must name source decision, failed requirement, hostile narrator, hostile claim, relying reader, harmed or excluded reader, state after, and future route effect.

Branch map

Branch	Immediate relief	Cost/scar	Future state
Accept narrow alibi	license, archive, or reader clarity improves	route scope narrows, handler burden rises	same-facts-only, scope hearing required for changed facts
Publish witness backing	public legitimacy or hostile-intent pressure improves	witness exposure, sponsor pressure, inspection heat	public addendum required, protection required
Amend archive reason	lawful, voice, or memorial reader becomes safer	archive debt, bureau favor debt, public distrust	lawful bridge required, archive-only or voice-only scope
Split public/internal alibi	public panic, sponsor, or schedule pressure falls	broadcast-reality drift and reader conflict rise	split reader required, later correction armed
Retract and pay	hostile-intent pressure or harmed-reader distrust falls	license, sponsor, voice, memorial, or fan cost rises	costlier route, recovery with confession
Hostile intent default	immediate burden disappears or hostile narrator wins	bad-faith claim hardens	blocked, hostile, lawful bridge, consent bridge, recovery-only

Counter contract

Every branch must change at least three counters or durable states. One must be relief, one must be cost, and one must alter future route acceptance, required bridge, reader scope, or recovery state.

Primary surfaces:

• producer_license_pressure
• alibi_scope_integrity
• archive_admissibility
• voice_custody_legitimacy
• memorial_claim_trust
• sponsor_stop_loss_pressure
• fan_oxygen_resentment
• inspection_heat
• public_receipt_legitimacy
• public_receipt_distrust
• edit_debt
• broadcast_reality_drift
• hostile_intent_pressure
• future_route_acceptance
• recovery_only_window

Integration notes

• With 未采纳报价回执线, the chosen alibi must not erase why declined offers were rejected.
• With 播出资产来源后生线, a derivative copy can carry different reasons for different readers.
• With 跨台前例召回线, an alibi may later become a precedent only if its reader scope and harmed-reader warning survive.
• With 压力认领人转化链, a hostile narrator can be converted before the hostile alibi hardens.
• With Memorial Rights Contempt Storyline, memorial respect cannot be cited as clean permission if the harmed mourner or voice reader is hidden.
• With Iris Vale 纪念声权验讫线, a probate reason can become archive-only, voice-only, witness-backed, hostile, or recovery-only.
• With 公开回顾捕获线, a recap statement can become an alibi only if its source scar, proof, and reader scope are preserved.

Replay/session evidence shape

storyline_id: storyteller.storyline.producer_alibi_recall.v1
session_id: lens-producer-alibi-recall-v1-<timestamp>
seed: <deterministic-seed>
entry_state:
  trigger_kind: state_pressure
  source_decision_present: true
  source_decision_needed_reason: true
  source_branch_or_route_effect_visible: true
  alibi_present_or_required_absence_recorded: true
  relying_reader_present: true
  harmed_or_excluded_reader_present_or_explicit_absence: true
  proof_anchor_or_explicit_absence_visible: true
  no_fixed_turn_trigger: true
source_decision:
  source_session_id: <session or explicit_absence>
  source_surface: <surface>
  source_branch_id: <branch>
  chosen_action: <action>
  immediate_relief: <relief>
  immediate_cost: <cost>
alibi_row:
  card: storyteller.card.producer_alibi_ledger.v1
  alibi_id: <stable id>
  alibi_kind: <kind>
  stated_by: <actor>
  wording_state: <state>
  proof_anchor_or_absence: <proof or explicit_absence>
  relying_reader: <reader>
  harmed_or_excluded_reader: <reader or explicit_absence>
  scope_boundary: <scope>
offered:
  rite: storyteller.rite.alibi_scope_hearing.v1
branch_result:
  selected_posture: accept_narrow_alibi | publish_witness_backing | amend_archive_reason | split_public_internal | retract_and_pay | default_hostile_intent
  alibi_state_after: <state>
  relying_reader_state_after: <state>
  harmed_reader_state_after: <state or explicit_absence>
  future_route_effect: <effect>
  emitted_event: storyteller.event.hostile_intent_default.v1 | none
  counter_deltas:
    relief: []
    cost: []
    future: []
assertions:
  - source_decision_and_reason_are_visible
  - proof_anchor_or_absence_visible
  - relying_reader_and_harmed_reader_visible_or_absent
  - alibi_scope_boundary_visible
  - branch_results_diverge_by_reader_scope_and_future_effect
  - hostile_intent_default_is_durable
  - no_universal_clean_alibi
  - no_fixed_turn_day_week_raw_count_dashboard_or_lens_health_trigger

Missability and recovery

This storyline is missed when a future reader can cite an earlier producer reason without a ledger, scope boundary, proof anchor or explicit absence, harmed-reader row, and future route mutation.

Recovery is allowed only with visible cost:

• late witness backing;
• archive amendment;
• public addendum;
• lawful or voice-consent bridge;
• memorial claimant payment;
• sponsor carve-out;
• edit checksum correction;
• retraction and confession;
• route quarantine and recovery-only path.

Non-goals

• Not filler lore.
• Not a morality meter.
• Not a PR dialogue system.
• Not a fixed-turn callback.
• Not a raw statement-count target.
• Not a dashboard or governance page.
• Not a replacement for local custody, provenance, precedent, declined-offer, or claimant systems.
• Not valid if an alibi can become clean universal permission for every later reader.