Engram
Supports AMD ROCm hardware acceleration through the rocm-kernels flag, enabling wavefront HIP execution for geometric memory operations on AMD GPUs.
Supports Apple Metal hardware acceleration through automatic detection, enabling dynamic runtime compilation via metal-rs for geometric memory operations on macOS systems.
Provides integration with Google Antigravity IDE, allowing AI agents to access Engram's persistent geometric memory system and native tools for associative memory operations within the Antigravity development environment.
Supports NVIDIA CUDA hardware acceleration through the cuda-kernels flag, enabling BVH O(log N) indexing and NVMe parallel kernel computation for geometric memory operations on NVIDIA GPUs.
Engram
Persistent geometric memory for AI agents.
Patent Pending US19/372,256 — Aric Goodman & Static Rooster Media
Engram gives your AI agent a long-term memory that works directly like human associative memory—store anything, retrieve by meaning, not keywords. No vector database. No cloud. No API key. Runs entirely on your machine via the Model Context Protocol (MCP).
🚀 The AI Native Agentic Daemon
Engram is not just a passive database. When you map it into an LLM IDE (like Antigravity or Cursor), it boots an Agentic Daemon that handles geometric awareness completely in the background:
Native OS Watcher: By calling the
mcp_engram_watch_workspaceJSON tool, the Daemon binds directly to OS-level kernel events (inotify/fsevents). The moment you or your Agent saves any major code file, Engram immediately re-ingests the vector chunk to the manifold. Your contextual window never decays into staleness.Tiered Autophagy GC: Every hour, a deep-asynchronous Tokio thread wakes up and scans your memory manifold. Irrelevant ephemeral states automatically log-decay (2% for 24h stale, 5% for 7d stale). If a geometric block drops below
0.05 CRS(Coherence-Reliability Score), it is permanently evicted from the NVMe disk to clear room for new vectors.Project Matrix Pinning: Using the
mcp_engram_pinormcp_engram_remember_solutiontools, a connecting LLM can permanently bind critical Task Boards, PR Specs, or Bug Fixes to a perfect1.0 CRS. The Autophagy Daemon is hardcoded to never decay pinned invariants.
⚡ The Semantic Ray-Tracer & NVSA Reasoning
Because Engram uses Vector Symbolic Architectures inside the core math engine, you and your agents are capable of performing complex geometrical operations before extracting memory.
Engram native operators strictly adhere to the Monad CodeLand NVSA specification:
op_deduce: Physically trace logical implication constraints ($A \rightarrow B$).op_attend: Massively attenuate dimensions without tearing the hologram.op_is_symbolic_of: Avoid logic freezes by hoisting paradoxes into ZADO-CPS conformal toroidal embedding.op_geometric_product: Computes cosine similarities alongside orthogonal dimensions simultaneously using the Clifford ansatz.
Instead of hunting for keywords, you can mathematically bind, superpose, and intersect concepts across the hyperdimensional plane using the Trace commands:
# Locate the precise `.rs` chunks where native "CUDA" overlaps contextually with "Memory"
engram-cli trace "cuda" BIND "memory"
# Find code blocks that share equivalence between two combined domains
engram-cli trace "geometric" ADD "tensor"These logophysical math routes are available locally over CLI, or explicitly exposed to AI integrations over the robust /api/trace Axum REST route!
💾 Engineering Limitations: NVMe O_DIRECT Block Rules
If you are modifying the engram-core serialization pipelines, strictly adhere to the 256KB block rules.
Every piece of knowledge is stamped into fundamentally isolated HolographicBlocks (.leg files). We designed these logical containers to be exactly 262,144 bytes (256KB) in memory space.
This is not an arbitrary limitation.
The exact 256KB payload was specifically optimized for O_DIRECT physical SSD alignments. This ensures that geometrical tensors can completely bypass standard Operating System CPU buffer-caches, and be Direct Memory Access (DMA) streamed off of M.2 NVMe drives directly into GPU VRAM for CUDA or ROCm kernel processing.
If you alter the struct geometry in types.rs so that it no longer aligns evenly to modern block bounds, you will break the underlying DMA speeds!
⚡ Quick Start integration
Integration configs for all supported IDEs are openly tracked in
integrations/
Install
cargo install engram --git https://github.com/staticroostermedia-arch/engramGoogle Antigravity IDE
Engram ships a ready-to-use config for Google Antigravity IDE. Add to ~/.gemini/antigravity/mcp_config.json:
{
"mcpServers": {
"engram": {
"command": "engram",
"args": ["mcp", "--store", "~/.engram/manifold"],
"disabled": false
}
}
}Claude Desktop Integration
Add to ~/.config/claude-desktop/claude_desktop_config.json:
{
"mcpServers": {
"engram": {
"command": "engram",
"args": ["mcp", "--store", "~/.engram/manifold"]
}
}
}Restart Claude Desktop. You immediately tap into the native tools: remember, recall, forget, list_concepts, mcp_engram_watch_workspace, mcp_engram_pin, mcp_engram_relate, mcp_engram_context_for_file, and mcp_engram_remember_solution.
💻 CLI Operations & Manifold Bootstrapping
If you're bringing Engram into a legacy repository, you do not need to manually parse your code logs. Just utilize the native recursive chunking engine:
# Bootstrap an entire monolithic repository into geometric logic inside of seconds:
engram-cli ingest /path/to/monolithic-workspace --chunk-size 8000
# Store single ad-hoc memories:
engram-cli remember krebs_cycle "The Krebs cycle converts acetyl-CoA to ATP via 8 enzymatic steps"
# Interrogate memory conceptually:
engram-cli recall "how does cellular respiration produce energy"
# Prints exactly the Krebs Cycle vector, and exact code lines tied to that phase domain.Hardware Support
Engram maps identically across the top hardware architectures natively:
Backend | Flag | Status | Notes |
CPU (Rayon) | Default | ✅ v1.0 | Uses B=4 TurboQuant Codebook for 4x accelerated K-NN bounds |
CUDA (NVIDIA) |
| ✅ v2.0 | BVH O(log N) index, NVMe parallel kernel computation |
ROCm (AMD) |
| ✅ v2.0 | Wavefront HIP execution |
Metal (Apple) |
| ✅ v1.0 | macOS MSL dynamic runtime compilation via metal-rs |
License & Patent
This software is licensed under AGPL-3.0-only.
The .LEG container format is covered by U.S. Patent Application No. 19/372,256 (pending),
Self-Contained Variable File System (.LEG Container Format),
Applicant: Aric Goodman, Oregon, USA — Static Rooster Media.
This is a reference implementation. Commercial licenses (including for SaaS/cloud use) are available.
Contact: StaticRoosterMedia@gmail.com
See PATENT-NOTICE.md for full details.
Latest Blog Posts
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/staticroostermedia-arch/engram'
If you have feedback or need assistance with the MCP directory API, please join our Discord server