MemoryWell
State Runtime for AI Systems
MemoryWell gives developers deterministic control over AI reasoning state across stateless LLM boundaries. State that would otherwise be reconstructed probabilistically each session is instead governed, validated, and resumed exactly.
Memory storage, semantic recall, and session continuity are components inside that runtime — not the runtime itself. The runtime is the lifecycle. The lifecycle is the product.
The fastest way to understand MW is to run the Hello World continuity demo.
The Lifecycle
If this loop works reliably, the idea is proven. Every component exists. Every boundary is tested.
Wake
Load the last known state snapshot. The AI resumes exactly where it left off — no inference, no guessing.
Reconstruct
Rebuild the full working context from the snapshot. Deterministic. Not probabilistic recall.
Work
The AI reasons. Context is live. State is intact. The session proceeds.
Guard
Every proposed state mutation is validated before it commits. Invalid state cannot enter the system.
Commit
Only the delta is recorded — not a full copy. State grows incrementally. Context window stays clean.
Sleep
Formal session closure. Snapshot pointer updated. Next Wake has everything it needs. Session terminates cleanly.
The Irreducible Core (MVIM)
Remove any of these five components and MemoryWell ceases to be MemoryWell.
State Snapshot
Without this, there is nothing to reconstruct.
Wake / Reconstruction Protocol
Without this, continuity breaks at every session boundary.
Guard Layer
Without guardrails, continuity becomes corruption.
State Commit / Delta Recording
Without controlled commit, state cannot evolve safely.
Sleep / Handover
Without formal closure, state continuity collapses between sessions.
All five are implemented and battle-tested across 14 production validation stages.
The Failure Map
Feature lists show what a system does. Failure maps show how it survives reality.
Most systems fail silently. MW cannot — state integrity is a first-class invariant.
The MemoryWell Guarantee
MW does not guarantee that AI reasoning is correct — that's impossible.
What it guarantees: the reasoning state itself remains coherent, reconstructible, and auditable.
That is the infrastructure primitive.
The API Surface
These endpoints expose the MW lifecycle through a simple developer surface. Internally they map to the wake, guard, commit, and snapshot protocols.
POST with JSON body. Bearer token auth. Same pattern across all four.
mwStoreMemory
Persist a state delta or memory. Async-queued, deduplicated, idempotent.
mwRecallMemory
Retrieve a specific memory by ID or key. Full content included.
mwSearchMemories
Semantic search. Natural language query against your full state history.
mwListMemories
List memories by tier and time. Lightweight — no full content.
What It's Proven With
14
Production stages
0
Cross-tenant leaks
0
Entropy events
100%
Chaos tests passing
Stage 11 — Soak + Chaos
1000-op soak, worker restart, Redis flush, burst spike, duplicate storm. All PASS.
Stage 12 — Security + DR
Cross-tenant isolation, export integrity, restore, right-to-delete. All PASS.
Stage 14 — Tenant Simulation
20 tenants × 100 ops. Zero cross-tenant bleed. Zero job corruption. Production-ready.
Ready to go deeper?
The BetaKit has your API key, curl examples, golden path code, and full error reference.