Ruling Attachment Ledger / 裁定附条件账本
Ruling Attachment Ledger is a board card for already-valid rulings that are not yet cleanly usable because the ruling carries enforceable conditions.
It records the attachments that make a served order legitimate: notice, remedy, exclusion, monitor, channel limit, proof bridge, witness protection, artist boundary, public receipt, sponsor carve-out, editor checksum, or archive seal. A ruling without its attachments may still exist, but using it as a universal key creates breach pressure.
When this card appears
Offer this card from state when all are true:
entry_state:
ruling_or_order_state: served | mandate_assigned | complied_partial | settlement_active | legality_converted | proof_burden_shifted | custody_order_live
attachments_min: 2
future_route_reads_attachment_state: true
no_fixed_turn_trigger: trueDo not offer this card because a numbered turn, arbitrary day count, chapter quota, or lens/dashboard status has been reached.
Required row shape
attachment_row:
row_id: <stable id>
source_ruling: <source order / event / storyline>
source_relief_kept_true: []
attachment_kind: notice | remedy | exclusion | monitor | channel_limit | proof_bridge | witness_protection | artist_boundary | public_receipt | sponsor_carveout | editor_checksum | archive_seal
obligated_party: inspector | archive | sponsor | editor | public_fan | artist | witness | manager | pirate | route_asset | explicit_absence
carrier_or_monitor: <card / character / route asset / explicit_absence>
satisfied_by: <assignment / proof / explicit_absence>
breach_if_absent: <breach state>
future_route_accepts_when: []
future_route_rejects_or_taxes_when: []Attachment states
| State | Meaning | Required consequence |
|---|---|---|
attachment_unserved | The condition exists but no credible party has carried it. | Future use is blocked, taxed, or breach-armed. |
attachment_served | A party has satisfied the condition with proof. | One route accepts the ruling, with a visible cost or exposure. |
attachment_public_only | Public receipt exists but lawful proof is missing. | Public route can proceed; formal route needs conversion. |
attachment_lawful_only | Formal seal exists but public/artist notice is absent. | Formal route can proceed; public/artist route gains distrust or refusal risk. |
attachment_editor_only | Continuity patch exists without raw proof or public bridge. | Broadcast continuity route improves; archive/raw-proof route narrows. |
attachment_sponsor_gated | Sponsor paid or packaged the condition. | Immediate pressure drops; future use requires sponsor gate or capture cost. |
attachment_contested | Two parties claim incompatible satisfaction. | Collision, conversion, or quarantine must resolve before clean use. |
attachment_breached | The ruling was used while the condition was unmet 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. |
Playable use
This card is not an inventory of clauses. Every live row must create at least one assignment question:
- who carries notice;
- who proves remedy;
- who must be excluded from use;
- who monitors the order;
- which channel accepts the copy;
- whose proof bridge is missing;
- which future route rejects a mismatched attachment.
Counter surfaces
Relevant branch deltas include:
attachment_complianceattachment_breach_risklawful_acceptancepublic_acceptanceartist_boundary_respectarchive_signature_legitimacyeditor_checksum_legitimacysponsor_gate_pressureinspection_heatpublic_receipt_distrustcontract_captureroute_asset_pressurefuture_route_acceptancefuture_recovery_cost
Non-goals
- Not a new verdict.
- Not a generic legal checklist.
- Not a fixed turn phase.
- Not a free cleanup for enforcement debt.
- Not valid if every served order can be reused without checking its attached conditions.