How Mneia works, and how to run it.

$ mneia brief "migrate the ledger writes to v2"

CONSTRAINTS (2 active, human-confirmed)
  · No downtime window; the cutover must be online
  · Ledger writes stay idempotent under retry

SUPERSEDED (do not re-propose)
  · Read from the shadow table in the worker
    → replaced by: read from v2 directly

14 items considered · 6 included · 1,840 tokens · 96ms

Mneia is in staged early access. Everything documented about the command surface and the tool surface is built and behaves as described. The client packages are not on npm yet, so the install steps describe what happens when your account is enabled rather than something you can run today.

Start here

• QuickstartInstall, authenticate, bind a repository, connect an MCP client, and run the loop end to end.8 min read
• ConceptsItem kinds, provenance, superseding, and how a rehydration slice is actually chosen.9 min read
• CLIEvery command and flag, the environment variables, the JSON contract, and the exit codes.7 min read
• MCP serverThe four tools your agent can call, how to configure the server, and how failures come back.7 min read

The three operations

Everything in these pages serves one of three operations. Checkpoint captures the decisions, constraints, and open questions out of a session at a task or day boundary. Rehydrate assembles the minimal high-signal slice for the next task under a token budget. Handoff produces a receivable artifact when work changes hands.

Checkpoint and rehydrate are available now. Handoff ships in the next milestone, and both clients refuse that surface by name today rather than pretending it exists — see the handoff artifact for what it will contain.