Topology

This is the reference topology for the stack validated live on 2026-03-30.

Quick read

• NATS is the center of operational coupling
• owasaka and spectre feed the event backbone
• phantom-api and ai-agent-os are part of the operational core
• cerebro, securellm-bridge, and spooknix define the intelligence layer
• Prometheus, Grafana, and Jaeger observe the system
• neotron closes the compliance layer

Logical map

flowchart LR
    O[owasaka]
    S[spectre]
    N[NATS]
    P[phantom-api]
    A[ai-agent-os]
    C[cerebro]
    B[securellm-bridge]
    K[spooknix]
    M[Prometheus]
    G[Grafana]
    J[Jaeger]
    T[neotron]

    O --> N
    S --> N
    N --> P
    N --> A
    N --> C
    C --> B
    K --> B
    P --> J
    A --> M
    P --> M
    C --> M
    M --> G
    P --> T
    N --> T

Layered view

1. Ingestion

• owasaka: collects signals and publishes network events
• spectre: defines and organizes the event domain

2. Backbone

• NATS: central bus between producers, APIs, agents, and observability

3. Operational core

• phantom-api: exposes endpoints and participates in the main flow
• ai-agent-os: publishes system telemetry into the bus

4. Intelligence

• cerebro: indexing, RAG, and analysis workflows
• securellm-bridge: security and routing layer for inference
• spooknix: specialized workloads and MCP or audio integrations

5. Observability

• Prometheus: metrics
• Grafana: operational visualization
• Jaeger: tracing

6. Compliance

• neotron: trail and integration for the regulated layer

Editorial rule

When there is doubt about where something belongs:

1. If it changes this topology, it belongs in the main path.
2. If it only deepens one approved system, keep it in Core System.
3. If it does not affect the validated stack, keep it in Reference or out of the main path.