Ruling Attachment Compliance / 裁定附条件履行线

Ruling Attachment Compliance is a non-character pressure storyline for the moment after a ruling has already become valid, served, mandated, settled, converted, or partially complied with — but before the player can safely reuse that ruling as route law.

The prior victory remains true. The new question is whether its attached conditions are still honored: notice, remedy, exclusion, monitor, channel limit, proof bridge, witness protection, artist boundary, public receipt, sponsor carve-out, editor checksum, or archive seal.

Primary playable question

When a valid ruling carries multiple enforceable attachments, which condition does the producer satisfy, publish, patch, contest, quarantine, or breach — and which future route now accepts, taxes, narrows, or rejects that ruling?

This storyline prevents served_order from becoming a clean universal key. It turns conditional compliance into management/RPG pressure without creating a new court case or an abstract checklist.

Gap diagnosis

The current mesh already has strong surfaces for the stages before and around this problem:

• Post-Ruling Enforcement Week Storyline proves that a verdict becomes operational work after custody decisions.
• 执行授权枯竭线 proves that several valid orders can compete for finite seals, carriers, windows, and authority.
• 归档执行案卷 makes enforcement rows and breach states playable.
• 播出合法性转轨线 prevents proof from crossing public, lawful, editor, sponsor, or pirate channels for free.
• 路线资产维护分诊线 keeps prior assets from remaining permanently fresh.
• 压力认领人转化链 turns default narrators into bounded, hostile, or missed claimant rows.

The remaining gap is the conditional afterlife of a served ruling. Once a row has mandate and survives immediate default, the engine still needs to prove whether the ruling’s attached obligations have been met before a future route can rely on it.

State-triggered entry

Open this storyline when all are true:

1. a ruling, order, settlement, legality conversion, proof-burden shift, custody decision, archive service, public receipt, or enforcement row is already valid or partially complied with;
2. the ruling has at least two attached conditions such as notice, remedy, exclusion, monitor, channel limit, proof bridge, witness protection, artist boundary, public receipt, sponsor carve-out, editor checksum, or archive seal;
3. at least one attachment is unserved, contested, channel-limited, sponsor-gated, monitorless, or breach-risk;
4. at least one future route, rite, event, or asset assignment reads the attachment state before accepting the ruling;
5. the player can answer through a concrete assignment or explicit absence;
6. the result can mutate future route acceptance, route asset state, claimant posture, or recovery cost.

No trigger may depend on fixed turn count, arbitrary day count, chapter quota, content count, or dashboard health.

Content pack

Mechanic

• 裁定附条件履行机制 — defines attachment rows, state machine, branch families, breach rules, and replay evidence.

Card

• 裁定附条件账本 — stores source ruling, attachment kinds, obligated parties, carriers/monitors, satisfaction proof, breach state, and future route acceptance.

Rite

• 裁定附条件履行听证 — assignable rite that serves, publishes, patches, carves out, contests, quarantines, or breaches an attachment.

Event

• 裁定附条件破口 — default/breach event when a ruling is used with unmet, mismatched, hidden, or falsely satisfied attachments.

Primary actors

• Han Yanshuang — can formalize notice, lawful service, exclusion, and monitor presence, raising inspection heat or bureau debt.
• Inspector Rhee Archive — can make compliance admissible, but may freeze a channel or expose archive opacity.
• Yu Lan — can publish notice, fan witness, and public receipt, raising sponsor, lawful, or exposure cost.
• Baiya — can checksum, redact, or patch channel use, raising edit debt and source ambiguity.
• Shen Luo — can negotiate sponsor carve-outs and managed quiet, raising contract capture and public distrust.
• Orion Breath — can fund remedy or privately satisfy a condition, but turns later use into sponsor-gated pressure.

Attachment route states

State	Meaning	Required consequence
attachment_unserved	Condition exists but lacks proof, carrier, or monitor.	Future route blocks, taxes, or arms breach.
attachment_served	Condition is credibly satisfied.	Route accepts with visible cost or exposure.
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 notice is absent.	Formal route works; public/artist route gains distrust or refusal risk.
attachment_editor_only	Continuity patch exists without raw proof or public bridge.	Broadcast route works; archive/raw proof narrows.
attachment_sponsor_gated	Sponsor package satisfies condition privately.	Immediate pressure drops; future route pays capture/gate cost.
attachment_contested	Incompatible parties claim condition is satisfied.	Collision, quarantine, or conversion must resolve before clean use.
attachment_breached	Ruling was used while condition was absent or mismatched.	Breach event mutates future availability.
attachment_recovered_with_scar	Later proof restores partial legitimacy.	Route reopens with named scar, surcharge, or channel limit.

Branch model

Branch A — Serve conditions

The player assigns a credible handler, notice carrier, archive seal, public receipt, monitor, or proof bridge.

Expected outcomes:

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

Branch B — Publish notice

The player assigns Yu Lan, fan oxygen proof, public receipt, pirate relay, witness chain, or public anchor.

Expected outcomes:

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

Branch C — Patch channel

The player assigns Baiya, editor checksum, black-box copy, redaction, continuity patch, or copy split.

Expected outcomes:

• 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

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

Expected outcomes:

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

Branch E — Contest attachment

The player challenges false satisfaction, duplicate notice, wrong monitor, or incompatible channel proof.

Expected outcomes:

• attachment becomes attachment_contested or split_satisfaction;
• false owner, counterfeit compliance, or sponsor/editor capture pressure drops;
• route can proceed only through collision, conversion, quarantine, or recovery.

Branch F — Quarantine use

The player refuses immediate use because every available bridge would create false compliance.

Expected outcomes:

• breach risk, contradiction risk, or artist/witness harm decreases;
• future route is delayed, narrowed, recovery-only, or substitute-dependent;
• schedule, sponsor, fan, archive, or audience pressure rises.

Branch G — Breach or default

The player uses the ruling while one or more attachments are absent, mismatched, hidden, unmonitored, or satisfied through an incompatible channel.

Expected outcomes:

• 裁定附条件破口 fires or arms;
• attachment becomes attachment_breached, public_lawful_mismatch, editor_raw_proof_mismatch, sponsor_public_mismatch, monitor_absent, or equivalent;
• a future route becomes blocked, costlier, captured, hostile, channel-limited, contradiction-pending, or recovery-only.

Counter contract

Every branch must change at least three counters or durable states. One must be relief, one must be cost, and one must change future route acceptance.

Primary surfaces:

• attachment_compliance
• attachment_breach_risk
• lawful_acceptance
• public_acceptance
• artist_boundary_respect
• archive_signature_legitimacy
• editor_checksum_legitimacy
• sponsor_gate_pressure
• inspection_heat
• archive_debt
• edit_debt
• contract_capture
• public_receipt_distrust
• handler_burden
• route_asset_pressure
• future_route_acceptance
• future_recovery_cost

Replay/session evidence shape

storyline: storyteller.storyline.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>
      source_ruling: <source>
      attachment_kind: <kind>
      attachment_state_before: <state>
      obligated_party: <party>
      carrier_or_monitor: <asset or explicit_absence>
      breach_if_absent: <state>
      future_route_accepts_when: []
      future_route_rejects_or_taxes_when: []
rite:
  id: storyteller.rite.ruling_attachment_compliance_hearing.v1
  selected_attachment_rows: []
  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>
  excluded_party_or_absence: <party 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: accepted | accepted_with_cost | narrowed | blocked | channel_limited | contradiction_pending | recovery_only
  counter_deltas: {}

Missability and recovery

This storyline is missable when the game lets a served ruling skip its attached conditions, hides the attachment ledger, treats public/lawful/editor/sponsor channels as interchangeable, or fails to change future route acceptance after breach.

Recovery is allowed only with named scar or bridge:

• late notice with public distrust or sponsor retaliation;
• remedy paid with route asset pressure or fan oxygen debt;
• exclusion restored through quarantine;
• monitor appointed with inspection heat;
• channel converted with legality cost;
• proof bridge rebuilt with archive or edit debt;
• route asset protected after breach with recovery-only state.

Non-goals

• Not a new verdict.
• Not a legal checklist disconnected from play.
• Not fixed-turn or fixed-week content.
• Not raw count satisfaction.
• Not a dashboard governance page.
• Not a replacement for mandate exhaustion, claimant conversion, route asset maintenance, archive enforcement, or broadcast legality conversion.
• Not valid if attachment states do not affect future route acceptance.