Archive Claim Table Must Produce Playable Custody Branches

Design intent

Ensure Archive Claim Table behaves as a playable rite hub, not as a lore page. A custody dispute must surface multiple local actions, competing factions, evidence objects, counter changes, and event logs.

Scope

This lens is backed by ChatGPT handle d462fbcf0144 and the active storyteller source only. It binds archive custody, current-hand evidence cards, faction contestants, refusal/exception rules, double-copy state, and pirate-loop containment.

Oracle

Within 30 turns, a relevant hand containing archive-table or evidence cards must offer at least three custody actions, register claims with claimant/evidence/contested fields, respect artist refusal unless legal exceptions are present, create public/sealed double archive versions, and make pirate-loop containment costly rather than free value.

Progress metric

The lens is satisfied when the replay fixture and evaluator prove custody_playability_score >= 7, restart remains frozen, and dashboard-facing custody rows expose object, claimant, contestedBy, and version state.

Evidence

• Code sibling: archive-claim-table.lens.ts
• Replay fixture: lens/replays/archive-custody-playable-hooks.replay.json
• Evaluator: scripts/evaluate_lenses.mjs