Dual-Plane Memory
Architecture
The Data Plane stores memory and its context. The Control Plane governs admission, conflict handling, and memory policy. Reasoning and memory rules have distinct roles.
Four layers,
two planes
Agent Layer
Connected agents and applications
Transport
MCP and REST interfaces
Control Plane
Admission rules, policy enforcement, conflict review
Data Plane
Persistent memory, metadata, and search indexes
Rumi Governance
Claim validation, provenance, and review
Retrieval Engine
Relevant memories returned with context
Lifecycle Manager
Claim states, supersession, and audit records
Component
architecture
Ingestion & Transport
Connected agents and applications submit and retrieve memory through MCP or REST. Input validation and configured scope establish the context for each operation.
- Agent and application interfaces
- Input validation
- Project and user context
Control Plane — Admission & Policy
Memory policy stays separate from model reasoning. Validation, provenance, and conflict handling govern how claims enter and move through the Stash.
- Claim admission rules
- Source and citation checks
- Conflict resolution and review
- Operation audit records
Data Plane — Storage & Indexing
Persistent storage holds memories, metadata, and retrieval indexes. Namespaces keep project context scoped. Session state uses configurable expiry.
- Durable memory
- Structured metadata
- Search indexes
- Namespaced session state
Retrieval Engine
Semantic and keyword retrieval surface relevant knowledge. Results carry the context needed to inspect and reuse stored information.
- Meaning-based search
- Keyword matching
- Scoped results
- Source context
Lifecycle Manager
Claims move between explicit states as information changes. Review stale knowledge, handle conflicts, and preserve relationships between superseded claims.
- Candidate and confirmed claims
- Freshness and review
- Supersession and conflicts
- Archival and traceability
Deployment & Operations
Deploy the memory workflow in your environment. Configure local processing, monitor service health, and maintain scheduled backups with the retention your operations require.
- Local model processing
- Health and usage visibility
- Scheduled backups
- Configurable retention
- Optional offsite mirroring
Credentials take a separate path.
Detected secrets are handled outside ordinary memory content. When the encrypted vault is available, memory keeps a reference. When it is unavailable, detected values are redacted and the remaining content is retained.
Explore Security