Run the daemon, connect an MCP client, and make the first bounded call.
Documentation control plane · reviewed 15 July 2026
Memory that can
explain itself.
MemoryCrux is not one database and it is not one magic trust claim. It is a local memory engine, a bounded retrieval surface, an identity and receipt model, and an optional hosted fleet layer. This map keeps those boundaries visible.
Memory lifecycle
From source material to an inspectable decision record.
Facts, freshness, sessions, handoffs and compiled organisational knowledge.
BM25, token budgets, evidence-aware retrieval and reproducible benchmarks.
Receipts, passports, constraints, capability gates and honest trust boundaries.
Configuration, troubleshooting, releases, upgrades and executable assurance.
Source ownership
Five surfaces, five different kinds of truth.
positioning truthcontract truthruntime truthfleet truthmeasurement truthMaintained catalogue
Choose the job in front of you.
Install & connect
Run the daemon, connect an MCP client, and make the first bounded call.
Install Crux and mint the first receipt
Go from a clean machine to the local console, MCP endpoint and a tamper-checkable receipt.
Explore MemoryCrux
A feature-first tour of facts, decisions, constraints, sessions, plans and the operator console.
How the data path works
Follow content from ingest through indexing and bounded retrieval to MCP clients.
Agent operating prompt
Recommended retrieval, memory, session, coordination and observability calls for an MCP client.
Hosted fleet memory
Understand what Pro and Governance add without implying that local custody requires a subscription.
Memory & continuity
Facts, freshness, sessions, handoffs and compiled organisational knowledge.
Versioned facts that age visibly
Store provenance-bearing facts with freshness horizons, supersession and deterministic decay.
Sessions and crash recovery
Persist structured state, resume after compaction and retain the anchors needed to continue an ExecPlan.
Handoffs and live coordination
Move bounded state between agents and coordinate concurrent work without treating advisory intent as a lock.
Engrams: memory that compiles
Distil reusable, provenance-linked procedural knowledge and resolve it by declared intent and capability tier.
Scoped forget and custody
Understand deletion markers, export behaviour and the distinction between erasure evidence and destructive history rewriting.
Search & context
BM25, token budgets, evidence-aware retrieval and reproducible benchmarks.
BM25 retrieval under token budgets
Retrieve metadata and content inside an explicit token budget instead of flooding the model with top-K context.
Memory recall benchmark
Run the deterministic recall and stale-leak benchmark and inspect why both metrics matter.
Measured context efficiency
See the cited ScoreCrux evidence behind the scale and token-use claims used on this site.
HTTP API reference
Use the local HTTP surface when MCP is not the right transport, while preserving the same bounded retrieval model.
Capability-shaped MCP surface
Discover the current memory, retrieval, session, coordination and evidence tools exposed to a client.
Identity & evidence
Receipts, passports, constraints, capability gates and honest trust boundaries.
What a CROWN receipt proves
Receipts prove record integrity, signer and chain relationships; they do not prove that an agent decision was correct.
Session plans and invocation receipts
Inspect the capability graph, plan hash, receipt modes and the explicitly documented follow-up boundaries.
Passports and principal identity
Separate agent identity and reputation from the RCX capability token that authorises a specific route or data class.
Opt-in usage receipts
See the three-part consent gate, exact metadata fields and default no-egress posture.
Source-available licence boundary
Read the CCL v1.0 permitted uses, prohibited uses and time-delayed Apache 2.0 change licence.
Run & verify
Configuration, troubleshooting, releases, upgrades and executable assurance.
Operations reference
Configure bind addresses, ports, MCP, authentication, storage and the default no-phone-home posture.
Troubleshooting
Diagnose daemon readiness, MCP connectivity, indexes, authentication and store integrity.
Verify a release before running it
Check signatures and provenance before installing a daemon binary or container.
Update channels and rollback posture
Understand release notification, channel selection and the difference between awareness and automatic mutation.
Executable assurance map
Trace feature claims to unit, integration, protocol and browser tests rather than relying on marketing prose.
Site audit ledger
What changed, and why.
Seven product pages
The current narrative and proof graphics are retained; the new hub points each technical claim back to the code or guide that owns it.
Receipt language
“Every tool call is signed” is replaced with the implemented boundary: state mutations are receipted, and invocation coverage is capability-dependent.
Free-tier packaging
Platform and pricing now agree on the canonical up-to-10-agent local tier instead of contradicting each other.
Imports coming
The stale badge is replaced by the shipped local-folder ingest path and its provenance-preserving command.
Source ownership
MemoryCrux web, Crux protocol docs, runtime code, VaultCrux read-through and ScoreCrux evidence now have distinct authority boundaries.
The maintenance rule