Mímisbrunnr · the well of memory

Branch any audit point.Recover any client to a known-good state.No detail is ever overwritten.

Self-hosted on your VPS. Your data never leaves your tenant.

Ed25519-signed · bitemporal · replay-byte-identical · EU AI Act article 12

Type-checked. AST-gated. Schema-validated. The deterministic guard rails most agent stacks skip.

descend

I · The well of memory

In the old stories, Odin sacrificed an eye to drink from Mímisbrunnr — Mimir's well.

Today, the well has new water. Every action your agents take, every read, every write, every halt — sealed in a tamper-evident chain at the root of the World Tree, retrievable forever. Mimir is the supervisor that lives on your VPS. He spawns specialist agents on demand, learns from their work, and lets you replay or branch any decision they ever made.

You supervise Mimir. Mimir supervises the team.

II · Three runes

Three things only Mimir can do.

BRANCH

Fork any audit point at datom granularity. Try a different decision in a parallel timeline; commit only the branch that wins.

$ mimir branch \
  --agent watcher-7af1 \
  --from chain://event-1247

REPLAY

Re-execute any decision deterministically. Intervene at any step. Watch the trajectory change exactly where you change it.

$ mimir replay \
  --agent watcher-7af1 \
  --from chain://event-1247 \
  --intervene tool=write_file

EXPORT

Produce an EU AI Act Article 12 evidence package signed end-to-end with Ed25519. Hand it to the regulator. They can verify it without you.

$ mimir export \
  --format=eu-ai-act \
  --from 2026-05-01 \
  --to 2026-08-01

branch · replay — try it

illustration — not a live runtime

chain://watcher-7af1 · Ed25519-signed

↑ click any datom to fork a parallel timeline from it

OpenClaw (368K stars) ships event-sourced replay and snapshot persistence — but no Ed25519 audit chain, no bitemporal model, no fork with byte-identity. Hermes-agent (Nous Research, 129K stars) supports only /undo. Letta, Mem0, and AnythingLLM have memory but no audit chain. Cursor, Cline, and Aider have neither.

vs Nono

Nono signs executions of arbitrary binaries; Mimir signs the plan AST and the datoms it produces, with replay-byte-identity. Plan-as-data, not binary-identity.

vs DBOS

DBOS forks workflows from Postgres checkpoints; Mimir forks the fact ledger itself with per-branch child-txn rollback at datom granularity. Datalog query over forked state, not re-execution.

vs Microsoft AGT / OrgKernel

These ship audit chains as a service (FastAPI, REST). Mimir ships it as a library with curated SDK, no infrastructure to operate.

III · The six branches

How Mimir holds his fleet.

01

Spawns specialists.

mimir spawn --tier SAFE creates a child agent under your authority with bounded skills, a vault tier, and a capability token.

02

Trains them from their audit logs.

Successful patterns are distilled into reusable skills, gated by replay byte-identity, audit-chain integrity, score delta, and stub coverage.

03

Coordinates them via STM.

Children sharing state commit atomically — either both ship or neither does. Software-transactional memory at the substrate.

04

Forks-and-votes when uncertain.

Spawn N children to try N approaches. Score them. Commit only the winner. The N−1 losing branches leave zero trace.

05

Filters every read by tier.

PUBLIC, SAFE, SENSITIVE, PII — capability tokens enforced server-side. A SAFE-tier child literally cannot read PII, even if it tries.

06

Audits everything end-to-end.

Every spawn, every read, every write, every halt — one Ed25519-signed datom in a Merkle-chained log spanning the whole fleet.

IV · The trunk

The substrate makes durability possible.

Mimir is built on persistence-os — a bitemporal, effect-typed substrate where every fact is an immutable datom, every action is an effect, every plan is an EDN AST, every shared state change is a transaction, every LLM boundary has a spec, and everything is REPL-live.

Open-core under AGPL-3. Substrate completion shipped at v0.8.5a1 with 2135 tests passing.

Substrate on GitHub →

well

Mímisbrunnr — Mimir the supervisor, running on your VPS

Tap any part of the tree to read what it is.

V · Drink at the well

Pricing.

The OSS tier is the funnel. The Compliance tier funds the development. Everyone drinks from the same well.

SELF-HOSTED

FreeApache 2.0

Everything below. Run the Docker image on your VPS or laptop. Forever.

MIMIR PRO

$29/mo · for one operator

Hosted Ed25519 retention (90d), email support, multi-device sync, web UI.

MIMIR TEAM

$199/mo · 5 seats

Shared memory graph, RBAC, team audit dashboard, 1y retention.

EU AI ACT COMPLIANCE

$2,500/mo · per regulated entity

EU residency, ISO mapping, expert-witness export, dedicated tenant, SLAs, SSO.

VI · The install

Drink from the well.

Once v0.1.0 ships, paste this into Claude Code. It will provision Mimir on your VPS, mint your Ed25519 keys, wire your MCP, and start the agent loop. 90 seconds, end to end.

claude> /mimir install

Alpha targets July 2026. Tell me where to send the install command.

One email when alpha ships. No newsletter.