Ruling Attachment Compliance / 裁定附条件履行机制

Ruling Attachment Compliance makes a served ruling playable after the mandate has been assigned. It answers a different question from mandate scarcity: what conditions must remain true before this ruling can be used as route law?

A ruling can be valid, served, and still unsafe to reuse if its attached notice, remedy, exclusion, monitor, proof bridge, or channel limit has not been satisfied. This mechanic makes those conditions stateful and replay-visible.

Design gap filled

The existing mesh can already produce verdicts, custody orders, proof-burden shifts, legality conversions, mandate exhaustion, and route-asset maintenance. The remaining gap is conditional use. A player should not be able to treat served_order as a clean universal key when the order only works if attached obligations are honored.

This mechanic sits between:

• 执行授权枯竭线, which allocates finite mandate across multiple live rows;
• 路线资产维护分诊线, which keeps prior route assets fresh or scars them;
• 播出合法性转轨线, which prevents a proof from crossing channels without conversion.

State-triggered entry

Open this mechanic when all are true:

entry_state:
  source_ruling_state: served | mandate_assigned | complied_partial | settlement_active | legality_converted | proof_burden_shifted | custody_order_live
  attachment_rows_min: 2
  attachment_pressure_present: true
  future_route_reads_attachment_state: true
  player_can_assign_compliance_response: true
  no_fixed_turn_trigger: true

Never open from fixed numbered turn, arbitrary day interval, chapter quota, raw asset count, or dashboard/lens health.

Attachment families

Attachment	What it tests	If satisfied	If breached
notice	Was the affected party, public, artist, witness, archive, or sponsor informed?	Route accepts with exposure or trust cost.	Late notice, distrust, refusal, or public breach.
remedy	Was refund, oxygen relief, payroll, apology, edit correction, or clarification delivered?	Relief becomes credible with cost.	Hostility, fan debt, payroll leak, or recovery-only.
exclusion	Was a barred claimant or channel kept out?	Capture risk decreases.	False owner, contract capture, edit capture, or breach.
monitor	Is a watcher, carrier, seal, checksum, or public witness present?	Compliance becomes traceable.	Counterfeit compliance or contradiction pending.
channel_limit	Is the ruling used only in its valid channel?	Route accepts within limit.	Public/lawful/editor/sponsor mismatch.
proof_bridge	Does the order have proof strong enough for the intended route?	Future route accepts with stated bridge.	Route is blocked, costlier, or recovery-only.
route_asset_protection	Is the person/copy/carrier/follower protected before reuse?	Asset remains usable with cost.	Asset becomes exposed, hostile, captured, or false-fresh.

Core state machine

State	Meaning	Consequence
attachment_unserved	Required condition exists but lacks proof/carrier.	Future route blocks, taxes, or arms breach.
attachment_served	Condition is credibly satisfied.	Route can accept the ruling, never for free.
attachment_public_only	Public proof exists but lawful proof is missing.	Public route works; formal route needs conversion.
attachment_lawful_only	Formal seal exists but public/artist condition is absent.	Formal route works; public/artist route gains distrust.
attachment_editor_only	Continuity patch exists without raw proof/public bridge.	Broadcast route works; archive/raw proof narrows.
attachment_sponsor_gated	Sponsor package satisfies the condition privately.	Immediate pressure drops; future route pays capture/gate cost.
attachment_contested	Incompatible parties claim the condition is satisfied.	Collision, quarantine, or conversion required.
attachment_breached	The ruling was used while condition was absent or mismatched.	Breach event mutates future route acceptance.
attachment_recovered_with_scar	Later proof restores limited legitimacy.	Route reopens with named scar or surcharge.

Branch contract

裁定附条件履行听证 must offer or explicitly block at least four branch families:

1. serve conditions;
2. publish notice;
3. patch channel;
4. sponsor carve-out;
5. contest attachment;
6. quarantine use;
7. breach/default.

Each branch must produce different attachment state, cost, and future route effect.

Future-route acceptance rule

A future route must read the attachment state before accepting the ruling.

future_route_acceptance_check:
  source_ruling: <ruling>
  required_attachment_states: []
  accepted_states: []
  rejected_or_costlier_states: []
  required_conversion_or_absence: <conversion / explicit_absence>
  route_effect_after_branch: accepted | accepted_with_cost | narrowed | blocked | channel_limited | contradiction_pending | recovery_only

The mechanic fails if attachment_served, attachment_unserved, attachment_contested, attachment_sponsor_gated, and attachment_breached all unlock the same future route.

Default and breach

裁定附条件破口 fires or arms when:

• a ruling is reused while a row is unserved;
• a public proof is treated as lawful service;
• a lawful seal ignores public/artist notice;
• an editor patch is treated as raw proof;
• sponsor carve-out is treated as public legitimacy;
• a monitor is absent;
• a required exclusion is violated;
• remedy is promised but not delivered;
• a route asset is used without its protection attachment.

Counter contract

Every branch resolution must mutate at least three surfaces:

required_delta_families:
  compliance_relief:
    - attachment_compliance
    - lawful_acceptance
    - public_acceptance
    - future_route_acceptance
  cost_or_scar:
    - inspection_heat
    - archive_debt
    - edit_debt
    - contract_capture
    - public_receipt_distrust
    - route_asset_pressure
    - handler_burden
  future_state:
    - route_accepted_with_cost
    - route_narrowed
    - route_blocked
    - channel_limited
    - contradiction_pending
    - recovery_only

Replay evidence shape

mechanic: storyteller.mechanic.ruling_attachment_compliance.v1
session_id: lens-ruling-attachment-compliance-v1-<timestamp>
seed: <deterministic-seed>
entry_state:
  trigger_kind: state_pressure
  source_ruling_state: served | mandate_assigned | complied_partial | settlement_active | legality_converted | proof_burden_shifted | custody_order_live
  attachment_rows_min: 2
  attachment_pressure_present: true
  future_route_reads_attachment_state: true
  no_fixed_turn_trigger: true
ledger:
  card: storyteller.card.ruling_attachment_ledger.v1
  rows:
    - row_id: <row>
      attachment_kind: <kind>
      attachment_state_before: <state>
      obligated_party: <party>
      carrier_or_monitor: <asset or explicit_absence>
      breach_if_absent: <state>
rite:
  id: storyteller.rite.ruling_attachment_compliance_hearing.v1
  response: serve_conditions | publish_notice | patch_channel | sponsor_carveout | contest_attachment | quarantine_use | breach_or_default
  handler_or_absence: <handler or explicit_absence>
  proof_bridge_or_absence: <proof or explicit_absence>
  cost_or_scar: <cost or scar>
result:
  attachment_state_after: <state>
  unselected_attachment_effect: <effect>
  event_seen_or_armed: storyteller.event.ruling_attachment_breach.v1 | none
  future_route_effect: <effect>
  counter_deltas: {}

Non-goals

• Not a new verdict system.
• Not a generic checklist.
• Not an upkeep tax.
• Not a fixed turn or fixed week trigger.
• Not a replacement for mandate exhaustion, route asset maintenance, claimant conversion, or legality conversion.
• Not valid if attachments have no effect on future route acceptance.