Memorial Voice Revocation Notice

A memorial voice probate row can be narrowed later, but the withdrawal must be playable as a notice surface rather than an invisible cleanup. The revocation is triggered by state pressure: a scoped probate row exists, a later consumer tries to keep using it, and at least one affected reader would lose access or inherit a surcharge.

The player is choosing who receives the notice first: archive clerk, fan public, sponsor runner, cutroom editor, pirate relay, or route-asset custodian. Each route preserves the original source row while changing future use.

Playable pressure

• A source probate row remains visible and cannot be deleted by revocation.
• The withdrawn scope names a reader, claimed use, proof carrier, notice carrier, and effective boundary.
• Late notice can create breach debt, fan oxygen loss, sponsor refund pressure, cutroom delay, or route asset lock.
• Clean notice can reduce false-clean voice reuse but raises grief, delay, or contract liability.

Evidence shape

The lens is evidenced by memorial-voice-revocation-ledger, memorial-voice-revocation-hearing, and memorial-voice-revocation-default. Replay evidence should use a lens-scoped durable session and expose the selected notice branch plus counter/flag movement.