Ariadne · Architecture

V8 — Architecture (Page Index)

A focused page within the Ariadne Architecture documentation. The full map and every sibling page live in the Architecture hub.

6sections2 minread1diagram

On this page

This directory holds the V8 (Ariadne — a self-authoring detective universe) architecture reference, decomposed from the single ../V8_ARCHITECTURE.md hub into focused, in-depth, code-grounded pages. The hub remains the canonical entry point and preserves every section heading; each page below expands one part of the system with richer, code-grounded detail and an honest implemented / spec-only status. V8 is a small product with a focused real symbolic core and an ambitious spec, so the pages are deliberately consolidated and explicit about what is shipped versus designed. The companion feature map lives in ../V8_features.md.

Cross-reference convention. Page-to-page links are relative (./<slug>.md). Platform-foundation links point at the shared platform/ space.

Architecture landscape#

FlowchartFlowchart: 13 steps and 14 connections.Seeded case brief andworld constraintsClew case proposalMinos formal solvabilityand uniqueness proofPalimpsest canon graphAnansesem writers roomLoom media realizationOri living suspectsDaedalus compiler and V5runtime bridgeTheseus automated playand evaluationIndependent eight-gateReleaseDecisionOracle delivery andoperationsProof case and canonartifactsCompiled provenance andreplay artifacts
Flowchart: Flowchart. Flowchart: 13 steps and 14 connections.

Drawn from its Mermaid source.

As text
Parts:
- Seeded case brief and world constraints
- Clew case proposal
- Minos formal solvability and uniqueness proof
- Palimpsest canon graph
- Anansesem writers room
- Loom media realization
- Ori living suspects
- Daedalus compiler and V5 runtime bridge
- Theseus automated play and evaluation
- Independent eight-gate ReleaseDecision
- Oracle delivery and operations
- Proof case and canon artifacts (data)
- Compiled provenance and replay artifacts (data)

Connections:
- Seeded case brief and world constraints to Clew case proposal
- Clew case proposal to Minos formal solvability and uniqueness proof
- Minos formal solvability and uniqueness proof to Palimpsest canon graph
- Palimpsest canon graph to Anansesem writers room
- Palimpsest canon graph to Loom media realization
- Anansesem writers room to Ori living suspects
- Loom media realization to Ori living suspects
- Ori living suspects to Daedalus compiler and V5 runtime bridge
- Daedalus compiler and V5 runtime bridge to Theseus automated play and evaluation
- Theseus automated play and evaluation to Independent eight-gate ReleaseDecision
- Independent eight-gate ReleaseDecision to Oracle delivery and operations
- Minos formal solvability and uniqueness proof to Proof case and canon artifacts
- Daedalus compiler and V5 runtime bridge to Compiled provenance and replay artifacts
- Independent eight-gate ReleaseDecision to Compiled provenance and replay artifacts
Show source
flowchart LR
  Brief[Seeded case brief and world constraints] --> Clew[Clew case proposal]
  Clew --> Minos[Minos formal solvability and uniqueness proof]
  Minos --> Palimpsest[Palimpsest canon graph]
  Palimpsest --> Anansesem[Anansesem writers room]
  Palimpsest --> Loom[Loom media realization]
  Anansesem --> Ori[Ori living suspects]
  Loom --> Ori
  Ori --> Daedalus[Daedalus compiler and V5 runtime bridge]
  Daedalus --> Theseus[Theseus automated play and evaluation]
  Theseus --> Decision[Independent eight-gate ReleaseDecision]
  Decision --> Oracle[Oracle delivery and operations]
  Minos --> Artifacts[(Proof case and canon artifacts)]
  Daedalus --> Artifacts2[(Compiled provenance and replay artifacts)]
  Decision --> Artifacts2

Each edge carries a typed, versioned artifact rather than shared mutable prose. Failures route according to ownership: symbolic ambiguity returns to Clew, canon conflicts to Palimpsest, surface defects to realization, compatibility to Daedalus, and missing independent evidence to release withholding.

Use this index to trace one immutable case version through contracts, proof, canon, realization, living-suspect policy, compilation, automated evaluation, independent release gates, staging, observation, and rollback. Pair the trace with the feature index so pipeline success is measured against the complete fair player experience.

Every focused architecture page appears exactly once below. The V8 documentation guide supplies the case-truth model and role paths; the diagram atlas supplies the shared visual vocabulary. Gap/research/decision/dependency sources, backlog, current artifacts/tests, human-aligned evidence, and production operations govern completion.

The case identifier, schema version, seed, solver result, canon revision, model and prompt identifiers, asset provenance, compiler target, evaluation report, and release decision together form the trace key. A reader should be able to move forward from the brief to delivery or backward from a player-visible clue without guessing which regenerated surface or proof artifact was used. If that join is absent, the pipeline is not auditable even when every individual stage reports success.

Orientation#

Data Contracts#

  • Canonical Data Contracts — the typed case bundle, clue/suspect/alibi/solution shapes, and gate verdicts every stage shares.

The Symbolic Core#

Surface Realization#

Delivery, Evaluation & Operations#