How Mneia works, and how to run it.

$ mneia brief "migrate the ledger writes to v2"

# Context slice: migrate the ledger writes to v2
Generated 2026-08-17 09:14 UTC · 3 items · 412/4000 tokens
Cite an item as `#id` when you use it.

## Constraints (do not violate)
- **LOAD-BEARING** [#4c1f7a2e · 2026-08-11 · human-confirmed] The cutover must be online
- **LOAD-BEARING** [#9b3d0155 · 2026-08-12 · human-confirmed] Writes stay idempotent under retry

## Superseded recently (do not re-propose)
- [#e7a4b019 · 2026-08-14 · unconfirmed · superseded] Read from the shadow table in the worker
  Replaced by reading from v2 directly.

---
task: migrate the ledger writes to v2
items: 3 (2 load-bearing) · tokens: 412/4000 · generated: 2026-08-17T09:14:22.104Z

Everything here describes one system: three operations - checkpoint, rehydrate, handoff - with conflict arbitration where they collide, reachable through the CLI, an MCP server, the web app, and a CI runner. The pages are organised by what you are trying to do rather than by which surface you reach it from, because the surfaces are translations of the same verbs and return the same answers for the same input.

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, the two clocks, and how a rehydration slice is actually chosen.10 min read
• The three operationsCheckpoint, rehydrate, and handoff in depth - the pipeline, the scoring, and the artifact.9 min read
• ReferenceEvery command, tool, flag, and exit code, plus the schema and the security posture underneath.14 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.

Where two of them collide, conflict resolution decides what happens - and only one of its three rules is automatic. Every surface is a translation of the same verbs, so the CLI, an MCP client, the web app, and a CI runner return the same answer for the same input.