memtrace-decision-memorylisted
Install: claude install-skill syncable-dev/memtrace-public
# Decision Memory First
## The Iron Law
```
BEFORE you assume why code exists, contradict a convention, re-pick a settled
choice, or delete code that "looks unused/weird" → CHECK DECISION MEMORY.
recall_decision(free-text) → what did we decide / ban about X?
why_is_this_here(symbol_id) → what decision put this here?
verify_intent(decision_id) → did that decision still hold, or was it violated?
get_arc(decision_id) → what episodes implemented it?
governing_contracts(sym_id) → what constraints bind this symbol?
```
This is the **rationale layer** of the codebase. `memtrace-first` answers *what the
code is and how it's wired* (symbols, calls, git, blast radius). Decision memory
answers *why it is the way it is, what we already decided, and whether that decision
still holds* — extracted from real coding conversations and decisions, not the AST.
The graph can tell you a function exists and who calls it. Only decision memory can
tell you that three weeks ago you **banned** the approach you're about to reintroduce.
Full parameter spec for every Memtrace tool: `references/mcp-parameters.md` (bundled at the memtrace-skills plugin root).
## The honesty contract — read this first
These five tools are **deterministic, zero-LLM**. Every call returns a labeled
**Verdict / Evidence / CannotProve** answer carrying its FactStatus and proof path.
**No tool ever fabricates an answer.**
| Answer | What it means | What you must NOT do |
|---|---|---|
| **Verdict + Evidence*