Docs.
Mneme is an open-source CLI and local MCP server for governing AI coding agents. Start with one check, connect the Decision Index, then go deeper on proposal review, violations, language coverage, and benchmark methodology.
Run your first governed check.
Install the CLI, prepare the repository, then evaluate one proposed task.
$ pipx install "mneme-hq==0.9.2" $ mneme setup $ mneme check --memory .mneme/project_memory.json --input prompt.txt --query "storage backend"
Using a coding agent?
Copy a setup prompt for Claude Code, Codex, or another local agent.
Installs and detects only. Stops before hooks, trust approval, or blocking enforcement.
How-to guides
Each guide solves one engineering job, with outputs recorded from mneme-hq 0.9.2.
Add a Constraints section to an ADR, import it, and get a FAIL when a request handler imports the database client.
Read the guide →Block a forbidden import before Claude Code writes it, and tell the agent which decision it broke.
Read the guide →Run mneme check on every changed file in GitHub Actions and keep the JSON verdicts.
Read the guide →Every guide, grouped by job, including loading the decisions that apply to a task.
All how-to guides →Reference surfaces
Mneme HQ's documentation is intentionally narrow. We document the surfaces engineers need to operate Mneme: the CLI, the local MCP server, human decision authority, the violations Mneme catches, language coverage, and benchmark methodology. Everything else lives in the source repository.
How Mneme turns architectural decisions into a structured corpus with deterministic enforcement across four workflow boundaries: guidance, prevent, catch, verify — and why retrieval is not enforcement.
How enforcement works →What Mneme can attach to an engineering decision — identity, applicability, authority, lifecycle, precedence, enforcement, and evidence — and where each is documented. Architecture is the first decision domain.
Decision model →How a Mneme-ready decision becomes a verified deterministic guardrail: mneme protect list, status, validate, activate. Validation is not activation; protection is only reported when canonical assessment observes enforcement.
Commands, flags, and exit codes for mneme, including the 0.9.0 decision-mcp server and decision authority workflow alongside setup, Audit, protection, enforcement, exports, and benchmarks.
Install and operate the local stdio Decision Index server in 0.9.0. Exact tools, input and result shapes, errors, storage, and the authority boundary.
MCP server reference →Review producer proposals, preserve provenance, and explicitly accept or reject them with the human authority CLI without silently activating protection.
Decision proposal workflow →Twelve worked examples across architecture, workflow, security, dependency, and platform governance. Each shows the rule, the AI's offending output, and the structured flag Mneme emits.
Governance violations →Canonical coverage matrix. Tier 1 (Python, TypeScript, JavaScript) and Tier 2 (Go, Java, C#, Rust). Capabilities, limitations, and roadmap per language.
Supported languages →How the v1.1 governance benchmark is measured: layered retrieval and enforcement scoring, structured-output verification, pre-registered thresholds, anti-gaming protocol.
Benchmark methodology →How to read these docs
Start with a how-to guide when you have a specific job to do. Use the CLI reference for commands, the MCP server reference for the protocol surface, decision proposals for human review, the protection activation guide for the audit-to-Protected loop, and the benchmark methodology for measurement. For the ideas behind the system, continue to Insights.
One decision boundary across every coding surface.
Connect Mneme where tasks enter, where agents edit, and where changes merge.
Explore all integrations →