---
id: ADR-001
title: Positioning and Messaging Rules
status: accepted
priority: foundational
date: "2026-05-01"
scope: messaging
---

# Context

Mneme must be positioned distinctly as the architectural governance layer for
AI-assisted development, not as a generic memory or productivity tool. Adjacent
vendors are beginning to market governance features downstream in delivery or
observability -- Mneme's differentiation is pre-generation enforcement.

# Decision

Mneme HQ is the **architectural governance layer for AI-assisted development**.
All product copy, docs, and outreach must reinforce this framing.

## Approved phrasing

- Decision Memory and Architectural Drift Prevention for Coding Agents
- The governance layer between your architecture and the model
- Context continuity and decision enforcement for AI coding workflows
- Architectural decision continuity and constraint enforcement during generation

## Avoid

- Generic AI governance framing
- Persistent memory / AI memory store / context database
- Chatbot assistant framing
- Productivity or autocomplete framing
- Downstream DevOps / deployment governance conflation

# Rationale

The core bottleneck in AI-assisted development is no longer raw model quality
but context continuity and adherence to prior architectural decisions. Mneme
owns that layer. Trust in AI-assisted development requires enforceable
architectural memory.
