Repository navigation
v1.0.0
Mnemovela v1.0.0 Release Notes
Version: v1.0.0
Date: 2026-08-21
Status: Stable (1.0)
Summary
v1.0.0 declares the core Mnemovela 1.0 on the quality-and-track-record gate
(docs/status-and-roadmap.md § Path to 1.0), not a calendar date. The core has
held the frozen contract baseline through two consecutive post-freeze
zero-breaking feature minors (v0.14.0 with dual-version context.v2,
v0.15.0 with Hybrid MemorySpace P1), with all five core 1.0 gates met:
- Sustained post-freeze use — two consecutive zero-breaking minors
(v0.14.0+v0.15.0); interface frozen sincev0.13.0. - Web beta → stable — interface freeze audit re-verified zero churn
(2026-08-21): every routed surface + atlas view targetsmnemovela.rest.v1,
ng test32/32, live-backend e2e smoke 4/4, no blocking TODO/any. - gRPC surface parity — lifecycle, legal-hold, and Policy V2 CRUD RPCs
shipped as non-breaking additions on the coreMnemovelaservice. - Quality harness — 117/117 green under
--fail-on all, gate on for every
push. - RFC + dual-version governance — exercised end-to-end via the
context.v2
breaking-change RFC (proposal → RFC → dual-version → closure).
The Mnemovela-open mirror ships the same v1.0.0 tag (client SDKs follow the
core contract; SDK stability audit, mirror-sync automation, and first-party
adoption evidence recorded).
Release content since v0.15.0
- v1.0.0 declaration — no code/contract changes; the release records the
sustained-track-record evidence for the 1.0 declaration and bumps the
capability matrix tov1.0.0.
Quality & CI
- Quality harness 117/117 under
--fail-on all; gate on for every push. - Python core 504 tests, Python REST 49 tests, Go 8 packages, Web 32 specs +
e2e smoke — all green. - Capability matrix
--checkno drift.
Tags
v1.0.0— repository release tag (core + open share the same tag).