Skip to content

Concepts

Memory architecture

Separate context, governance and persistence to understand the guarantees.

From integration to memoryThe integration supplies context. SemanticLayer organizes tags and budget. GovernedStore applies access and protection before querying the backend. The integration decides how results enter the prompt. 1.IntegrationcontextDetects and queries2.SemanticLayertagsFilters and orders3.GovernedStoreaccessReads and writes4.Backendpersistence
From integration to memory. The integration supplies context. SemanticLayer organizes tags and budget. GovernedStore applies access and protection before querying the backend. The integration decides how results enter the prompt.

From context to storage

The integration receives context. SemanticLayer validates ontology, detects tags and manages the budget. GovernedStore applies protection, access and ordering. The backend stores and queries data according to its declared capabilities.

Tags first; semantics as a complement

Tag search uses exact matching. Semantic search combines text and vectors when configured, without replacing rule retrieval. ACLs, expiration and injection risk filter what may enter context.

Guarantees with boundaries

Rules reach the prompt through integrations that build it. MCP and CLI provide on-demand queries. The memory backend is volatile and Qdrant is experimental; the governed layer does not remove these storage limitations.