nmg-memory

NMG Memory

Treat this file as the quick-start card, not a document to reread every turn. Once the workflow is known, use it directly. Read a reference only after forgetting an operation or encountering its named special case.

Responsibilities and boundaries

• Use NMG to recall and save durable information; do not treat it as the final judge of truth, currency, relevance, or evidence completeness.
• Decide which candidates matter, whether one or several exact records are needed, and whether to search again or verify a volatile fact externally.
• Accept no useful memory as a valid outcome.
• Save only attributable durable information. Keep secrets, transient content, unconfirmed Assistant proposals, and unsupported guesses out of memory.
• When temporary cross-Agent coordination is enabled, use the task board rather than LTG or Markdown files. Blackboard entries expire and never become durable memory unless an Agent separately calls nmg remember with attributable evidence. Ordinary single-Agent memory use does not require the board.
• Let ordinary work produce natural improvement evidence when controller shadow collection is enabled. Record only outcomes that are directly observable; an uncorrected answer, silence, retrieval, or answer reuse remains unknown.

Normal workflow

1. Check nmg daemon status --json and inspect both running and compatible.

2. If it is not running, run nmg daemon start --json and remember that this Agent invocation owns the daemon. If it is running but compatible=false, do not reuse or automatically replace it: report that a coordinated nmg daemon restart is required. A shared daemon may still serve another active Agent, so only its owner or the user may choose the safe restart point.

3. Before answering a history-dependent question, run:

   nmg search "<focused recall query>" --project-dir . --limit 8 --max-tier 1 --compact-json
   

   Narrow the scope when the store is large or the topic is specific: --node "<name>", --scope project=NAME, --source-actor user, --include-historical, --max-tier 2, --graph-hops 2.