Ariadne · Guides & deep dives

V8 Diagram Atlas

The symbolic skeleton is established before expensive surface realization.

9sections2 minread

On this page

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#

FlowchartFlowchart: 15 steps and 16 connections.Case brief world canon andconstraintsClew proposes symbolicskeletonMinos proves satisfiableunique and completeKnox and Van Dinefair-play checksPalimpsest binds canoncontinuityAnansesem realizes proseand dialogueLoom realizes art audioand scene assetsOri living suspectsDaedalus compiles V5case bundleTheseus automated playand quality evaluationIndependent eight-gateReleaseDecisionOracle stages and directseligible casesPlayer investigationProof artifactsVersioned bundleprovenance and replay
Flowchart: Flowchart. Flowchart: 15 steps and 16 connections.

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#

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#

Entity-relationship diagramEntity-relationship diagram: 15 entities and 15 relationships.producescontainscontainsconstrainsprovesparticipatesrequiresverified_bybindsrealizescontainsrecordscompilesreceivessupportsCASE_BRIEFCASE_VERSIONSUSPECTCLUEALIBISOLUTIONDEDUCTION_EDGEPROOF_ARTIFACTCANON_BINDINGSURFACE_VERSIONASSETPROVENANCECOMPILED_BUNDLEGATE_VERDICTPLAY_SESSION
Entity-relationship diagram: Entity-relationship diagram. Entity-relationship diagram: 15 entities and 15 relationships.

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#

State diagramState diagram: 15 states and 16 transitions.typed world and case constraints passformal uniqueness proof existsclue completeness and rules passcontinuity acceptedprose assets voice and suspects generatedcompatible V5 bundle emittedautomated and independent evidence attachedall eight release-decision gates passinvalid or unsatisfiablemultiple solutions or missing inferencesurface-only failureevidence gate or operations absentregression rights safety or canon conflictProposedConstraintValidUniquelySolvedFairPlayVerifiedCanonBoundRealizedCompiledEvaluatedReleasedRejectedAmbiguousRegeneratingWithheldRetracted
State machine: State diagram. State diagram: 15 states and 16 transitions.

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#

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#

AriadneMind map: 21 ideas.AriadneSymbolic truthClew proposalMinos proofFair-play rulesPalimpsest canonRealizationAnansesem writers roomLoom media productionOri living suspectsRights safety andprovenanceDeliveryDaedalus compiler and V5bridgeTheseus automatedevaluationIndependent qualityevidenceOracle direction and rolloutCross-cuttingDeterminism replay andcostLocalization accessibilityand fallbackObservability versioningand rollbackBacklog decisionsdependencies and research
Mind map: Ariadne. Mind map: 21 ideas.

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 research
Show 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#

A fair V8 mystery from the player's seatUser journey: 8 stages.1Enter a coherent world and understand the caseDiscover. Player. Score 5 of 5.2Observe accessible clues with provenance cuesDiscover. Player. Score 5 of 5.3Question living suspects and test alibisInvestigate. Player, Ori. Score 5 of 5.4Revisit evidence without canon driftInvestigate. Player, Palimpsest. Score 5 of 5.5Build a supported inference chainDeduce. Player. Score 5 of 5.6Receive honest contradiction or missing-clue feedbackDeduce. Player. Score 5 of 5.7Accuse through a uniquely reachable solutionResolve. Player, Minos. Score 5 of 5.8See consequences and continue in stable canonResolve. Player, Oracle. Score 5 of 5.
User journey: A fair V8 mystery from the player's seat. User journey: 8 stages.

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#

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, feature index, and architecture index.