Keep device identity separate from memory relevance.
ADR-044 · source bound · current01THE PRODUCT
Your own memory server.
On your own hardware.
Mnemes is self-hosted software: a personal Rust agent-memory server above semantic-memory and semantic-memory-mcp. Install it on hardware you already own to add device identity, routed cross-device search, server-side memory copies, and one operator-controlled boundary.
mnemes v0.1.1 sourcecontinuous replication in development
01 / THREE DEPLOYMENT PATHS
Mnemes is the server.
Node R1 is optional.
One device can use the same semantic-memory engine through Agent Memory Kits. Mnemes adds the server and multi-device layer. Node R1 simply arrives assembled.
self-hosted
YOUR HARDWARE
Mnemes server
Run your own personal agent memory server on Linux hardware you already own. Mnemes adds device and actor identity, per-device server shards, routed witnessed search, and one operator-controlled place for your agents to remember together.
WHAT THIS PATH KEEPS
- Your hardware, storage, and network boundary
- Multiple authorized agents and devices
- Server-side memory copies with source identity
BOUNDARY
Current source supports server-side per-device shards. Continuous device-owned replication and fully proven recovery remain in development.
02 / THE CORE IDEA
Local-first does not have
to mean device-isolated.
A laptop, server, edge node, and phone can contribute different kinds of memory without collapsing into one anonymous vector pile. Identity and authority filter the search before relevance gets a vote.
ΜMnemespooled.db + server shards
scope
receipt
QUERY ORIGIN · LAPTOP
“What did we decide about the memory authority—and what evidence survived?”
The edge service restarted cleanly after the watchdog event.
receipt 8f2… · source bound · currentExact f32 rerank remained the deciding stage.
run-1842 · source bound · currentSOURCE-ESTABLISHED
Current source implements server-side per-device shards and routed witnessed search.
Authorization filters eligible shards before semantic ranking begins.
A tailnet can connect devices. It does not prove replication, freshness, merge, or replay.
Results should disclose origin, owner, replica freshness, temporal state, and route evidence.
03 / OPTIONAL PHYSICAL EDITION
Mnemes Node R1.
The convenience path.
The same Mnemes server can be installed on your own hardware. Node R1 is an early custom-build option for people who want it preconfigured with Hermes, bounded onboard AI, visible status, and portable-power hardware.
A working personal deployment is reported
The founder reports Mnemes, display behavior, and small-model utility work active on the personal UNO Q deployment. This is not an independent hardware certification.
Productization is early
Enclosure, first-connection flow, battery selection, endurance, repeatability, price, and availability remain open gates.
04 / TWO DATABASE RESPONSIBILITIES
Add control metadata.
Do not duplicate truth.
Mnemes owns pooling and routing metadata. Semantic-memory continues to own every memory payload and its retrieval semantics.
pooled.dbControl plane
- devices identity, status, credentials
- actors human, agent, service, process
- operations idempotent envelopes
- provenance typed bitemporal edges
- routing selected, skipped, fallback
routes and witnesses
memory.db × NDevice shards
laptop.memory.dbfacts · chunks · graph · receiptsserver.memory.dbfacts · chunks · graph · receiptsedge.memory.dbfacts · chunks · graph · receiptsphone.memory.dbfacts · chunks · graph · receipts
05 / OPERATION LIFECYCLE
Every material step
keeps its identity.
The lifecycle preserves who requested an operation, which device recorded it, what content digest was accepted, when it was valid, and when the server recorded it.
Enroll
Register a device and actor with explicit identity. Unknown credentials fail closed.
Capture
Write a typed operation envelope with source, actor, valid time, content digest, and idempotency key.
Route
Filter eligible shards, rank by sparse overlap and locality, select within budget, and record the decision.
Retrieve
Search selected semantic-memory shards, merge by score, deduplicate by item identity, and reject content conflict.
Witness
Return source identity, temporal state, route evidence, retrieval evidence, fallback, and degradation.
Revoke
Rotate, quarantine, or revoke device authority without pretending old reachability grants current access.
06 / OPERATOR SURFACE
HTTP, MCP,
and an admin boundary.
The loopback server exposes health, integrity, device lifecycle, actors, operations, witnessed search, sync, receipts, audit events, and MCP JSON-RPC behind device credentials.
GET /livezGET /healthzGET /v1/healthGET /v1/integrityPOST /v1/devices/registerPOST /v1/devices/:id/rotatePOST /v1/devices/:id/revokePOST /v1/devices/:id/quarantinePOST /v1/search/witnessedPOST /v1/syncGET /v1/receipts/:idGET /v1/audit/eventsRead-only daily surface
Search, facts, graph paths, namespaces, authority decisions, receipts, and replay. No device management.
Explicit operational surface
Device and actor registration, operation submission, heartbeat, rotation, revocation, and quarantine.
07 / CURRENT TRUTH
Three states.
No blended claim.
Architecture prose is not allowed to borrow proof from a different plane. The current source boundary remains visible here and throughout the site.
Current candidate
Per-device server shards, control metadata, routed witnessed search, route receipts, bearer-token admission, and device lifecycle endpoints exist in public source.
Edge node
An ARM64 edge deployment is reported in the supplied context. That observation does not certify recovery, security, or cross-device convergence.
Device-owned replicas
Canonical databases on home devices with continuous signed replication, freshness proof, offline backlog, conflict law, and recovery still require end-to-end canaries.