Archive Custody

Archive custody is not storage. It is broadcast permission over memory: who may use a dead, missing, retired, deplatformed, or disputed artist’s voice, face, route footage, interview fragments, rehearsal takes, grief objects, and fan-made memorials.

This page converts ChatGPT handle 6835f7d97996 into the active storyteller wiki. It extends broadcast-reality, schedule-contracts, mirror-rights, fan-oxygen, and route-assets-and-custody without advancing the frozen restart source.

Playable rules

• A voice archive can be claimed by a company, estate, fan trust, sponsor, inspector, rebel editor, or the player’s temporary production license.
• Custody only counts when it is visible on-screen as a broadcast, contract, rite, inspection, archive ledger, or black-screen leak.
• A single archive object can split rights: voice_usage_right, memorial_stage_right, training_data_right, fan_liturgy_right, and suppression_right.
• Disputed custody must create playable pressure: assignments, choices, counters, deadlines, failure states, or route assets.
• Private promises do not resolve custody unless recorded into the schedule or replay.

Memorial voice loop

The narrow custody loop introduced here is the memorial-voice-permit: a memorial voice archive enters the schedule, claimants contest it, and the player chooses preserve, license, suppress, recruit, or miss/fail. The loop is proven by Memorial Voice Permit resolves archive custody.

Black-screen outcomes

Archive failures fold into black-screen pressure instead of a generic HP loss:

• black_screen.unlicensed_aftervoice — an archived voice airs without settled custody.
• black_screen.memorial_oxygen_riot — fans expose hidden oxygen/compute cost for a memorial.
• black_screen.false_saint_edit — an editor fabricates a memorial confession.
• black_screen.sponsor_relic_capture — a sponsor gains exclusive custody after an audit is missed.