Synedrix OS has a 12-layer architecture.

#LayerPrimary purposeMust not own
1Human Interface LayerCapture human intent, approvals, and operational reviewDomain logic execution, tool adapters, memory internals
2Goal & Intent LayerTranslate business objectives into structured intentsDomain-specific execution logic, raw tool calls
3Orchestration LayerRoute work, decompose goals, sequence tasks, manage retries and approvalsDomain-specific heuristics, long-lived memory management
4Agent Runtime LayerExecute agents with bounded scope and lifecycle managementUI concerns, business-specific workflow routing
5Agent Registry LayerDefine discoverable capabilities and boundariesDomain workflows, runtime execution itself
6Tool Abstraction LayerNormalise access to external systemsDomain decision logic, human interface concerns, domain-specific policies
7Memory & Data LayerPersist business state and contextual knowledge, and govern how it is formed, recalled and forgottenWorkflow sequencing, UI logic, retention policy (Layer 12 sets the values), context assembly for a specific run (Layer 4)
8Event LayerStandardise event production, transport, and consumptionDomain-specific policy logic
9Governance & Controls LayerEnforce policy, permissions, approvals, complianceDomain execution logic itself
10Observability LayerMake execution measurable, explainable, reviewableBusiness decisions, domain state ownership
11Domain Pack LayerInject domain-specific entities, workflows, agents, toolsShared OS primitives
12Business Instance LayerConfigure a concrete runtimeShared platform abstractions

Stack topology

SliceLayers
Human and intent surface1, 2
Orchestration core3, 4, 5
Infrastructure services6, 7, 8
Governance and observability9, 10
Domain and runtime config11, 12

The layers stacked in their slices:

flowchart TB
    subgraph s1["Human and intent surface"]
        l1["1. Human Interface Layer"]
        l2["2. Goal & Intent Layer"]
    end
    subgraph s2["Orchestration core"]
        l3["3. Orchestration Layer"]
        l4["4. Agent Runtime Layer"]
        l5["5. Agent Registry Layer"]
    end
    subgraph s3["Infrastructure services"]
        l6["6. Tool Abstraction Layer"]
        l7["7. Memory & Data Layer"]
        l8["8. Event Layer"]
    end
    subgraph s4["Governance and observability"]
        l9["9. Governance & Controls Layer"]
        l10["10. Observability Layer"]
    end
    subgraph s5["Domain and runtime config"]
        l11["11. Domain Pack Layer"]
        l12["12. Business Instance Layer"]
    end
    s1 --> s2
    s2 --> s3
    s3 --> s4
    s4 --> s5

Layer principles

  1. Shared before specific
  2. Controls before execution
  3. Tools are adapters, not business logic
  4. Memory is shared, access is scoped
  5. Memory moves only under governance

Platform mapping

Which platform in the tech stack implements each layer.

PlatformLayer(s)Notes
n8n3Orchestration only. Complex agent reasoning runs in LangGraph (Layer 4). See ADR-OS-001.
LangGraph4Stateful, cyclic, multi-agent reasoning runtime invoked by n8n as a governed step.
Hookdeck8Ingress webhook fan-out and replay.
Hookdeck Outpost8Egress delivery and retry for outbound events.
Redis7Hot state and pub/sub.
Supabase PG177Canonical relational truth.
QuestDB7Time-series metrics and telemetry.
Neo4j7Context graph and decision lineage. Backs the graph memory tier through the NAMS client, adopted as a library rather than a platform row. See ADR-OS-002.
Qdrant7Semantic vector memory; the single vector substrate for every indexed memory tier.
Langfuse10LLM tracing and prompt engineering.
PostHog10Behavioural analytics.
Grafana LGTM Stack10Operational monitoring (Grafana, Alloy, Mimir, Loki, Tempo).