This atlas provides V8's cross-cutting visual models for solve-first case generation, proof, durable case data, lifecycle, subsystem composition, ownership, the player journey, and release evidence. Focused pages, typed artifacts, solver/compiler output, tests, independent quality evidence, and current operations remain authoritative.
Solve-first generation landscape#
This picture is wider than it can be shown here. Move across it, or read it as text.
Drawn from its Mermaid source.
As text
Parts: - Case brief world canon and constraints - Clew proposes symbolic skeleton - Minos proves satisfiable unique and complete - Knox and Van Dine fair-play checks - Palimpsest binds canon continuity - Anansesem realizes prose and dialogue - Loom realizes art audio and scene assets - Ori living suspects - Daedalus compiles V5 case bundle - Theseus automated play and quality evaluation - Independent eight-gate ReleaseDecision - Oracle stages and directs eligible cases - Player investigation - Proof artifacts (data) - Versioned bundle provenance and replay (data) Connections: - Case brief world canon and constraints to Clew proposes symbolic skeleton - Clew proposes symbolic skeleton to Minos proves satisfiable unique and complete - Minos proves satisfiable unique and complete to Knox and Van Dine fair-play checks - Knox and Van Dine fair-play checks to Palimpsest binds canon continuity - Palimpsest binds canon continuity to Anansesem realizes prose and dialogue - Palimpsest binds canon continuity to Loom realizes art audio and scene assets - Anansesem realizes prose and dialogue to Ori living suspects - Loom realizes art audio and scene assets to Ori living suspects - Ori living suspects to Daedalus compiles V5 case bundle - Daedalus compiles V5 case bundle to Theseus automated play and quality evaluation - Theseus automated play and quality evaluation to Independent eight-gate ReleaseDecision - Independent eight-gate ReleaseDecision to Oracle stages and directs eligible cases - Oracle stages and directs eligible cases to Player investigation - Minos proves satisfiable unique and complete to Proof artifacts - Daedalus compiles V5 case bundle to Versioned bundle provenance and replay - Independent eight-gate ReleaseDecision to Versioned bundle provenance and replay
Show source
flowchart LR
Brief[Case brief world canon and constraints] --> Clew[Clew proposes symbolic skeleton]
Clew --> Minos[Minos proves satisfiable unique and complete]
Minos --> Fair[Knox and Van Dine fair-play checks]
Fair --> Palimpsest[Palimpsest binds canon continuity]
Palimpsest --> Anansesem[Anansesem realizes prose and dialogue]
Palimpsest --> Loom[Loom realizes art audio and scene assets]
Anansesem --> Ori[Ori living suspects]
Loom --> Ori
Ori --> Daedalus[Daedalus compiles V5 case bundle]
Daedalus --> Theseus[Theseus automated play and quality evaluation]
Theseus --> Gates[Independent eight-gate ReleaseDecision]
Gates --> Oracle[Oracle stages and directs eligible cases]
Oracle --> Player[Player investigation]
Minos --> Evidence[(Proof artifacts)]
Daedalus --> Evidence2[(Versioned bundle provenance and replay)]
Gates --> Evidence2
The symbolic skeleton is established before expensive surface realization. A surface can be regenerated without changing ground truth; any skeleton change requires proof, canon, compilation, and downstream gates again.
Case-generation sequence#
Counterexamples return to the symbolic proposal; surface-quality failures return to realization. Routing the wrong failure upstream either wastes cost or risks silently altering the mystery.
Durable case and proof records#
This picture is wider than it can be shown here. Move across it, or read it as text.
Drawn from its Mermaid source.
As text
Parts: - CASE_BRIEF - CASE_VERSION - SUSPECT - CLUE - ALIBI - SOLUTION - DEDUCTION_EDGE - PROOF_ARTIFACT - CANON_BINDING - SURFACE_VERSION - ASSET - PROVENANCE - COMPILED_BUNDLE - GATE_VERDICT - PLAY_SESSION Connections: - CASE_BRIEF to CASE_VERSION (one to zero or many): produces - CASE_VERSION to SUSPECT (one to one or many): contains - CASE_VERSION to CLUE (one to one or many): contains - CASE_VERSION to ALIBI (one to zero or many): constrains - CASE_VERSION to SOLUTION (one to one): proves - CLUE to DEDUCTION_EDGE (zero or many to zero or many): participates - SOLUTION to DEDUCTION_EDGE (one to one or many): requires - CASE_VERSION to PROOF_ARTIFACT (one to zero or many): verified_by - CASE_VERSION to CANON_BINDING (one to zero or many): binds - CASE_VERSION to SURFACE_VERSION (one to zero or many): realizes - SURFACE_VERSION to ASSET (one to zero or many): contains - ASSET to PROVENANCE (one to zero or many): records - SURFACE_VERSION to COMPILED_BUNDLE (one to zero or many): compiles - COMPILED_BUNDLE to GATE_VERDICT (one to zero or many): receives - COMPILED_BUNDLE to PLAY_SESSION (one to zero or many): supports
Show source
erDiagram
CASE_BRIEF ||--o{ CASE_VERSION : produces
CASE_VERSION ||--|{ SUSPECT : contains
CASE_VERSION ||--|{ CLUE : contains
CASE_VERSION ||--o{ ALIBI : constrains
CASE_VERSION ||--|| SOLUTION : proves
CLUE }o--o{ DEDUCTION_EDGE : participates
SOLUTION ||--|{ DEDUCTION_EDGE : requires
CASE_VERSION ||--o{ PROOF_ARTIFACT : verified_by
CASE_VERSION ||--o{ CANON_BINDING : binds
CASE_VERSION ||--o{ SURFACE_VERSION : realizes
SURFACE_VERSION ||--o{ ASSET : contains
ASSET ||--o{ PROVENANCE : records
SURFACE_VERSION ||--o{ COMPILED_BUNDLE : compiles
COMPILED_BUNDLE ||--o{ GATE_VERDICT : receives
COMPILED_BUNDLE ||--o{ PLAY_SESSION : supports
Case, proof, canon, surface, compiled bundle, gate, and play-session versions are explicit. The immutable skeleton and regenerable surface are related but must never share an ambiguous revision identity.
Case lifecycle#
This picture is wider than it can be shown here. Move across it, or read it as text.
Drawn from its Mermaid source.
As text
Parts: - Start (initial) - Proposed - ConstraintValid - UniquelySolved - FairPlayVerified - CanonBound - Realized - Compiled - Evaluated - Released - Rejected - Ambiguous - Regenerating - Withheld - Retracted Connections: - Start to Proposed - Proposed to ConstraintValid: typed world and case constraints pass - ConstraintValid to UniquelySolved: formal uniqueness proof exists - UniquelySolved to FairPlayVerified: clue completeness and rules pass - FairPlayVerified to CanonBound: continuity accepted - CanonBound to Realized: prose assets voice and suspects generated - Realized to Compiled: compatible V5 bundle emitted - Compiled to Evaluated: automated and independent evidence attached - Evaluated to Released: all eight release-decision gates pass - Proposed to Rejected: invalid or unsatisfiable - ConstraintValid to Ambiguous: multiple solutions or missing inference - Ambiguous to Proposed - Realized to Regenerating: surface-only failure - Regenerating to Realized - Evaluated to Withheld: evidence gate or operations absent - Released to Retracted: regression rights safety or canon conflict
Show source
stateDiagram-v2
[*] --> Proposed
Proposed --> ConstraintValid: typed world and case constraints pass
ConstraintValid --> UniquelySolved: formal uniqueness proof exists
UniquelySolved --> FairPlayVerified: clue completeness and rules pass
FairPlayVerified --> CanonBound: continuity accepted
CanonBound --> Realized: prose assets voice and suspects generated
Realized --> Compiled: compatible V5 bundle emitted
Compiled --> Evaluated: automated and independent evidence attached
Evaluated --> Released: all eight release-decision gates pass
Proposed --> Rejected: invalid or unsatisfiable
ConstraintValid --> Ambiguous: multiple solutions or missing inference
Ambiguous --> Proposed
Realized --> Regenerating: surface-only failure
Regenerating --> Realized
Evaluated --> Withheld: evidence gate or operations absent
Released --> Retracted: regression rights safety or canon conflict
Each transition emits a typed artifact or verdict. Withheld is a valid final release posture when evidence is insufficient; it must not be converted to a pass by retrying a judge until it agrees.
Subsystem composition#
The composition makes the two-track contract visible: the verified skeleton survives regeneration, while every realized/compiled version remains bound to the exact skeleton, canon, runtime, and evidence used.
Ariadne ownership estate#
Drawn from its Mermaid source.
As text
Tree:
- Ariadne
- Symbolic truth
- Clew proposal
- Minos proof
- Fair-play rules
- Palimpsest canon
- Realization
- Anansesem writers room
- Loom media production
- Ori living suspects
- Rights safety and provenance
- Delivery
- Daedalus compiler and V5 bridge
- Theseus automated evaluation
- Independent quality evidence
- Oracle direction and rollout
- Cross-cutting
- Determinism replay and cost
- Localization accessibility and fallback
- Observability versioning and rollback
- Backlog decisions dependencies and researchShow source
mindmap
root((Ariadne))
Symbolic truth
Clew proposal
Minos proof
Fair-play rules
Palimpsest canon
Realization
Anansesem writers room
Loom media production
Ori living suspects
Rights safety and provenance
Delivery
Daedalus compiler and V5 bridge
Theseus automated evaluation
Independent quality evidence
Oracle direction and rollout
Cross-cutting
Determinism replay and cost
Localization accessibility and fallback
Observability versioning and rollback
Backlog decisions dependencies and research
Every branch has a typed boundary. Oracle schedules only; it cannot waive a proof or release gate. Theseus diagnoses and evaluates; it cannot serve as its own independent G5 evidence.
Player investigation journey#
Drawn from its Mermaid source.
As text
Steps: - 1. Enter a coherent world and understand the case (good). Discover. Player. Score 5 of 5. - 2. Observe accessible clues with provenance cues (good). Discover. Player. Score 5 of 5. - 3. Question living suspects and test alibis (good). Investigate. Player, Ori. Score 5 of 5. - 4. Revisit evidence without canon drift (good). Investigate. Player, Palimpsest. Score 5 of 5. - 5. Build a supported inference chain (good). Deduce. Player. Score 5 of 5. - 6. Receive honest contradiction or missing-clue feedback (good). Deduce. Player. Score 5 of 5. - 7. Accuse through a uniquely reachable solution (good). Resolve. Player, Minos. Score 5 of 5. - 8. See consequences and continue in stable canon (good). Resolve. Player, Oracle. Score 5 of 5.
Show source
journey
title A fair V8 mystery from the player's seat
section Discover
Enter a coherent world and understand the case: 5: Player
Observe accessible clues with provenance cues: 5: Player
section Investigate
Question living suspects and test alibis: 5: Player, Ori
Revisit evidence without canon drift: 5: Player, Palimpsest
section Deduce
Build a supported inference chain: 5: Player
Receive honest contradiction or missing-clue feedback: 5: Player
section Resolve
Accuse through a uniquely reachable solution: 5: Player, Minos
See consequences and continue in stable canon: 5: Player, Oracle
Release evidence must prove this complete journey, not just successful case generation or a solver verdict in isolation.
Evidence order#
The timeline orders proof; it does not let a downstream quality score repair a missing symbolic invariant.
How to use this atlas#
Use the landscape and sequence for pipeline review, the ER/state models for artifact/version review, the class/estate views for ownership, and the journey/timeline for player and release evidence. Continue to the V8 guide, feature index, and architecture index.