Tip: select any text on this page to bring up the Ask tooltip and question the Synedrix OS assistant about it.
What Memory & Data is
Memory & Data persists business state and contextual knowledge, and owns the memory control plane: the governed process by which a record is formed, consolidated, promoted, recalled, decayed, and erased. Five self-hosted stores answer where a byte lives: Redis for hot state, Supabase PG17 for canonical relational truth, QuestDB for time-series, Neo4j for the context graph, Qdrant for semantic vectors. A lifecycle governs how a record moves between them.
Memory cognition is a control plane over persistence, in the same relationship Governance has to execution, not a peer layer beside it. These five stores, the two observability stores at Layer 10 (Langfuse and PostHog) and the control plane over all seven together make up the memory fabric.
What it owns, and what it does not
Every layer in the architecture has a non-overlapping responsibility. The boundary is as much a part of the design as the capability.
Owns
- Transactional databases, vector stores, graph stores, caches, and audit state: the five Layer 7 stores
- The tier taxonomy: eight tiers (working, episodic, semantic, procedural, profile, relational, graph, temporal)
- Record lifecycle: formation, consolidation, reflection, promotion, decay, and erasure
- Recall mediation: every memory read is a scoped, authorised tool call, never ambient context
- Promotion: the governed transition of a record from one tier to a longer-lived one
Does not own
- Workflow sequencing
- → Orchestration Layer
- UI logic
- → Human Interface Layer
- Retention policy: the concrete values, not the mechanism
- → Business Instance Layer
- Context assembly for a specific agent run
- → Agent Runtime Layer
Interfaces with
The other layers this one exchanges work, state, or decisions with, and why.
Agent runtime
LangGraph binds to the fabric through SynedrixMemoryStore, a compliance seam that enforces scope and rejects direct writes and deletes.
Orchestration
n8n owns the trigger and sequence for the scheduled memory-consolidation workflow.
Governance
the Memory Access Broker resolves scope before any store is queried; Policy Guard gates promotions, visibility widening, and every erasure.
Observability
every recall opens a Langfuse span nested under the agent's trace; memory events aggregate into QuestDB for fabric-level signals.
How Synedrix OS implements it
The Memory Fabric Specis the authoritative specification. Its eight-tier taxonomy separates what kind of memory a record is from where it's stored. Every governed record carries a 14-field envelope mirroring the event envelope: a record with no provenance back to a causing event is non-compliant by construction. Authority splits three ways: the Consolidation & Reflection Agent recommends, the Memory Curator commits, the Memory Access Broker approves access; no single agent both proposes and commits.
Three invariants are load-bearing and must never be violated: only the Memory Curator may commit durable memory; every other agent proposes; memory recall is an authorised tool call, never ambient context; and no record crosses a tier boundary without a governed promotion event, with erasure leaving a tombstone (a marker that something existed and was destroyed under an approval) rather than a silent gap.
ADR-OS-002 is the decision record behind this: memory cognition was framed as a control plane over persistence rather than a peer layer, extending Layer 7 instead of adding a thirteenth. NAMS (neo4j-labs/agent-memory) was adopted as a library over the existing self-hosted Neo4j, the same precedent LangChain set for LangGraph.
Platform mapping
Redis
The working tier: hot state for an in-flight run, TTL-bound, never a source of truth.
Supabase PG17
Write-authoritative for every audit-bearing tier.
QuestDB
The temporal tier: time-series measurements and fabric-level observability.
Neo4j
The graph tier's entity and reasoning half, reached through the NAMS client library.
Qdrant
The single semantic vector store for every indexed memory tier.
OS agents at this layer
Memory Curator Agent
control · os-agt-010The only agent that commits durable memory; every other agent proposes. Forms, consolidates, promotes and erases records.
Consolidation & Reflection Agent
intelligence · os-agt-011Proposes consolidations, reflections and distilled skills from accumulated memory. Reads broadly, writes nothing.
Layer principles that apply
- Memory is shared, access is scoped: agents need shared context, but access must remain selective and policy-aware.
- Memory moves only under governance: persisting a fact and deciding it's worth remembering are different acts; a record moves only through a governed path that leaves lineage behind.
Memory & Data questions, answered
Short, citable answers drawn from this page.
What is the Memory & Data layer in Synedrix OS?
Memory & Data is layer 7 of the twelve-layer Synedrix OS architecture, in the "Infrastructure services" group. Five Layer 7 stores and one governed lifecycle. Nothing moves without leaving lineage.
What does the Memory & Data layer own?
The Memory & Data layer owns: Transactional databases, vector stores, graph stores, caches, and audit state: the five Layer 7 stores; The tier taxonomy: eight tiers (working, episodic, semantic, procedural, profile, relational, graph, temporal); Record lifecycle: formation, consolidation, reflection, promotion, decay, and erasure; Recall mediation: every memory read is a scoped, authorised tool call, never ambient context; Promotion: the governed transition of a record from one tier to a longer-lived one.
What does the Memory & Data layer not own?
The Memory & Data layer does not own: Workflow sequencing (owned by Orchestration Layer); UI logic (owned by Human Interface Layer); Retention policy: the concrete values, not the mechanism (owned by Business Instance Layer); Context assembly for a specific agent run (owned by Agent Runtime Layer).
Which platforms implement the Memory & Data layer?
Redis: The working tier: hot state for an in-flight run, TTL-bound, never a source of truth.; Supabase PG17: Write-authoritative for every audit-bearing tier.; QuestDB: The temporal tier: time-series measurements and fabric-level observability.; Neo4j: The graph tier's entity and reasoning half, reached through the NAMS client library.; Qdrant: The single semantic vector store for every indexed memory tier.
The full reference page, with every canonical specification this layer touches, lives in the documentation repository, which is private while the platform is being built.