Mneme

Highlights

The load-bearing wall of the differentiation per ARCHITECTURE.md §4. Two Mneme instances now converge to identical state via any transport implementing the SyncPeer interface.

import { Mneme } from '@mneme/sdk'

const alice = new Mneme({ path: '/path/to/alice.sqlite', ownerId: 'pedro' })
const bob = new Mneme({ path: '/path/to/bob.sqlite', ownerId: 'pedro' })

await alice.remember({ kind: 'fact', body: 'london resident' })
await bob.remember({ kind: 'preference', body: 'prefers concise reviews' })

const result = await alice.sync(bob.asPeer())
// → { pushed: 1, pulled: 1, merged: 0 }

• Deterministic CRDT merge on the tiny lifecycle envelope: supersededBy → latest target createdAt wins (both replacements kept); expiresAt / forgetAt → earliest wins (strictest constraint honoured).
• Commutative, associative, idempotent. Re-running sync is a no-op.
• Transport-agnostic. SyncPeer is three methods (catalog, fetch, push). v0.0.6 ships InProcessSyncPeer; WebSocket / HTTP / hosted Cloud implement the same three methods in later versions and the engine doesn't change.
• ADR 0008 captures the eight design choices — written before the code per CLAUDE.md operating procedure.

What's in the repo today

• packages/protocol v0.0.1 — open spec types
• packages/sdk v0.0.6 — encryption + recovery + signing + sync engine
• packages/embedder-local v0.0.1 — on-device embeddings
• apps/mcp-server v0.0.1 — Claude Code-installable MCP server
• tests/conformance v0.0.1 — cross-implementation suite
• docs/protocol/v0.1.md — public wire spec
• decisions/ — 8 ADRs

What's deliberately deferred

• Multi-device pairing ceremony — v0.0.7 (ADR 0009)
• WebSocket transport for cross-machine sync — v0.0.7
• Hosted Mneme Cloud sync target (apps/api) — v0.1.0
• Incremental sync (catalog cursor for > 10K records) — v0.0.7
• Signature verification at the sync boundary — v0.0.8+ when cross-key sync exists

Try it

git clone https://github.com/ppserapiao/mneme
cd mneme
bun install
bun test    # 94 pass, 2 skip