V8 — Features (Page Index) — Ariadne

This directory holds the V8 (Ariadne — a self-authoring detective universe) feature map, decomposed from the single ../V8_features.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 product with richer, code-grounded detail and an honest implemented / spec-only status. V8 is a small product, so the pages are deliberately consolidated. The companion architecture reference lives in ../architecture/.

Cross-reference convention. Page-to-page links are relative (./<slug>.md); the architecture companion for a feature page is linked as ../architecture/<slug>.md. Platform-foundation links point at the shared platform/ space.

Feature landscape#

flowchart LR Player[Player mystery experience] --> Oracle[Oracle case selection and direction] Oracle --> Case[Generated case candidate] Case --> Proof[Clew proposal Minos proof and fair-play gates] Proof --> Canon[Palimpsest continuity] Canon --> Surface[Anansesem prose Loom assets and Ori suspects] Surface --> Compile[Daedalus V5-compatible bundle] Compile --> Eval[Theseus playtest and independent ReleaseDecision] Eval --> Player Proof --> Evidence[(Proof and constraint artifacts)] Surface --> Evidence2[(Provenance model prompt asset and rights records)] Eval --> Evidence2 Evidence2 --> Operations[Determinism cost localization observability rollback and release]

The landscape preserves V8's solve-first thesis. The immutable symbolic skeleton and canon are proved before the expensive experienced surface is realized. Prose, media, voice, and suspect performance may regenerate, but they remain bound to the exact verified case and cannot repair an ambiguous or unfair mystery.

Use this index to select the player-facing concern, pair it with the owning architecture page, and follow typed versions, seeds, proof, canon, generated surfaces, compiler compatibility, independent gate evidence, rollout, and retraction. Then inspect gap/research/decision/ dependency documents, backlog, current code/tests/artifacts, preregistered quality evidence, and production state before making a completion claim.

The five focused pages deliberately consolidate a small product without losing scope, and each appears exactly once below. The V8 documentation guide supplies role-based paths and the case-truth model; the diagram atlas supplies pipeline, proof, data, lifecycle, component, player, and release views. The separate eight-gate ReleaseDecision and seven-gate platform content harness remain named distinctly wherever gates are discussed.

When investigating a defect, classify it before following links. An impossible or multiply solvable case belongs to proposal and proof; a contradiction with a previous event belongs to canon; awkward dialogue or a missing asset belongs to realization; a broken playable package belongs to compilation; and a valid case that should not reach a cohort belongs to direction or release. This prevents a generative retry from hiding a truth failure and keeps every repair at the boundary that can prove it.

Orientation#

Overview & Player Promise — what V8 is, the player-facing experience, and the GA promise.

Generation, Proof & Canon#

Case Generation, Proof & Canon — how a fair case is minted and made provably solvable (Clew, the Minos SAT/CSP proof, and Palimpsest canon).

Realization & Suspects#

Realization & Living Suspects — turning a verified case into playable prose, assets, and interrogatable AI suspects.

Delivery & Operations#

Delivery, Direction & Operations — compiling, eval-gating, and directing a case for the player (Daedalus, Theseus, Oracle).
Cross-Cutting Concerns, the Pipeline & Localization — the end-to-end pipeline, determinism/cost/governance, localization, and observability.