Engineering decisions,
made operational.
Mneme is the decision and control layer for agentic software development, and its core primitive is a durable engineering decision. This page maps each property Mneme attaches to a decision to the pages that document it in detail.
What a decision carries
Documentation records what a team decided. A Mneme decision also records whether it is binding, where it applies, what it replaces, and how it is checked, as structured properties set when the decision is recorded. That is what lets the same decision reach different agents and CI workflows and produce the same verdict.
| Property | The question it answers | Where it is documented |
|---|---|---|
| Identity | What was decided, and from which source? | Decision memory vs documentation · ADR import |
| Applicability | Does this decision apply to this change? | ADR import (path applies, skips, or is unknown) · How enforcement works |
| Authority | Who can adopt, reject, or change a decision? | Decision proposals · MCP server (non-authoritative proposals) |
| Lifecycle | Is this decision still in force, and what did it replace? | ADR import (status, explicit supersession) · Decision memory |
| Precedence | What wins when two decisions both apply? | ADR import (supersession, then scope priority and date; unresolved ties block the import) |
| Enforcement | How is the decision checked, and where? | Deterministic enforcement · GitHub Actions gate |
| Evidence | What shows the decision held? | How enforcement works (auditable verdict trace) · Protection activation (Protected only when enforcement evidence is observed) |
Architecture is the first domain
Mneme starts with architecture: ADRs and engineering standards become decisions that coding agents receive and that hooks and CI gates check deterministically. The Architecture Protection Audit classifies each discovered architectural decision as Protected, Mneme-ready, Requires modelling, or Guidance, so you can see which are deterministically protected today. Architectural drift prevention is the first use case.
The decision model is designed to extend to broader engineering policy. Other decision domains are not shipped today; see the roadmap.
Interfaces
The same decisions are reachable from several surfaces: the CLI for checks, audits, protection, and human decision authority; the local MCP server for read access and non-authoritative proposals; the GitHub Actions gate for pull requests; and the agent integrations, each with its own documented support level.