a375c4b354
* feat(#956): add MemPalace memory capability (ADR-857 feature plug-in) Adds an opt-in, default-resilient ADR-857 feature capability that wires MemPalace (local-first memory: MCP server + CLI) into the GSD loop: deliberate recall before discuss/plan and verbatim + temporal-KG capture at phase boundaries. Three memory modes (augment default; kg_backend and replace forward-declared). Master gate mempalace.enabled (default off); every hook onError:skip, zero gates; absent/disabled MemPalace => loop unchanged. Transport is rendered-markdown only — MemPalace runs out-of-process, no third-party code in gsd-core (ADR-857 §7). Capability: capabilities/mempalace/ (manifest + 2 fragments), skills commands/gsd/mempalace-{recall,capture}.md, agent agents/gsd-mempalace-curator.md. Registration: ns-context router, utility cluster, KNOWN_SKILLS, help full.md, model-catalog, copilot install list, size baselines; regenerated capability-registry + inventory manifest. ship:post wired into ship.md (wire-on-demand). HELD on #1196: this capability also declares hooks at discuss:pre and discuss:post, which are structurally un-wireable until the host-loop conformance model covers the discuss phase (discuss-phase.md is not in HOST_LOOP_FILES). The phase6-capstone-conformance gate therefore fails on exactly those two orphaned points by design — see #1196. Once #1196 lands, rebase onto next and the gate goes green with no further change. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> * docs(#956): backfill changeset PR number (#1201) Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2.1 KiB
2.1 KiB
Memory recall (MemPalace)
Gate first. Read .planning/config.json. If mempalace.enabled is not true, or mempalace.recall_on_discuss is false, skip this entire section and continue the discussion unchanged. (This contribution is only injected when the capability is enabled; the recall_on_discuss check lets you turn discuss-time recall off without disabling the rest of the capability.)
Otherwise — before gathering new context, surface what you already know. This is read-only and side-effect-free; if MemPalace is unreachable, note "memory unavailable" and continue — recall never blocks discussion.
- Resolve the wing. Use
mempalace.wingif set; otherwise derive it fromproject_code(fall back to the project directory name). - Wake up (cheap, ~600–900 tokens).
- Interactive run → call
mempalace_searchafter a wake-up read of the wing. - Headless/cron run (no MCP server) → run
mempalace wake-up --wing <wing>via the CLI.
- Interactive run → call
- Targeted recall. Search the palace for prior work on this phase's topic:
- Interactive →
mempalace_search(query=<phase topic>, wing=<wing>)and, whenmempalace.mirror_kgis on,mempalace_kg_query/mempalace_kg_timelinefor decision facts and their validity windows. - Headless →
mempalace search "<phase topic>" --wing <wing>.
- Interactive →
- Mode awareness. Only
augmentis currently wired: always treat the palace as an additional recall layer on top of GSD's native memory — never skip.planning/graphs/or STATE.kg_backend/replaceare forward-declared and behave asaugmenttoday. - Surface, don't dump. Fold the top relevant drawers, decisions, patterns, and surprises into the discussion as prior context — cite drawer/fact provenance. Do not paste raw search output.
If any MemPalace call errors or times out, skip the rest of recall and proceed with discussion as normal.