Egbe Companions · Architecture

V6 — Architecture (Page Index)

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

6sections3 minread1diagram

On this page

This directory holds the V6 (Egbe — an agentic-companion universe where autonomous AI agents, "Ori", live persistent lives in a shared world "Orun" and the player is a steward guiding their fate) architecture reference, decomposed from the single ../V6_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. The companion feature map lives in ../V6_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: 12 steps and 13 connections.Orun world server andauthoritative stateMoirai deterministic lifeticksOri identity biographymemory and consentCognition groundingplanning and policyVAC player communicationGoverned intent and worldeffectUE embodiment pixelstreaming and webfallbackClio narrativeFoundry ending and legacyAye cross-gameincarnationReplay provenance evaland auditWelfare cost performancesecurity testing and launch
Flowchart: Flowchart. Flowchart: 12 steps and 13 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:
- Orun world server and authoritative state
- Moirai deterministic life ticks
- Ori identity biography memory and consent (data)
- Cognition grounding planning and policy
- VAC player communication
- Governed intent and world effect
- UE embodiment pixel streaming and web fallback
- Clio narrative
- Foundry ending and legacy
- Aye cross-game incarnation
- Replay provenance eval and audit (data)
- Welfare cost performance security testing and launch

Connections:
- Orun world server and authoritative state to Moirai deterministic life ticks
- Ori identity biography memory and consent to Cognition grounding planning and policy
- Moirai deterministic life ticks to Cognition grounding planning and policy
- VAC player communication to Cognition grounding planning and policy
- Cognition grounding planning and policy to Governed intent and world effect
- Governed intent and world effect to Orun world server and authoritative state
- Governed intent and world effect to Ori identity biography memory and consent
- Orun world server and authoritative state to UE embodiment pixel streaming and web fallback
- Ori identity biography memory and consent to Clio narrative
- Ori identity biography memory and consent to Foundry ending and legacy
- Ori identity biography memory and consent to Aye cross-game incarnation
- Governed intent and world effect to Replay provenance eval and audit
- Replay provenance eval and audit to Welfare cost performance security testing and launch
Show source
flowchart TB
  World[Orun world server and authoritative state] --> Moirai[Moirai deterministic life ticks]
  Identity[(Ori identity biography memory and consent)] --> Cognition[Cognition grounding planning and policy]
  Moirai --> Cognition
  VAC[VAC player communication] --> Cognition
  Cognition --> Action[Governed intent and world effect]
  Action --> World
  Action --> Identity
  World --> Client[UE embodiment pixel streaming and web fallback]
  Identity --> Clio[Clio narrative]
  Identity --> Foundry[Foundry ending and legacy]
  Identity --> Aye[Aye cross-game incarnation]
  Action --> Evidence[(Replay provenance eval and audit)]
  Evidence --> Operations[Welfare cost performance security testing and launch]

The topology encloses probabilistic reasoning inside durable, versioned, replayable state and governed effect boundaries. A model response is neither a world action nor a biography update until the authoritative contract commits it and produces evidence.

Trace a change from Ori/consent version and Moirai tick through recall, grounding, cognition, policy, intent, world effect, biography/event receipt, embodiment, and evaluation/operations. Pair the trace with the feature index so runtime components are evaluated against autonomy, continuity, disclosure, accessibility, welfare, and recovery promises.

Every focused architecture topic appears exactly once below. The V6 documentation guide supplies the truth/welfare model and role paths; the diagram atlas supplies the shared visual language. Backlog, dependencies, current schemas/code/tests, evals, flagship evidence, model/provider state, and release operations govern completion.

Orientation#

The Agent Mind#

World, Edge, and Client#

Communication, Story, and Lifecycle#

Platform, Governance, and Launch#