Namespace: memory-steward • Owner: architecture-team
← Prev: Contributing | Next: Architecture Cheat Sheet →
- 0. Status, Scope, and Authority
- 1. What is this?
- 2. Documentation Index
- 3. Architecture & Standards
- 4. Quick Start (Deployment)
- 5. License
- 6. Closing Statement
Status: ACTIVE / CANONICAL Audience: General Engineering Public Change policy:
- Append-only
- No silent edits
Documentation: docs/
Memory Steward is not a chatbot. It is a Cognitive Control Plane that enforces determinism, safety, and long-term memory coherence on top of probabilistic LLMs.
It separates Reasoning (The Model) from Memory & Policy (The Steward), ensuring that critical invariants—like safety rules, personality constraints, and authoritative facts—are never hallucinated or forgotten.
The system is fully specified in the docs/ directory.
- 01_overview.md: System architecture, taxonomy, and core invariants.
- 10_industry_landscape.md: Why we built this (vs. RAG/LangChain).
- 11_design_principles.md: Async semantics and storage philosophy.
- 02_operational_mode.md: How the system decides "Engineering" vs "Casual".
- 03_reference.md: How to ingest documentation (Reference Memory).
- 04_optimizations.md: Caching, Speculation, and Latency tuning.
- 05_stability.md: Hysteresis loops to prevent mode jitter.
- 06_telemetry.md: Metrics, Dashboards, and SQL schemas.
- 07_glass_pane.md: The "Glass Pane" management interface (MCP).
- 09_runtime_contract.md: Env vars, Ports, and C4 Architecture.
- 08_verification.md: The "Definition of Done" and regression tests.
- 00_style_guide.md: Documentation standards.
Memory Steward is not just a codebase; it is a reference implementation of the Dual-Plane Memory Architecture. We adhere to strict engineering standards to prevent "Probabilistic Drift" in production systems. For deep dives and architectural reasoning, please refer to our core documentation:
- Technical White Paper: The "Engineering Manifesto." Explains the philosophy of Determinism, the "Alignment Tax" of memory, and why we split the system into Data and Control planes.
- RFC Standard (Proposal): The formal specification for the Dual-Plane Architecture. Defines the strict separation of concerns, async admission contracts, and atomic storage requirements.
- Architecture Cheat Sheet: A high-density one-pager for System Operators. Contains the C4 System Map, Env Variable Reference, and MCP Tool definitions for quick lookup.
See DEPLOYMENT.md for Kubernetes instructions.
Apache License 2.0
See LICENSE file for details.
This repository constitutes the definitive implementation of the Memory Steward, operating strictly within the invariants defined by the core engineering specifications.
END OF DOCUMENT README
