- From AGENTS.md or CLAUDE.md?
- Those files carry standing instructions, not history. Nauro writes your AGENTS.md context section from the record and keeps what a flat file cannot hold: each decision’s rationale, rejected alternatives, and supersession chain, retrievable by any connected agent.
- From Cursor rules or agent memory?
- Rules and memory belong to one tool. The record is vendor-neutral local Markdown, read over MCP by Claude Code, Codex, Cursor, and anything else you connect. Nothing enters it without your approval.
- From committed ADRs?
- ADRs wait to be reread. Nauro decisions are retrieved: before a change, agents check the proposal against the record and get the related history ranked by relevance.
- What happens when a decision goes stale?
- It is superseded, never silently edited. The old decision keeps its number and points forward, the new one carries the reasoning, and you approve the change. Agents always see the current rule with its lineage.
- When do I not need this?
- If committed decisions plus an agent instruction keep one repo aligned, keep them. Nauro is for judgment that must stay current across sessions, agents, and tools.