01
control plane
—registry unavailablemnemes
- downloads · unavailable
- —
- stars · unavailable
- —
- GitHub activity
- unavailable
μνήμη / MEMORYLOCAL-FIRST AI INFRASTRUCTURE
Your agents
should remember
together.
Hermes Agent runs locally with Rust acceleration, persistent memory, and multi-agent graphs. Mnemes adds a self-hosted memory server with device identity, cross-device search, and replication — all on hardware you control.
DEVICE-AWARESQLITE-AUTHORITATIVEBITEMPORALRECEIPT-BEARING
DESCEND INTO THE SYSTEM
public source pulseLIVE WHERE AVAILABLE · FALLBACK JUL 16, 2026
02
agent protocol
v0.5.4snapshot Jul 16, 2026semantic-memory-mcp
- downloads · snapshot
- 167
- stars · unavailable
- —
- GitHub activity
- unavailable
03
memory engine
v0.5.11snapshot Jul 16, 2026semantic-memory
- downloads · snapshot
- 352
- stars · unavailable
- —
- GitHub activity
- unavailable
COMPLETE RECURSIVEINTELL PORTFOLIO
Open live portfolio →Every public repository and crate, plus the 97-package audited Library Atlas.
00 / THE PRODUCT
The product is software.
The hardware is your choice.
Mnemes runs as a personal server on hardware you already own. Node R1 is the ready-to-go option, not a requirement. If you only need one device, Agent Memory Kits and semantic-memory-mcp provide the same underlying memory engine without the Mnemes server layer.
00B / CHOOSE THE BOUNDARY
One device. Your server.
Or ready-to-go.
Memory quality comes from the semantic-memory engine. Mnemes adds the personal server, device identity, server-side memory copies, and cross-device routing. Node R1 adds convenience.
start here
ONE DEVICE
Agent Memory Kits
Install semantic-memory-mcp beside the agent you already use. Its memory stays on that machine and uses the same semantic-memory engine, hybrid retrieval, temporal state, provenance, and receipts.
WHAT THIS PATH KEEPS
- The same core memory and retrieval quality
- Local SQLite authority on your device
- Agent lifecycle integration through a host kit
BOUNDARY
No Mnemes server copy, cross-device routing, or server-side recovery layer. Nothing about the underlying memory engine is downgraded.
01 / THE COMPOUNDING CURVE
The first session is empty.
That is not the product.
The product is the curve: memory becoming more useful as durable decisions, evidence, corrections, and cross-device context accumulate.
quiet by design
The recall hook waits. Nothing invented.
context appears
Conventions and active work begin returning.
decisions compound
Prior failures and architecture stop repeating.
continuity emerges
Cross-session questions have sourced answers.
An agent that compounds
Decisions, corrections, conventions, failed approaches, and open questions survive the session boundary.
A memory that spans devices
Search authorized device shards from another machine without flattening origin, actor, time, or namespace.
An answer that brings evidence
Witnessed retrieval can return source identity and an execution receipt alongside the result.
A system the operator owns
SQLite remains the durable authority; models, indexes, and compressed candidates stay replaceable.
02 / THE PRIVATE MEMORY FABRIC
Ask one device
what another learned.
Explore the current server-shard architecture, then switch to the device-owned replication target. The status boundary changes with the diagram instead of hiding in a footnote.
ΜMnemespooled.db + server shards
scope
receipt
QUERY ORIGIN · LAPTOP
“What did we decide about the memory authority—and what evidence survived?”
Keep device identity separate from memory relevance.
ADR-044 · source bound · currentThe 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.
03 / OPTIONAL READY-TO-GO HARDWARE
A private memory server
you can pick up.
Mnemes Node R1 packages the same self-hostable server into an early built-to-order appliance for people who lack suitable hardware or prefer a configured system.
MNEMES NODER1 / PROTOTYPE
USB-C
BUILT ON ARDUINO UNO Q 4GB · INDEPENDENT RECURSIVEINTELL PROTOTYPE
Mnemes ready
The node shows memory-plane state without pretending network reachability proves synchronization.
SHARDS 04 ELIGIBLEROUTE RECEIPTS ONLAST CHECK 00:42
founder-reported prototype · July 2026
Explore Mnemes Node R1 →You do not need Node R1 to use Mnemes. Configuration, enclosure, onboarding, and measured endurance are still being productized.
04 / DENSE MEMORY IN MOTION
Find one current answer
inside 64,000 records.
Run the model. Watch lexical and semantic candidates activate, graph context expand, temporal conflicts resolve, and the final answer arrive with source and receipt identity.
Q
FTS5 / 428
DENSE / 612
GRAPH / 84
1,124 candidates → 12 current results
AGENT QUERYWITNESSED ANSWER
“What owns package identity now?”
BM25.76
dense.91
graph.64
3 older statements excludedcurrent head resolved
stack-ids owns canonical identity. Adapter-local identifiers were superseded after ADR-031.
Interactive capability model—not a benchmark. Counts illustrate a dense archive and do not report measured performance.
05 / ONE SYSTEM, THREE OWNERS
Server.
Protocol.
Engine.
Mnemes does not swallow the stack. Each crate owns one layer, and each layer has explicit refusal boundaries.
Personal memory server
Self-hosted device and actor identity, control metadata, routed shard search, operation envelopes, provenance edges, and routing receipts.
Agent-facing MCP server
Profiles bound the exposed tools. Agents can retrieve through stdio or loopback HTTP without automatically receiving mutation or administration.
Authoritative local memory
SQLite, FTS5, dense vectors, weighted RRF, temporal views, graph relationships, provenance, receipts, replay, integrity, and recovery.
06 / CLAIMS WITH EDGES
See the ambition.
Keep the boundary.
The site distinguishes what current source establishes, what has been observed on hardware, and what still needs end-to-end synchronization proof.
Self-hosted Mnemes server
Public Rust software for hardware you control, with device and actor identity, per-device server shards, routed witnessed search, idempotent operation envelopes, and durable routing receipts.
Semantic memory engine
SQLite-authoritative hybrid retrieval with temporal views, graph relationships, provenance, governed mutation, optional receipts, and explicit replay privacy.
Device-owned replication
The target design keeps canonical databases on their home devices and synchronizes replayable server replicas. Continuous replication is not yet a released claim.
THE RECEIPT LAWA receipt records observed execution evidence. It does not prove factual truth, correctness, security, authorization, or task success.
07 / FROM INTEREST TO FIRST RECALL
Start where you are.
Keep what compounds.
Use one device with an Agent Memory Kit, install Mnemes on your own server, or choose Node R1 when you want the system assembled.
FULL AGENT STACK
One command. Complete AI agent.
Install Hermes Agent with Rust acceleration, 70+ skills, agent hooks, and 5 MCP servers — all pre-configured. Starts with a single curl command.
Full Josh's setup: llm-pipeline, context-governor, poly-kv, semantic-memory, agent-graph, claim-ledger, cea-graph, pilot-bridge, 70+ skills, 12 hooks. Use --help to see all flags. Skips Rust wheels: --skip-rust. Minimal: omit --with-josh-setup.
PRODUCT
Mnemes, without the mythology haze.
Current architecture, target replication, trust boundaries, API surface, and device lifecycle.
ENTER PRODUCT →PROOFInterrogate how memory knows.
Dense retrieval, temporal resolution, receipts, evidence scopes, and public source status.
ENTER PROOF →PLATFORMSee every layer and owner.
Engine, MCP protocol, Mnemes control plane, host kits, compression, and adjacent trust primitives.
ENTER PLATFORM →PERSONMeet the engineer behind it.
Josh Stevenson, RecursiveIntell, the public portfolio, and bounded ways to work together.
ENTER PERSON →MNEMES / THE LIVING ARCHIVE
Memory should remember
how it knows.
Start with one agent on one device. Add your own Mnemes server when those memories should travel. Choose Node R1 only if you want the hardware handled too.