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

Lawful Annex Relay Receipt is the state mechanic that prevents a useful proof row from becoming lawful service by implication.

The mechanic sits between a source proof surface and a lawful reader. It does not decide whether the proof is true, popular, edited, sponsored, or route-valid. It records whether a lawful annex bridge exists, who carries it, what reader scope it covers, and what future state remains after consumption.

State object

lawful_annex_relay:
  relay_id: <stable id>
  source_proof:
    proof_id: <source proof id>
    source_surface: public_receipt | editor_checksum | sponsor_sideletter | archive_stamp | pirate_timestamp | protected_witness | ruling_attachment | route_asset_receipt | private_copy | equivalent
    source_reader_scope: public | editor | sponsor | archive | pirate | private | route_asset | split | explicit_absence | equivalent
    source_scope_limitation: <what this source proof cannot do alone>
  lawful_reader_request:
    reader_id: inspector | lawful_reader | archive_lawful_desk | appeal_body | compliance_table | owed_reader | equivalent
    intended_use: route_unlock | proof_bridge | service | release | appeal | audit | receipt_validation | contradiction_closure | equivalent
    request_reason: <why lawful reader is consuming the row>
  annex_carrier:
    carrier_id: han_yanshuang | baiya | archive_clerk | editor_checksum | public_witness | sponsor_desk | route_asset | proxy_runner | explicit_absence | equivalent
    carrier_state: visible | protected | retained | captured | hostile | unavailable | explicit_absence
  proof_bridge_or_absence:
    bridge_kind: lawful_annex | split_record | archive_escrow | public_addendum | editor_checksum_annex | sponsor_unwind | explicit_absence | equivalent
    bridge_scope: lawful_only | public_addendum_required | split_required | checksum_required | archive_only | sponsor_rejected | recovery_only | explicit_absence
    proof_or_recorded_lack: <proof row or explicit_absence>
  reader_split:
    served_reader: <reader or explicit_absence>
    omitted_or_delayed_reader: <reader or explicit_absence>
    capturing_reader_or_absence: <reader or explicit_absence>
  result:
    selected_posture: 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
    annex_state_after: annex_attached | split_record | archive_escrowed | public_addendum_required | checksum_annexed | sideletter_rejected | false_annex | recovery_only
    future_reader_or_route_effect: lawful_only | public_addendum_required | split_required | checksum_required | archive_escrow_required | sponsor_unwind_required | blocked | hostile | costlier | recovery_only | equivalent

Entry contract

Create or refresh this state only when a future reader needs it:

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
  proof_bridge_or_absence_visible: true
  future_reader_consumes_annex_state: 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 mechanic is invalid if it starts from time passage, a chapter quota, a generic legal warning, a dashboard status, or lens health.

Valid states

State	Meaning	Required future scar
annex_due	lawful reader wants a bridge but no bridge has been selected	lawful reader blocked or costlier
annex_attached	a scoped lawful annex exists	lawful-only or annex-required
split_record	public/editor/sponsor proof and lawful proof remain separate	split-required or two-reader ruling
archive_escrowed	annex is held until release conditions are visible	archive-gated or recovery-only until release
public_addendum_required	source public scope must be clarified before lawful use	public addendum required
checksum_annexed	editor checksum carries a lawful annex bridge	checksum-required or editor-bound lawful use
sideletter_rejected	sponsor sideletter is refused as lawful service	sponsor unwind or sponsor-only scar
false_annex	non-lawful proof was consumed as lawful service	blocked, hostile, costlier, or recovery-only
recovery_only	relay can continue only through scarred repair	recovery-only

Transition rules

• A source proof may be useful without being lawful service.
• A lawful annex may be lawful-only without becoming public truth.
• A public addendum may improve public scope without satisfying every lawful reader.
• An editor checksum may bridge format and custody but not erase source ambiguity.
• A sponsor sideletter cannot become an annex unless the sponsor-only scope and unwind risk remain visible.
• Explicit absence is valid only when the missing annex carrier or bridge is recorded as a future scar.

Counter surfaces

Relief surfaces:

• lawful_reader_legibility
• false_annex_risk
• source_scope_visibility
• archive_trace_preservation
• checksum_legibility
• public_capture_block
• sponsor_sideletter_containment

Cost surfaces:

• inspection_heat
• bureau_favor_debt
• public_addendum_pressure
• archive_debt
• edit_debt
• source_ambiguity
• sponsor_pressure
• handler_burden
• recovery_cost

Future surfaces:

• lawful_only
• public_addendum_required
• split_required
• checksum_required
• archive_escrow_required
• sponsor_unwind_required
• blocked
• hostile
• costlier
• recovery_only

False annex default

Arm False Lawful Annex Default when any of the following happen:

• a public receipt is filed as lawful service without annex bridge;
• an editor checksum is filed as raw lawful proof;
• a sponsor sideletter is treated as lawful annex;
• a pirate timestamp is accepted by a lawful reader without audit scar;
• a lawful reader consumes a source row while source reader scope is hidden;
• annex carrier, bridge, served reader, or omitted reader is absent but not explicitly recorded.

The default must mutate at least three surfaces: false-annex risk, harmed or capturing reader state, and future route effect.