Lawful Annex Relay Receipt / 法务附件传达回执线

Lawful Annex Relay Receipt is the pressure-system storyline for the moment an existing proof row has enough public, editor, sponsor, archive, or private force to matter, but a lawful reader tries to consume it without a scoped annex bridge.

The corpus already has many outcomes that say lawful_annex_required, lawful_only, public_addendum_required, or public notice is not lawful proof. This storyline owns the missing middle step: the visible handoff from source proof to lawful reader.

Gap diagnosis

Without this packet, implementation can let a public receipt, editor checksum, sponsor sideletter, pirate timestamp, archive note, or witness countercopy become lawful service by implication. That collapses reader scope. It also hides the carrier or explicit absence that should explain why the lawful reader can consume the row.

The pack is deliberately narrow:

• Broadcast Legality Conversion decides whether a route asset can change channel class. This storyline records the annex relay after a source proof already exists.
• Reader Rebuttal Notice decides whether an affected party can answer a cited row. This storyline records lawful-reader attachment, not rebuttal rights.
• Stay Notice Relay handles appeal-stay scope. This storyline handles any proof row that needs a lawful annex bridge.
• Ruling Attachment Compliance handles attachment conditions. This storyline makes the relay receipt and future consumption visible.

Primary playable question

When a lawful reader wants to use an existing public, editor, sponsor, archive, private, or route-asset proof row, does the producer attach a lawful annex, split public and lawful records, escrow the annex, return for public addendum, file an editor checksum annex, reject a sponsor sideletter, or let a false lawful annex default harden?

Every branch must name:

• source proof;
• source reader scope;
• lawful reader request;
• annex carrier, or explicit absence;
• proof bridge or absence;
• served reader;
• omitted or delayed reader;
• selected relay posture;
• annex state after;
• future reader or route effect.

State-triggered entry

Open this storyline only from live reader-scope pressure:

entry_state_required:
  trigger_kind: state_pressure
  source_public_or_editor_or_sponsor_proof_present: true
  lawful_reader_requests_annex: true
  source_reader_scope_visible: true
  annex_carrier_or_explicit_absence_visible: true
  source_proof_has_future_use: true
  future_reader_consumes_annex_state: true
  player_can_attach_split_escrow_return_checksum_reject_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

Valid source proofs include public receipts, fan queue receipts, editor checksums, sponsor countercopies, archive stamps, pirate timestamps, protected witness rows, ruling attachments, route asset transfer receipts, rebuttal notice rows, and custody-proof chain receipts.

Bound content pack

• Lawful Annex Relay Receipt defines annex-relay states, carrier rules, false-annex defaults, and future reader effects.
• Lawful Annex Relay Ledger records source proof, source reader scope, lawful reader request, annex carrier, proof bridge or absence, annex state after, and future effect.
• Lawful Annex Relay Review resolves attach, split, escrow, return, checksum, sponsor rejection, and default postures.
• False Lawful Annex Default fires or arms when a non-lawful proof row is consumed as lawful service without an annex bridge.

Storyline spine

Beat 1 - A source proof row hits a lawful reader

A public, editor, sponsor, archive, private, or route-asset row is cited by a lawful reader. The row may be true and useful, but its source reader scope is not enough.

Examples:

• a public receipt blocks private capture but cannot satisfy a lawful table alone;
• an editor checksum proves continuity but not service;
• a sponsor sideletter protects a slot but not public or lawful acceptance;
• an archive stamp preserves custody but needs a reader-facing annex;
• a pirate timestamp keeps proof alive but raises admissibility heat.

Beat 2 - Ledger separates proof from bridge

Create or refresh Lawful Annex Relay Ledger. The ledger must keep source proof, source reader scope, lawful reader request, annex carrier, proof bridge or absence, and future effect separate.

It fails if it stores only proof_exists, lawful_ok, receipt_served, annex_sent, or legal_reviewed.

Beat 3 - Relay review chooses posture

Run Lawful Annex Relay Review before the lawful reader consumes the row.

Valid postures:

• attach_lawful_annex
• split_public_and_lawful_record
• archive_escrow_annex
• return_for_public_addendum
• editor_checksum_annex
• sponsor_sideletter_reject
• false_lawful_annex_default

Beat 4 - Future reader consumes scarred state

The result must change a later route, proof, receipt, release, appeal, audit, or broadcast-reality reader. Outcomes can become lawful-only, public-addendum-required, split-required, checksum-required, sponsor-rejected, archive-escrowed, blocked, costlier, hostile, or recovery-only.

No branch may make the source proof clean for all public, lawful, sponsor, editor, archive, fan, pirate, route-asset, and management readers at once.

Branch matrix

Branch	Relief	Cost/scar	Future state
Attach lawful annex	lawful reader can consume the row	inspection heat, bureau debt, public delay	lawful-only or annex-required
Split public and lawful record	public proof and lawful proof both survive	source ambiguity, handler burden	split-required or two-reader ruling
Archive escrow annex	false legal service is blocked	archive debt, release delay	archive-gated or recovery-only until release
Return for public addendum	public scope is clarified before lawful use	public contradiction, sponsor pressure	public addendum required before lawful use
Editor checksum annex	edited proof gains a lawful checksum bridge	edit debt, source ambiguity, audit risk	checksum-required or editor-bound lawful use
Sponsor sideletter reject	sponsor-only sideletter cannot impersonate service	sponsor retaliation, slot pressure	sponsor-only rejected or unwind required
False lawful annex default	short pressure may drop	false service, harmed reader, future route scar	blocked, hostile, costlier, recovery-only

Counter contract

Every resolved branch must mutate at least one relief surface, one cost surface, and one future reader or route surface.

Accepted relief surfaces include lawful_reader_legibility_up, false_annex_risk_down, source_scope_visible, public_capture_blocked, archive_trace_preserved, checksum_legibility_up, and sponsor_sideletter_contained.

Accepted cost surfaces include inspection_heat_up, bureau_favor_debt_up, public_addendum_pressure_up, archive_debt_up, edit_debt_up, source_ambiguity_up, sponsor_pressure_up, handler_burden_up, and recovery_cost_up.

Accepted future states include lawful_only, public_addendum_required, split_required, checksum_required, archive_escrow_required, sponsor_unwind_required, blocked, hostile, costlier, and recovery_only.

Missability and recovery

This storyline is missed when a source proof row is cited by a lawful reader without a ledger, annex carrier, bridge or absence, served and omitted readers, and future state.

Missed states include:

• false_lawful_annex_default;
• public_notice_as_lawful_service;
• editor_checksum_as_raw_lawful_proof;
• sponsor_sideletter_as_annex;
• annex_carrier_hidden;
• source_scope_hidden_or_mismatched;
• future_reader_consumed_without_annex_state;
• recovery_only_annex_route.

Recovery is allowed only with visible scar: late lawful annex, split record, public addendum, archive escrow, checksum correction, sponsor unwind, lawful-only acknowledgement, public-only acknowledgement, blocked route, costlier route, or recovery-only route.

Replay evidence expectation

storyline_id: storyteller.storyline.lawful_annex_relay_receipt.v1
session_id: lens-lawful-annex-relay-receipt-v1-<timestamp>
seed: <deterministic-seed>
entry_state_required:
  trigger_kind: state_pressure
  source_public_or_editor_or_sponsor_proof_present: true
  lawful_reader_requests_annex: true
  source_reader_scope_visible: true
  annex_carrier_or_explicit_absence_visible: true
  future_reader_consumes_annex_state: true
  no_fixed_turn_trigger: true
source:
  source_proof: <proof row id>
  source_reader_scope: public | editor | sponsor | archive | private | route_asset | equivalent
  lawful_reader_request: <reader and intended use>
offered:
  card: storyteller.card.lawful_annex_relay_ledger.v1
  rite: storyteller.rite.lawful_annex_relay_review.v1
branch_runs:
  valid_branch:
    selected_posture: attach_lawful_annex | split_public_and_lawful_record | archive_escrow_annex | return_for_public_addendum | editor_checksum_annex | sponsor_sideletter_reject
    annex_carrier: <carrier or explicit_absence>
    proof_bridge_or_absence: <bridge or explicit_absence>
    annex_state_after: <state>
    future_reader_or_route_effect: <effect>
  default_branch:
    event: storyteller.event.false_lawful_annex_default.v1

Non-goals

• Not a global legality conversion layer.
• Not a replacement for affected-party rebuttal.
• Not an appeal-stay relay.
• Not a way to make public, editor, or sponsor proof universal.
• Not valid from fixed turn, fixed day, raw count, dashboard state, or lens health.