# V9 — Architecture (Page Index)

This directory decomposes the single
[`../V9_ARCHITECTURE.md`](../V9_ARCHITECTURE.md) hub into focused, in-depth,
code-grounded pages. The hub remains the canonical entry point and preserves its
heading anchors (so existing cross-references keep resolving); each page below
expands one section with far richer, code-grounded detail. The companion feature
section lives at [`../features/README.md`](../features/README.md).

> **Cross-reference convention.** A bare `§N` / `§N.M` points at a section of
> the backlog [`../V9_TODOS.md`](../V9_TODOS.md); `deps§N` points at
> [`../V9_DEPENDENCIES.md`](../V9_DEPENDENCIES.md); page-to-page links are
> relative (`./<slug>.md`, or `../features/<slug>.md` for the companion).

## Architecture landscape

```mermaid
flowchart LR
  Wonder[Wonder and consented learner context] --> Atlas[Atlas knowledge spine]
  Atlas --> Ground[Sophia sources and Nyx or Kalika kernels]
  Ground --> Prometheus[Prometheus lesson pipeline]
  Prometheus --> Hephaestus[Hephaestus explorable runtime]
  Prometheus --> Chiron[Chiron tutor and delivery surfaces]
  Hephaestus --> Aletheia[Aletheia seven gates]
  Chiron --> Aletheia
  Aletheia --> Artifact[Immutable skeleton and regenerable lesson surfaces]
  Artifact --> Delivery[Web-first cache LMS and modality fallback]
  Delivery --> Mnemosyne[Mastery and spaced retrieval]
  Mnemosyne --> Theia[Continuation and personal Atlas]
  Artifact --> Evidence[(Claim source kernel gate provenance and replay)]
  Evidence --> Governance[AgentRun budgets kill switch audit retraction and operations]
```

V9 adds a small product-specific layer over a six-layer reused platform; it does
not create another agent loop or grounding system. Each edge carries typed
identifiers, versions, evidence, and refusal behavior so generated surfaces
cannot outrun source, computation, pedagogy, consent, or governance authority.

Use this index to trace a wonder through graph resolution, source/kernel
grounding, solve-first planning, realization, seven gates, compiled artifact,
delivery/fallback, assessment/mastery, continuation, correction, and rollback.
Pair the trace with the [feature index](../features/README.md) so architectural
composition is measured against the learner's complete, accessible job.

Every focused architecture page appears exactly once below. The
[V9 documentation guide](../docs/README.md) supplies the lesson-truth model and
role paths; the [diagram atlas](../docs/diagram-atlas.md) supplies the shared
visual vocabulary. Product/gap/research/dependency sources, backlog, current
artifacts/tests, learner evidence, deployment, and retraction/operations govern
completion.

## Orientation

- [V9 Architecture Overview — A Curious Ape's Guide to Reality](./overview.md) —
  The integration-architecture thesis: V9 adds three genuinely-new pieces
  (Atlas, Hephaestus, the consumer experience layer) over ~80% composed Oshun
  substrate, gated behind seven release gates.
- [Subsystem Map & the New-vs-Composed Reuse Ledger](./subsystem-map-and-reuse-ledger.md)
  — Every Metis-myth subsystem (Atlas, Prometheus, Aletheia, Chiron, Hephaestus,
  Mnemosyne, Theia, Agora, Experience) mapped to the real lib/service that owns
  it, and the aggregate ~20%-new / ~80%-composed accounting.
- [The Six-Layer Reuse Stack](./six-layer-reuse-stack.md) — L1 model plane
  (Iris+Nous) → L2 Iris agent runtime → L3 capability tool servers → L4 Yemaya
  production orchestration → L5 governance plane → L6 delivery, consumed whole —
  V9 spawns no new agent loop.

## The Knowledge Spine

- [Atlas — The Knowledge Spine (Graph, Invariants, Wonder Resolution)](./atlas-knowledge-graph.md)
  — The unified knowledge graph assembled from the Metis/Sophia/Mnemosyne
  graphs, the ConceptNode/ConceptEdge contract with its grounding-pin and
  kernelRef invariants, and how a free-text wonder resolves to a minimal
  prerequisite-ordered concept set.

## Lesson Generation

- [The Prometheus Lesson-Generation Pipeline](./prometheus-lesson-pipeline.md) —
  The solve-first, HTN-planned, gated 9-stage pipeline (resolve → ground → plan
  → write → realize media → build explorable → assess → gate → compile →
  deliver), each stage emitting a replayable artifact, with profile-class
  caching and determinism as a cost lever.
- [Hephaestus — The Explorable Runtime](./hephaestus-explorables.md) — The three
  explorable kinds in increasing generative risk (computed-kernel Nyx/Kalika,
  verified generative widget, P2/P3 game-bridge), the explorable contract with
  its mandatory success state, and the verify-before-ship / G4 completeness
  rule.
- [The Lesson Artifact — Delivery Contract](./lesson-artifact.md) — The
  compiled, cacheable, provenance-stamped Lesson contract: the immutable
  verified-skeleton (groundTruth) vs regenerable-surface (narrative/media)
  split, claim-ref integrity, the seven gate verdicts, the C2PA bundle, and the
  Theia continuation thread.

## Governance & Platform Integration

- [The Seven Release Gates & Aletheia](./seven-gates-and-aletheia.md) — G1–G7
  (grounding, accuracy, pedagogy, completeness, quality, safety, provenance)
  enforced at Stage 7 on the shared platform release-gate, and Aletheia as a
  thin pass/fail policy over Sophia grounding + Nyx/Kalika recomputation — not a
  new RAG engine.
- [Web-First Delivery & Cross-Cutting Concerns](./delivery-and-cross-cutting.md)
  — Why P1 ships web-first with no Unreal/Bellona dependency (Nyx WebGL, Kalika
  WASM, Psyche avatar, Nous local inference), and the platform-wide concerns
  threaded through every lesson — governance, safety/age-gating, C2PA
  provenance, determinism/caching, localization/accessibility,
  identity/entitlements.