Ruling Attachment Compliance Hearing / 裁定附条件履行听证

This rite asks the producer to make an already-valid ruling usable by satisfying, narrowing, contesting, quarantining, or breaching its attached conditions.

The rite starts from 裁定附条件账本. It is not a new court case. It is the operational hearing where the player proves that the served order can actually be used in a future route.

Entry condition

entry_condition:
  ledger: storyteller.card.ruling_attachment_ledger.v1
  live_attachment_rows_min: 2
  at_least_one_row_unserved_or_contested: true
  future_route_reads_attachment_state: true
  no_fixed_turn_trigger: true

Required assignments

assignments:
  ledger: storyteller.card.ruling_attachment_ledger.v1
  selected_attachment_rows:
    - <row id>
  intended_future_route: <route / rite / event / explicit future use>
  response: serve_conditions | publish_notice | patch_channel | sponsor_carveout | contest_attachment | quarantine_use | breach_or_default
  handler_or_absence: <handler / monitor / explicit_absence>
  proof_bridge_or_absence: <proof / receipt / checksum / seal / explicit_absence>
  excluded_party_or_absence: <party / explicit_absence>
  cost_or_scar: <cost / scar>
  unselected_attachment_effect: <effect>

The rite fails design if a famous handler can satisfy every attachment without proof, cost, exclusion, monitor, or future route restriction.

Branches

Branch A — Serve conditions

Assign a credible handler, notice carrier, archive seal, public receipt, proof bridge, or monitor to satisfy the selected row.

Expected outcome:

• selected attachment becomes attachment_served or attachment_recovered_with_scar;
• intended future route accepts the ruling;
• cost rises through inspection heat, public exposure, archive debt, handler burden, route asset pressure, or sponsor retaliation;
• at least one unselected attachment remains live or becomes harder.

Branch B — Publish notice

Assign Yu Lan, fan ledger, public receipt, pirate relay, witness chain, or public anchor.

Expected outcome:

• public acceptance or public receipt legitimacy improves;
• lawful acceptance may remain blocked or costlier;
• sponsor pressure, inspection heat, pirate exposure, artist exposure, or fan oxygen liability rises.

Branch C — Patch channel

Assign Baiya, editor checksum, black-box copy, redaction, continuity patch, or archive copy split.

Expected outcome:

• broadcast continuity route improves;
• raw-proof, public, or lawful route acceptance narrows;
• edit debt, source ambiguity, archive debt, or public distrust rises.

Branch D — Sponsor carve-out

Assign Shen Luo, sponsor package, stop-loss settlement, naming-right carve-out, or manager bridge.

Expected outcome:

• immediate sponsor or schedule pressure decreases;
• selected attachment becomes attachment_sponsor_gated or managed_partial;
• public, artist, fan, or archive route later requires conversion or pays capture cost.

Branch E — Contest attachment

Assign counterproof, audit challenge, fan witness, artist boundary, unedited source, or checksum dispute.

Expected outcome:

• false satisfaction, duplicate notice, or wrong monitor is challenged;
• attachment becomes attachment_contested or split_satisfaction;
• route can proceed only through collision, conversion, or quarantine.

Branch F — Quarantine use

Refuse immediate use because every available proof bridge would create false compliance.

Expected outcome:

• breach risk falls;
• future route is delayed, narrowed, recovery-only, or substitute-dependent;
• schedule, sponsor, fan, archive, or audience pressure rises.

Branch G — Breach or default

Use the ruling while one or more required attachments are absent, mismatched, hidden, or satisfied by an incompatible channel.

Expected outcome:

• attachment becomes attachment_breached, public_lawful_mismatch, editor_raw_proof_mismatch, sponsor_public_mismatch, or equivalent;
• breach event fires or is armed;
• a future route becomes blocked, costlier, captured, hostile, channel-limited, or recovery-only.

Resolution contract

Each resolved branch must mutate at least three surfaces:

required_deltas:
  relief: attachment_compliance | lawful_acceptance | public_acceptance | future_route_acceptance
  cost: inspection_heat | archive_debt | edit_debt | contract_capture | public_receipt_distrust | route_asset_pressure | handler_burden
  future_effect: accepted | accepted_with_cost | narrowed | blocked | channel_limited | recovery_only | breach_armed

Non-goals

• Not a generic approval button.
• Not a free universal ruling refresh.
• Not a turn-count timer.
• Not valid if served, contested, quarantined, and breached attachments all lead to the same route acceptance.