Mnemovela-open 3.0.0

v3.0.0

Released 2026-10-17 as part of the PRAXOVELA 3.0 platform line.

• All axisvela Go module paths now end in /v3; this repository's public
  module tag is v3.0.0 (or <subdir>/v3.0.0 where the module lives in a
  subdirectory).
• Old pre-/v3 import paths are not maintained.
• npm packages are under @axisvela/*.

See the core release for the full highlights, the authoritative 2026-10-12
compatibility matrix and the deferred post-3.0 items:

https://github.com/axisvela/praxovela/releases/tag/v3.0.0

v1.2.0

Mnemovela v1.2.0 Release Notes

Version: v1.2.0
Date: 2026-08-22
Status: Stable (1.2)

Summary

v1.2.0 is the second feature minor on the v1.0 stable line. It ships Hybrid
MemorySpace P4 (bidirectional mirroring — the final Hybrid phase) and the
HARMOVELA dispatch-swap (configurable OperationDispatcher routing that
makes the EE HARMOVELA bridge actually serve Search/BuildContext). Zero
breaking changes to stable contracts.

Features

• Hybrid MemorySpace P4 (bidirectional mirroring) — sync.pull_branch
  (shared→local reverse link), sync.sync_bidirectional (one-shot pull+push
  mirror), projection rebuild for ingested/pulled commits
  (engine.index_commit), and a disclosure decision log in
  outbox/sync_status. Round-trip dedup and pre-apply conflict detection fix
  fast-forward and duplicate-mirror edge cases. Closes the final Hybrid phase;
  EE 1.0 code gates met.
• HARMOVELA dispatch-swap — httpserver.Options.Dispatcher and JSON-RPC
  HandleJSONRPCWithDispatcher/DecodeAndHandleJSONRPCWithDispatcher route
  Search/BuildContext through the OperationDispatcher seam when configured
  (nil = runtime-direct, OSS unchanged). The EE server wires the HARMOVELA
  bridge behind Mnemovela_HARMOVELA_BASE_URL, so coordinated deployments can
  serve memory operations over the Harmovela event surface.
• Release tooling fix — publish_release.ps1 uses platform-prefixed asset
  names + the correct uploads.github.com URL (open releases now carry all 4
  platform binaries).

Quality & CI

• Quality harness 117/117 under --fail-on all; gate on for every push.
• Python core 527 tests, Go 8+ packages (incl. HTTP/JSON-RPC dispatcher tests),
  Web 32 specs + e2e smoke — all green.
• Capability matrix --check no drift.

Tags

• v1.2.0 — repository release tag (core + open share the same tag).

---

Prebuilt Mnemovela embedded server binaries for v1.2.0.

• mnemovela-http: JSON-RPC-over-HTTP + REST
• mnemovela-grpc: gRPC
• mnemovela-jsonrpc-stdio: JSON-RPC over stdio
• mnemovela-mcp-stdio: MCP server over stdio

Built with CGO_ENABLED=0, embedded backends only.

Platforms: windows/amd64, linux/amd64, darwin/amd64, darwin/arm64.

Assets are named -- (e.g. mnemovela-http-linux-amd64); checksums--.txt per platform.

See BINARY-LICENSE.md for distribution terms.

v1.1.0

Mnemovela v1.1.0 Release Notes

Version: v1.1.0
Date: 2026-08-22
Status: Stable (1.1)

Summary

v1.1.0 is the first feature minor on the v1.0.0 stable line — it ships the
Hybrid MemorySpace P2 (Policy V2 disclosure gate + redaction seam) and P3
(multi-writer conflict detection, advisory) in the OSS core, plus roadmap/status
reconciliation. Zero breaking changes to stable contracts.

Features

• Hybrid MemorySpace P2 — sync.outbox now applies a Policy V2
  subject-boundary disclosure gate (authorizer= param) and a non-destructive
  redaction seam (_redact): strips metadata.redact fields and PII-bearing
  payload values while keeping commit_id; non-list redact metadata is
  fail-safe ignored. Default (no authorizer) preserves P1 behavior.
• Hybrid MemorySpace P3 — sync.detect_conflicts detects same-parent
  divergence on shared branches and suggests an advisory supersede/refute
  revision relation, surfaced as sync_status.pending_conflicts. Clean
  fast-forwards (remote strictly ahead) are not flagged; registry handling
  tolerates scope-string entries and clears stale conflicts.
• EE 1.0 gate roadmap update — HARMOVELA integration is an EE 1.0
  prerequisite (adapter implemented in Mnemovela-EE/go/server/harmovela/);
  B2 PGQ and the enterprise production track record move post-1.0;
  Hybrid P4 remains an EE 1.0 gate.

Quality & CI

• Quality harness 117/117 under --fail-on all; gate on for every push.
• Python core 518 tests, Python REST 49 tests, Go 8 packages, Web 32 specs +
  e2e smoke — all green.
• Capability matrix --check no drift.

Tags

• v1.1.0 — repository release tag (core + open share the same tag).

---

Prebuilt Mnemovela embedded server binaries for v1.1.0.

• mnemovela-http: JSON-RPC-over-HTTP + REST
• mnemovela-grpc: gRPC
• mnemovela-jsonrpc-stdio: JSON-RPC over stdio
• mnemovela-mcp-stdio: MCP server over stdio

Built with CGO_ENABLED=0, embedded backends only.

Platforms: windows/amd64, linux/amd64, darwin/amd64, darwin/arm64.

See BINARY-LICENSE.md for distribution terms.

---

Binaries: assets are named -- (e.g. mnemovela-http-linux-amd64, mnemovela-http-windows-amd64.exe); checksums--.txt per platform. Platforms: windows/amd64, linux/amd64, darwin/amd64, darwin/arm64. Built with CGO_ENABLED=0, embedded backends only. See BINARY-LICENSE.md for distribution terms.

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:

1. Sustained post-freeze use — two consecutive zero-breaking minors
   (v0.14.0 + v0.15.0); interface frozen since v0.13.0.
2. Web beta → stable — interface freeze audit re-verified zero churn
   (2026-08-21): every routed surface + atlas view targets mnemovela.rest.v1,
   ng test 32/32, live-backend e2e smoke 4/4, no blocking TODO/any.
3. gRPC surface parity — lifecycle, legal-hold, and Policy V2 CRUD RPCs
   shipped as non-breaking additions on the core Mnemovela service.
4. Quality harness — 117/117 green under --fail-on all, gate on for every
   push.
5. 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 to v1.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 --check no drift.

Tags

• v1.0.0 — repository release tag (core + open share the same tag).

v0.15.0

Mnemovela v0.15.0 Release Notes

Version: v0.15.0
Date: 2026-08-21
Status: Release Candidate (pre-stable)

Summary

v0.15.0 is the second consecutive post-freeze feature minor on the
v0.13.0-frozen contract baseline. It ships Hybrid MemorySpace P1 (the first
EE 1.0 B-track code delivery in the OSS core), the closure of the context.v2
RFC as implemented, and roadmap/status corrections. No breaking changes to
stable contracts.

Features

• Hybrid MemorySpace P1 (python/src/axisrobo/mnemovela/sync.py,
  tests/test_sync_hybrid.py): single-writer fast-forward sync outbox/ingest
  for shared branches — declare_shared_branch / outbox(since_sequence) /
  ingest(commits) / sync_status() with a disclosure filter (self scope
  never syncs) and idempotent ingest keyed by source commit_id. P1 is the
  first phase of the EE 1.0 gate E4; P2–P4 (policy disclosure gate, multi-writer
  conflict workflow, bidirectional mirroring) remain design intent
  (docs/architecture/hybrid-memoryspace.md, Status: Implemented P1).
• RFC closure: the context.v2 breaking-change RFC
  (2026-08-21-context-v2-remove-deprecated-derived-fields)
  is marked implemented (shipped in v0.14.0); governance evidence for core
  1.0 gate 5.

Docs & Governance

• docs/status-and-roadmap.md and docs/mnemovela-master-roadmap.md corrected
  to record Hybrid MemorySpace P1 as implemented (P2–P4 remaining); stale
  "Status: Designed" references removed.
• Capability matrix regenerated with the Hybrid MemorySpace sync (P1) row
  (py -3.13 scripts/capability_matrix.py --generate; --check clean).

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 --check no drift.

Tags

• v0.15.0 — repository release tag (core + open share the same tag).

v0.14.0

Mnemovela-open v0.14.0 - mirrors core v0.14.0 (context.v2 dual-version contract, task queue).

v0.13.3

Mnemovela-open v0.13.3 - mirrors core v0.13.3: PolicyV2 gRPC RPCs + regenerated Go/Python client stubs, updated grpc.md API reference.

Mnemovela-open v0.13.2

Open mirror sync of Mnemovela v0.13.2 (Mneme -> Mnemovela rename, contract freeze, clients).