XO Universe Map

docs/xo-universe-map.md

# XO Universe Map

This page provides a **visual overview of the XO ecosystem** and how its modules connect into a single trust continuum.

XO is not designed as a monolithic platform. Instead it is a **network of cooperating layers** where each component performs a clear role.

!!! tip
    For a **domain-level view** of how the ecosystem is exposed publicly, also see:

    - [XO Domain Constellation](domain-constellation.md)

    That page shows how the XO modules map onto the domain architecture of the ecosystem.

---

# The XO Trust Continuum

```mermaid
%% XO Trust Continuum lifecycle diagram
flowchart LR

subgraph Core[Core Trust Layer]
    Vault[Vault\nSeal + Store]
    Pulse[Pulse\nPublish]
    Agent[Agent\nAutomation]
end

subgraph Activation[Activation Layer]
    Drops[Drops\nArtifacts]
    Traits[Traits\nEvolution]
    Bridge[Bridge\nPhysical Link]
end

subgraph Public[Public Memory Layer]
    Ledger[Ledger\nPublic Record]
    Digest[Digest\nDaily Memory]
end

Vault --> Pulse
Pulse --> Drops
Drops --> Traits
Traits --> Ledger
Pulse --> Digest
Agent --> Vault
Agent --> Pulse
Agent --> Drops
Bridge --> Ledger
# XO Universe Map

This page provides a **visual overview of the XO ecosystem** and how its modules connect into a single trust continuum.

XO is not designed as a monolithic platform. Instead it is a **network of cooperating layers** where each component performs a clear role.

!!! tip
    For a **domain-level view** of how the ecosystem is exposed publicly, also see:

    - [XO Domain Constellation](domain-constellation.md)

    That page shows how the XO modules map onto the domain architecture of the ecosystem.

---

## The XO Trust Continuum

```mermaid
%% XO Trust Continuum lifecycle diagram
flowchart LR

subgraph Core[Core Trust Layer]
    Vault[Vault\nSeal + Store]
    Pulse[Pulse\nPublish]
    Agent[Agent\nAutomation]
end

subgraph Activation[Activation Layer]
    Drops[Drops\nArtifacts]
    Traits[Traits\nEvolution]
    Bridge[Bridge\nPhysical Link]
end

subgraph Public[Public Memory Layer]
    Ledger[Ledger\nPublic Record]
    Digest[Digest\nDaily Memory]
end

Vault --> Pulse
Pulse --> Drops
Drops --> Traits
Traits --> Ledger
Pulse --> Digest
Agent --> Vault
Agent --> Pulse
Agent --> Drops
Bridge --> Ledger

This diagram represents the core lifecycle of an artifact inside the XO universe, while also grouping the system into three readable zones: the core trust layer, the activation layer, and the public memory layer.

Lifecycle Example

A typical flow inside the system looks like this:

Vault seals an artifact or message
Pulse publishes the event
Drops distribute the artifact
Traits allow the artifact to evolve
Ledger records the permanent history
Digest summarizes activity
Bridge links the digital artifact to the physical world

Automation and orchestration are handled by the Agent layer.

Why This Structure Exists

Most platforms combine everything into one application.

XO intentionally separates responsibilities because:

each module can evolve independently
systems remain easier to audit
failures cannot break the entire ecosystem
trust becomes verifiable instead of implied

This architecture forms what XO calls the Trust Continuum.

Mental Model

You can think of XO as a living universe of layers:

Layer	Role
Vault	Source of truth and signatures
Pulse	Communication layer
Drops	Distribution mechanism
Traits	Evolution and identity
Ledger	Immutable public memory
Digest	Human-readable summaries
Bridge	Connection to the physical world
Agent	Automation and coordination

Each layer strengthens the others.

Status

Most of these components already exist in prototype or early operational form across the XO repositories.

The current phase focuses on:

stabilizing infrastructure
clarifying documentation
gradually activating public modules

Over time the map above will transform from an architectural diagram into a fully active ecosystem.