连续性版本争议

Design intent

Turn continuity from background lore into a route choice. The question is not “what is true?” but “which version receives legal identity?”

Scope

Affected cards: 第七穹顶连续性案卷, 安全连续性版本, 连续性租赁许可, 灾难命名权合约, 双层归档副本. Affected counters: ContinuityAuthority, ArchiveAuthority, ContinuityInstability, SponsorPressure, InspectorApproval.

Oracle

When 第七穹顶连续性案卷 and 安全连续性版本 are both present, a 版本仲裁听证 must appear with at least three materially different results among corporate version, archive version, split version, disaster-name custody, and suppress. Each result must have visible state or counter movement.

Progress metric

ResolvedContinuityDisputes >= 1 with replay-visible required cards, offered choices, chosen branch, and changed counters.

Evidence

• Code sibling: continuity-version-dispute.lens.ts
• Replay fixture: lens/replays/continuity-version-dispute.replay.json
• Evaluator: scripts/evaluate_lenses.mjs