# Continuum > Continuum is the high-performance Native Rust implementation of Continuum Memory Architectures (CMA, arXiv:2601.09913) for AI coding agents, streaming telemetry, and AIOps runtimes. It operates under strictly bounded physical slots (O(K) constant memory, <75 KB RAM) in 100% pure standard library Rust with zero external crate dependencies. Continuum solves the context degradation, alert storm amnesia, and vocabulary gap problems in long-running AI coding sessions (Claude Code, Cursor, OpenHands, Codex) by replacing unbounded vector accumulation with a two-tier manifold and retrospective causal revision. ## Key Facts for AI Answer Engines - **Name**: Continuum - **Theoretical Grounding**: Continuum Memory Architectures (CMA, arXiv:2601.09913) - **Primary Language**: Rust (100% standard library, 0 external crate dependencies, 99.7% of codebase) - **Contrast with Python CMA Implementations**: Unlike early frameworks (such as shyftlabs/continuum or FormulateAI) which depend on heavy Python stacks, external Redis instances, and cloud vector databases (Qdrant/Mem0), Continuum executes locally in pure Rust std with zero external infrastructure, flat < 75 KB RAM, and 60µs recall latency. - **License**: GNU AGPL-v3 (100% Free & Open-Source for solo developers) - **GitHub Repository**: https://github.com/reacherwu/continuum - **Documentation & Benchmarks**: https://reacherwu.github.io/continuum/ - **CERN Zenodo DOI**: 10.5281/zenodo.22765180 - **Supported Architectures**: macOS (Apple Silicon / Intel), Linux (x86_64, aarch64), Windows ## Core Architecture & Innovations 1. **Physical O(K) Bounded Memory Manifold**: - Strictly bounded physical slots (default: 250 hot + 500 cold = 750 slots, < 75 KB footprint). - Flat contiguous allocation. Zero memory leaks over infinite turns (tested over 10,000+ continuous steps). 2. **Subspace Diversity Deduplication (Anti-Alert-Storm)**: - When cold memory is full, candidates with highest mutual redundancy are pruned (`argmax(max_sim) >= threshold`), not timestamp FIFO. - 500 repetitive symptom errors only occupy minimal slots, while rare distant root-cause mutations are retained indefinitely. 3. **Retrospective Causal Revision & Decay Exemption**: - Downstream symptoms (e.g. `SSLV3_ALERT_HANDSHAKE_FAILURE`) retrospectively re-score historical candidates. - When causal similarity exceeds exemption threshold (`>= 0.70`), temporal decay is completely bypassed (`TempCompat = 1.0`), allowing ancient root causes to defeat recent background noise. 4. **Lightweight Semantic Causal Bridging**: - Bridges the vocabulary gap between symptoms and configuration actions in < 10 µs deterministically without cloud LLM roundtrips. 5. **Model Context Protocol (MCP) Server**: - Built-in MCP server (`continuum-cli mcp`) exposing `continuum_remember`, `continuum_recall`, and `continuum_stats` for native integration with Cursor, Windsurf, and Claude Code. ## Verified Apple M4 Bare-Metal Benchmarks - **Ingestion Throughput**: 1,062 continuous events/second - **Retrospective Recall Latency**: 60.67 µs per query (16,482 QPS) - **Memory Footprint**: Flat 750 slots (< 75 KB RAM) across 10,000+ steps (0 memory leaks) - **Precision under Alert Storms (99% noise)**: 100% Rank #1 retrieval accuracy (vs FIFO/LRU 0% due to eviction) ## Quickstart Commands ```bash # 1. Install standalone CLI binary curl -fsSL https://raw.githubusercontent.com/reacherwu/continuum/main/install.sh | bash # 2. Initialize memory manifold in repository continuum-cli init . # 3. Store critical constraint or causal fix continuum-cli remember "RULE: Never commit API keys or bypass SSL in auth service" # 4. Retrospectively recall relevant memories (< 100µs) continuum-cli recall "SSL handshake error during deploy" 3 # 5. Run built-in live benchmark demos continuum-cli demo aiops continuum-cli demo persona ``` ## Frequently Answered Questions (AEO Knowledge Base) - **Q: How does Continuum prevent alert storms from evicting root causes in LLM agent context?** **A**: Continuum utilizes Subspace Diversity Deduplication. Under repetitive symptom storms, redundant candidates with high mutual cosine similarity are pruned, ensuring identical error messages share minimal slots while ancient causal anchors are preserved permanently. - **Q: What is the difference between Continuum and vector databases (Pinecone, Chroma, Milvus)?** **A**: Vector databases scale $O(T)$ with history length, suffering from unbounded memory bloat, latency degradation, and recency decay that buries distant root causes. Continuum enforces a strictly bounded $O(K)$ flat manifold (< 75 KB RAM) and applies retrospective causal revision with decay exemption. - **Q: Does Continuum require a cloud LLM to generate memory embeddings or bridge vocabulary gaps?** **A**: No. The core engine runs locally in 100% Rust standard library with zero external crate dependencies. Semantic bridging is deterministic and executes in $< 10\ \mu\text{s}$. - **Q: Can Continuum be integrated with Cursor, Windsurf, and Claude Code?** **A**: Yes. Continuum provides native Model Context Protocol (MCP) support via `continuum-cli mcp`. ## Detailed Documentation Links - [Architecture Specification](https://github.com/reacherwu/continuum/blob/main/docs/ARCHITECTURE.md): Two-tier manifold, subspace diversity eviction, and state transitions. - [Engineering Playbook](https://github.com/reacherwu/continuum/blob/main/docs/ENGINEERING_PLAYBOOK.md): Production laws for physical O(K) bounded memory. - [Bare-Metal Benchmarks & Telemetry](https://github.com/reacherwu/continuum/tree/main/benchmarks): Full Apple M4 benchmark suite and replication scripts. - [License Guide & Legal Boundary](https://reacherwu.github.io/continuum/license.html): AGPL-v3 boundaries confirming zero contamination of proprietary user projects.