Research · Status

MEMA: versions, evidence, and release status.

A build can be implemented internally without being publicly available or cleared for production. This page keeps those boundaries visible.

§01 Current reconciliation

Four statements, four separate evidence lines.

Public repository

Package 2.22.13 · commit c37dbf7. Reproduced runtime run: 536 tests across 61 files with 1,361 expectations. The README's 538/63/1,362 claim is stale.

Internal build

v2.26.0 · commit d542fba · 25 commits ahead of c37dbf7 · locally verified · not public

Production readiness

Currently not asserted.

Roadmap

Customer-datacenter package, evidence export, and governed HOPE integration.

§02 Capability ledger

What is public, internal, experimental, or planned.

publicly inspectable

Seven-layer core and local data plane

The public repository contains episodes, facts and entities, cognitive records, governance, hybrid retrieval, an audit log, and asset metadata. Markdown is the primary record format; local SQLite files hold derived indexes and logs.

Evidence and boundary: Publicly inspectable in package 2.22.13 at c37dbf7. A reproduced runtime run produced 536 tests across 61 files with 1,361 expectations; the README's 538/63/1,362 claim is stale. This describes code surfaces, not production readiness.

publicly inspectable

LLM extraction on the write path

The public `/v2/observe` path calls an LLM extractor by default. Its automatic path stores filtered facts and entities directly as approved; separate draft/approve endpoints exist for other untrusted producers. This is external memory processing, not model-weight training.

Evidence and boundary: Public source at c37dbf7; this narrow wording corrects the earlier write-path description.

publicly inspectable

Targeted tombstoning with bounded deletion scope

The public baseline can tombstone selected primary records while the linked audit structure remains checkable. This does not establish complete deletion from derived indexes, caches, replicas, logs, or backups.

Evidence and boundary: Targeted tombstoning is publicly inspectable in source; a supported cascade across all derived data remains planned.

implemented internally

Internal v2.26 runtime baseline

Internal build d542fba has been locally verified as the v2.26 runtime. It is 25 commits ahead of c37dbf7. The website-rendered whitepaper is an editorial derivative and is not byte-identical to the immutable artifact at d542fba.

Evidence and boundary: Implemented and verified internally; not publicly available. Immutable whitepaper artifact: d542fba:docs/WHITEPAPER.md, SHA-256 62a9bda1…b563bd.

experimental

LLM-augmented reflection

An optional LLM reflection pass augments the rule-based pass. It remains an opt-in research mode; it does not imply model adaptation or production readiness.

Evidence and boundary: A code surface exists; operating boundaries and deployment evidence remain context-dependent.

planned

Customer-datacenter operations package

Target state: runtime, vault, keys, backups, updates, and monitoring under customer control, with no mandatory MEMA cloud. A supported HA, backup, and upgrade package is not yet publicly verified.

Evidence and boundary: Roadmap, not a shipped product offer.

planned

Exportable evidence bundle

The plan is a customer-verifiable bundle of selected records, hashes, policy decisions, and audit excerpts. Public code exposes local asset and audit surfaces, but not yet a supported external bundle export.

Evidence and boundary: Roadmap; a local anchor receipt is not an independent export.

planned

Governed HOPE integration

The proposal is an evidence and control plane around future model-internal continual-learning modules. Neither the public nor the internal MEMA baseline contains a HOPE runtime today.

Evidence and boundary: Architecture proposal; no implemented integration.

not asserted

Production readiness

This website currently makes no production-readiness assertion. Such a release requires public source parity plus current independent security, operations, and recovery evidence.

Evidence and boundary: Not asserted.

§03 Release note

There is no public v2.26 release.

The immutable v2.26 whitepaper artifact exists at internal commit d542fba. The text rendered on this website is an editorial derivative reconciled on 2026-08-26 and is not byte-identical to that artifact. Public origin/main remains at 2.22.13/c37dbf7. Before a public release note, source, package version, changelog, and website must all point to the same commit baseline.

§04 Document provenance

The artifact and web edition are separate objects.

The values below identify the immutable whitepaper in the internal Git object store. No public artifact link is presented. They enable a future byte-level check if publication receives separate approval.

Rendered website edition
Editorial derivative · reconciled 2026-08-26 · not byte-identical
Artifact edition
2.26.0 · 2026-07-21
Full commit
d542fba556a7d4d78094ec782277eda18c79cb18
Repository path
docs/WHITEPAPER.md
Git blob
f12fa1da06ada3bbcdb3a729f71f19ce14a6f1d4
SHA-256
62a9bda13f4f083ff45866f3a34df82453107904815ffc3b9c58304f61b563bd
Byte length
51,063
Lines
972
Public availability
No. The source commit, runtime, and artifact are not publicly available.

Horizontally scrollable content. Use the Left and Right Arrow keys to view all content.