Broadcast Signatory Counterclaim / 播出署名反诉线

Broadcast Signatory Counterclaim is the pressure-system storyline for the moment after broadcast reality turns a person, crowd, body, voice, worker, fan delegate, or route asset into an apparent signer.

The current mesh is strong at consent debt, fan mandate split, reality drift, public contrition, correction inventory, and recovery provenance. The remaining high-leverage gap is narrower and more dangerous: the show can air a surface that later desks treat as a signature even when nobody actually signed.

This storyline asks: when an aired reality manufactures a signer, who can counter-sign before that signature becomes route proof?

Why this expansion matters

Broadcast can become reality in Storyteller. That makes any visible human surface dangerous.

A face in a sponsor bumper can become endorsement. Silence after a public apology can become forgiveness. A crowd overlay can become mandate. A memorial voice can become survivor consent. A worker visible in an archive cut can become custody witness. An editor checksum can become acceptance of final cut.

Adjacent systems cover different questions:

This storyline binds those surfaces around one playable object: an alleged signature that future readers want to reuse.

Bound content pack

  • 播出署名反诉机制 defines entry state, signature state, branch families, counters, and replay evidence.
  • 播出署名反诉案卷 records aired claim, alleged signer, signature source, minimum valid surface, counterclaimant, proof bridge, handler, and future reader effect.
  • 播出署名反诉听证 resolves one row through ratification, counter-signature, split, escrow, public revocation, lawful annulment, sponsor indemnity, or suppression/default.
  • 非自愿播出署名默认 fires or arms when a signature is reused cleanly without counterclaim state.

State-triggered entry

Open this storyline only when all conditions are true:

entry_state:
  trigger_kind: state_pressure
  aired_or_packaged_claim_present: true
  alleged_signatory_visible_or_explicit_absence: true
  signature_source_visible: true
  minimum_surface_for_valid_signature_visible_or_explicit_absence: true
  future_reader_or_route_reuses_signature: true
  counterclaimant_or_explicit_absence_visible: true
  player_can_ratify_counter_sign_split_escrow_revoke_annul_indemnify_or_default: true
  no_fixed_turn_trigger: true
  no_fixed_day_or_week_trigger: true
  no_raw_count_trigger: true
  no_dashboard_or_lens_health_trigger: true

The storyline must fail if entry comes from fixed turn count, day/week interval, chapter quota, raw signature count, raw crisis count, dashboard status, lens health, generic PR crisis, generic law escalation, or a correction slot with no alleged signer.

Storyline spine

Beat 1 — Broadcast creates a signer

A prior aired or packaged surface appears to show consent, endorsement, witness, mandate, forgiveness, survival, or custody acceptance.

The aired surface may be:

  • live broadcast;
  • edited replay;
  • sponsor copy;
  • archive release;
  • public receipt;
  • fan queue overlay;
  • correction slot;
  • black-box excerpt;
  • memorial voice;
  • route asset receipt.

The claim is not automatically false. The problem is that a later desk wants to reuse it as if the signer had accepted it.

Beat 2 — The signature row becomes visible

Create or update 播出署名反诉案卷. The docket must show the aired claim before it shows the counterclaim. It must name the alleged signer or explicit absence, signature source, minimum surface for valid signature, future reader, and reader made vulnerable by the signature.

Beat 3 — Counterclaim hearing forces a management choice

Run 播出署名反诉听证.

The player chooses among:

  • ratify with cost;
  • counter-sign;
  • split signature;
  • escrow signature;
  • public revocation;
  • lawful annulment;
  • sponsor indemnity;
  • suppress or ignore.

Every valid branch must name aired claim, alleged signer or explicit absence, signature source, minimum valid surface, counterclaimant or explicit absence, handler or explicit absence, proof bridge or explicit absence, cost, and future reader effect.

Beat 4 — One reader gets proof; another inherits the scar

No branch produces universal clean acceptance. At least two reader states must diverge:

  • public accepts but lawful reader waits;
  • sponsor accepts but public becomes hostile;
  • archive accepts escrow but route asset remains recovery-only;
  • signatory ratifies but handler burden rises;
  • editor proves a boundary but public distrust rises;
  • fan delegate counter-signs but sponsor stop-loss rises;
  • lawful annulment blocks commercial reuse;
  • suppression creates an involuntary-signatory default.

Beat 5 — Default hardens if clean reuse moves first

If a future reader consumes an alleged signature without the docket and hearing, 非自愿播出署名默认 fires or arms.

Default is not a timeout. It is a durable state showing who filed the clean signature, which signatory was captured or silenced, which reader became vulnerable, and which future route became blocked, hostile, contradiction-pending, reader-limited, or recovery-only.

Branch map

BranchImmediate reliefCost/scarFuture state
Ratify with costaired claim can be reused after valid surfacecompensation, protection, handler burden, sponsor/public pressureaccepted with ratification cost
Counter-signclaim remains usable with boundarysplit message, sponsor heat, archive debt, public confusioncounter-signature required or split-required
Split signatureone reader can proceed while another rejects or waitsroute split, lawful/public/sponsor divergencepublic-only, lawful-only, sponsor-only, or split-required
Escrow signaturesignature held by lawful/archive/protected handlerdelay, inspection heat, bureau debt, sponsor objectionescrow-only or costlier
Public revocationprivate capture blockedsponsor retaliation, crowd churn, witness riskpublic-only, contradiction-pending, or blocked
Lawful annulmentinvalid implied signature narrowedquarantine, lawful cost, sponsor default risklawful-only, blocked, or recovery-only
Sponsor indemnitycommercial route proceeds with named boundarycontract capture, public distrust, unwind risksponsor-only or recovery-only
Suppress or ignoreimmediate clean reuse proceedsinvoluntary signer, hostile witness, reality driftinvoluntary-signatory default, blocked, hostile, contradiction-pending, reader-limited, or recovery-only

Character and desk hooks

  • Shen Luo can negotiate ratification, sponsor indemnity, or protected counter-signature. His route gains value when he protects a signer and becomes more dangerous when he brokers a captured signature.
  • Li Xingtong can be protected from saint-persona endorsement becoming selfhood signature.
  • Mu Ning can have fragile-newcomer silence treated as acceptance unless the player opens a protected counter-signature surface.
  • Editor Han Cutroom Storyline can prove edit boundaries, but checksum cannot replace signer surface.
  • Inspector Rhee Archive Storyline can escrow or annul signatures for lawful readers.
  • Fan delegates, worker witnesses, public delegates, and route assets can carry signature state only if protection, capture risk, or explicit absence is recorded.

Integration examples

The sponsor bumper shows an artist nodding under a lower-third. Later the sponsor cites the clip as proof of endorsement. The docket must show whether the artist ratified, counter-signed, split the commercial signature, escrowed it, revoked publicly, had it annulled, accepted sponsor indemnity, or became involuntary signer.

Fan queue mandate

A fan queue overlay appears during a public apology. Later management files it as crowd forgiveness. The docket must show whether fan mandate hearing or public counter-signature exists before the crowd becomes a clean mandate.

Archive witness signature

A worker appears in an archive release. Later custody cites that image as witness signature. The docket must show protected witness surface, lawful escrow, or counterclaim before the witness becomes clean custody proof.

Memorial voice endorsement

A memorial voice splice is aired as comfort. Later a sponsor package treats it as survivor consent. The docket must show explicit absence, memorial boundary, lawful annulment, or default scar.

Missability and recovery

This storyline is missed when implementation:

  • treats face, voice, silence, queue presence, survival, grief, or edit checksum as automatic signature;
  • hides the alleged signer or explicit absence;
  • records only consent_debt without the aired signature source;
  • records only reality_drift without the signer made vulnerable by the claim;
  • lets sponsor, archive, edit, public, management, producer-license, or broadcast-reality readers accept one signature as universal clean proof;
  • opens from fixed turn, day/week, raw count, dashboard, or lens-health state.

Recovery is allowed only through visible scar:

  • late ratification with higher compensation;
  • protected counter-signature;
  • public revocation bulletin;
  • lawful annex or annulment;
  • fan mandate rehearing;
  • route escrow;
  • sponsor unwind;
  • signature quarantine;
  • harmed-signatory receipt;
  • contradiction-pending route;
  • recovery-only signature.

Replay evidence expectation

storyline_id: storyteller.storyline.broadcast_signatory_counterclaim.v1
session_id: lens-broadcast-signatory-counterclaim-v1-<timestamp>
seed: <deterministic-seed>
entry_state:
  trigger_kind: state_pressure
  aired_or_packaged_claim_present: true
  alleged_signatory_visible_or_explicit_absence: true
  signature_source_visible: true
  minimum_surface_for_valid_signature_visible_or_explicit_absence: true
  future_reader_or_route_reuses_signature: true
  no_fixed_turn_trigger: true
aired_claim:
  aired_claim_id: <stable id>
  aired_surface: <surface>
  route_that_wants_to_reuse_claim: <route or explicit_absence>
signature:
  signatory_kind: <kind>
  signatory_id_or_absence: <id or explicit_absence>
  signature_source: <source>
  signature_status_before: <state>
  minimum_surface_for_valid_signature: <surface or explicit_absence>
  counterclaimant_or_absence: <counterclaimant or explicit_absence>
  desired_reader: <reader>
  reader_made_vulnerable_by_signature: <reader or explicit_absence>
offered:
  card: storyteller.card.broadcast_signatory_counterclaim_docket.v1
  rite: storyteller.rite.broadcast_signatory_counterclaim_hearing.v1
branch_runs:
  valid_branch:
    selected_counterclaim_mode: ratify_with_cost | counter_sign | split_signature | escrow_signature | public_revocation | lawful_annulment | sponsor_indemnity
    handler_or_absence: <handler or explicit_absence>
    proof_bridge_or_absence: <proof or explicit_absence>
    signature_state_after: <state>
    signatory_state_after: <state>
    vulnerable_reader_state_after: <state>
    future_reader_effect: <effect>
    counter_deltas:
      signature: []
      cost: []
      future: []
  default_branch:
    selected_counterclaim_mode: suppress_or_ignore
    event_seen_or_armed: storyteller.event.involuntary_broadcast_signatory_default.v1
    default_actor: <actor>
    harmed_signatory_state_after: <state>
    future_reader_effect: <effect>
assertions:
  entry_is_state_triggered: true
  aired_claim_visible: true
  alleged_signatory_visible_or_explicit_absence: true
  signature_source_visible: true
  minimum_signature_surface_visible_or_explicit_absence: true
  future_reader_consumes_signature_state: true
  branch_outcomes_diverge: true
  universal_clean_signature_blocked: true
  default_is_durable: true
  no_fixed_turn_day_week_raw_count_dashboard_or_lens_health_trigger: true

Non-goals

  • Not a generic consent-debt expansion.
  • Not a correction inventory economy.
  • Not governance.
  • Not a raw count objective.
  • Not a replacement for drift audit, fan mandate, or public contrition.
  • Not valid unless a broadcast-created alleged signature changes future playable acceptance.