# V8 Diagram Atlas 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 ```mermaid 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 ```mermaid sequenceDiagram participant Oracle as Oracle request participant Clew participant Minos participant Canon as Palimpsest participant Room as Anansesem and Loom participant Compile as Daedalus participant Eval as Theseus and release gates Oracle->>Clew: Seeded case brief and world constraints Clew->>Minos: Typed suspects clues alibis constraints and solution alt unsatisfiable ambiguous or unfair Minos-->>Clew: Counterexample and rejected verdict Clew->>Clew: Revise symbolic proposal else uniquely solvable Minos-->>Canon: Proof artifact and verified skeleton Canon-->>Room: Canon-bound realization brief Room-->>Compile: Prose dialogue assets voice and suspect policies Compile->>Eval: Versioned playable case bundle alt quality safety canon or independent evidence fails Eval-->>Room: Directed regeneration or withholding else all release gates pass Eval-->>Oracle: Immutable release decision and evidence refs end end ``` 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 ```mermaid 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 ```mermaid 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 ```mermaid classDiagram class VerifiedSkeleton { caseVersion seed solution proofRef } class CanonEnvelope { worldRevision entityBindings conflictPolicy } class SurfaceBundle { proseVersion assetRefs suspectPolicies } class CompiledCase { runtimeVersion contentHash provenanceRef } class ReleaseDecision { gateVerdicts evidenceRefs cohortPolicy } VerifiedSkeleton --> CanonEnvelope : bound by CanonEnvelope --> SurfaceBundle : constrains SurfaceBundle --> CompiledCase : compiled as VerifiedSkeleton --> CompiledCase : embedded in CompiledCase --> ReleaseDecision : evaluated into ``` 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 ```mermaid 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 ```mermaid 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 ```mermaid timeline title V8 release evidence Contract : Typed case skeleton canon surface and gate schemas : Seed version provider rights and compatibility policy Proof : Satisfiability uniqueness completeness and fair-play artifacts : Canon conflict and referential-integrity evidence Realization : Prose assets voice suspects compiler and runtime bridge : Accessibility localization safety provenance and cost Evaluation : Complete automated play and adversarial regression : Independent preregistered human-aligned quality evidence Release : Eight-gate decision staged cohort observability and rollback : Current retraction incident and production evidence ``` 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](./README.md), [feature index](../features/README.md), and [architecture index](../architecture/README.md).