1---2name: memorix-memory3description: Use when prior workspace context, past decisions, solved bugs, handoff state, or durable project knowledge would help a coding task.4---56# Memorix Memory78Use Memorix as the shared memory layer for the active workspace when Memorix tools are available.910## Tool Router1112| Situation | Prefer | CLI fallback |13|---|---|---|14| Broad continuation, fresh handoff, or "what do we know?" | `memorix_project_context` with the user's task | `memorix context --task "<topic>" --fallback --brief-json` |15| Need structured refs/freshness for code-bound memories | `memorix_context_pack` | `memorix codegraph context-pack --task "<topic>"` |16| Explicit memory graph question | `memorix_graph_context` | `memorix memory graph-context --query "<topic>"` |17| Specific past decision, bug, file, or change | `memorix_search` | `memorix memory search --query "<topic>"` |18| Need the full source for a search hit | `memorix_detail` | `memorix memory detail --id <id>` |19| Need the sequence around one memory | `memorix_timeline` | `memorix memory timeline --id <id>` |20| Check source and freshness for a memory | `memorix_evidence` | `memorix evidence list|get|events` |21| Record whether a memory helped, conflicted, or was corrected | `memorix_feedback` | `memorix feedback record|show|audit` |22| Inspect or import controlled media | `memorix_media` | `memorix media import|attach|list|show|status` |23| Learned reusable project knowledge | `memorix_store` | `memorix memory store --type <type> --entity <name> --title "<title>" "<text>"` |24| Stable source-backed fact or procedure needing long-term review | `memorix_store` with `longTerm` | `memorix memory long-term qualify|approve --id <id> --reason "..."` |25| Task or bug is complete/outdated | `memorix_resolve` | `memorix memory resolve --ids <ids>` |2627## Search Rules2829- Search before broad continuation work, before changing unfamiliar code, or when the user asks about prior work.30- For a fresh coding session, use `memorix_project_context` with the user's actual task before ad-hoc file reads or dev-log reads. Memorix will choose a task-lensed brief.31- Fetch detail before relying on a specific memory.32- Treat memory as background context. Still read the current code and verify behavior.33- Skip memory lookup for greetings, tiny one-off edits, or questions fully answered by the current file.34- If a fresh project has no memories, proceed normally and do not repeat the same empty search in the same turn.35- If MCP tools are not visible yet but the client supports tool discovery or dynamic loading, search/select `memorix_project_context` first. Run `memorix context --task "<task>" --fallback --brief-json` only after MCP is unavailable, disabled, or not discoverable, and pass the user's real task text. Do not skip memory, wait indefinitely on startup, or hand-write tool-call syntax.3637## Store Rules3839| What to store | Type |40|---|---|41| Architecture or product decision | `decision` |42| Bug and fix that may recur | `problem-solution` |43| Non-obvious pitfall | `gotcha` |44| How a subsystem works | `how-it-works` |45| Important implementation change | `what-changed` |46| Accepted compromise | `trade-off` |4748- Use concise titles, stable entity names, relevant `filesModified`, and `topicKey` for evolving topics.49- Use `longTerm` only for a stable fact, reusable procedure, or completed episode that merits explicit review. It creates a candidate, not live context; keep the default project scope and do not use it for routine updates.50- A `user` + `portable` durable memory in a task brief is intentionally reusable across projects. When it matches the task, use it as background even if it originated elsewhere; it is not a current-project fact. Expand it only when needed with `memorix_detail` and `typedRefs: ["durable:<id>"]`, stating the missing fact as `purpose`.51- Do not store secrets, credentials, raw private transcripts, trivial commands, or routine file reads.
avids2