Call-Sheet Watermark Afteruse Mechanics

The mechanic treats a production watermark as scoped evidence, not permission. Entry is trigger_kind: state_pressure: a later reader or route attempts to consume a prior call-sheet watermark state.

Required row fields:

• source_call_sheet_watermark_receipt_visible: true
• watermark_holder_or_explicit_absence_visible: true
• performer_or_crew_claimant_visible: true
• requested_afteruse_visible: true
• harmed_or_displaced_party_visible: true
• proof_bridge_or_explicit_absence_visible: true
• selected_afteruse_branch_visible: true
• future_reader_consumes_watermark_state: true
• no_watermark_as_universal_schedule_consent: true

Playable outputs must include at least one relief, one cost, and one future route effect. The false default is durable mutation: a copied roster is treated as consent, but the result is recovery_only, not clean permission.