diff --git a/CLAUDE.md b/CLAUDE.md index d340fc8..129e08e 100644 --- a/CLAUDE.md +++ b/CLAUDE.md @@ -61,7 +61,7 @@ to those two and fix the stale doc. **Empirical finding locked (2026-06-05):** Graphify is a structure extractor, not a topic clusterer — no emergent hub nodes appear even at `--mode deep`; hub notes + wikilinks must be author-provided during migration (not deferred). Migration scaffolding is now a first-class deliverable. Open question: do facet tags create graph edges? (ADR-014; findings: `docs/memory-system/07-graph-connectivity-findings.md`). -**Implementation status (2026-06-08):** The global Claude Code plugin is live (`~/.claude/plugins/memory/`). Steps 2a, 2b, 3, and 6 of the build plan are complete (including the `memory-project` skill, previously TODO under Step 6/Part D). Steps 1 (vault conventions), 4 (memsearch), and 5 (sync) remain. See `docs/memory-system/04-build-plan.md` for full step status. +**Implementation status (2026-06-09):** The global Claude Code plugin is live (`~/.claude/plugins/memory/`). Steps 1, 2a, 2b, 3, and 6 of the build plan are complete (including the `memory-project` skill, previously TODO under Step 6/Part D). Step 1 completed 2026-06-09: vault-conventions.md exists, all 6 fixture notes seeded, and 14 Graphify handbook + memory-system design notes migrated to the vault as migration scaffolding. Steps 4 (memsearch) and 5 (sync) remain. See `docs/memory-system/04-build-plan.md` for full step status. ## Implemented Components @@ -74,9 +74,9 @@ to those two and fix the stale doc. **Graphify** — v0.8.31 at `/home/jared/.local/bin/graphify` - Vault graph: `~/Documents/SecondBrain/graphify-out/` — disposable, rebuilt by SessionStart hook - Project graph: `/graphify-out/` — same pattern; gitignore it in each project repo -- Vault conventions: `~/Documents/SecondBrain/CONVENTIONS.md` — frontmatter contract + tag taxonomy +- Vault conventions: `~/Documents/SecondBrain/vault-conventions.md` — frontmatter contract + tag taxonomy (canonical name decided 2026-06-09; formerly referred to as CONVENTIONS.md) -**Not yet implemented:** vault conventions migration (Step 1), memsearch episodic layer (Step 4), VPS sync (Step 5) +**Not yet implemented:** memsearch episodic layer (Step 4), VPS sync (Step 5) ## OpenSpec workflow diff --git a/docs/memory-system/04-build-plan.md b/docs/memory-system/04-build-plan.md index 10c63ea..bcd7562 100644 --- a/docs/memory-system/04-build-plan.md +++ b/docs/memory-system/04-build-plan.md @@ -1,6 +1,6 @@ # Build Plan -_Last updated: 2026-06-08_ +_Last updated: 2026-06-09_ How a human builds this system, step by step, and answers to the operational questions: which scripts and hooks, how the AI knows when to write and what conventions to follow, how and @@ -37,13 +37,18 @@ plugin that packages it. `summary` (one-line, author-written — this is the human-readable router hint Graphify does not generate) and `scope` (`scope/global` or `scope/project`). Tags are now supplementary, not the primary query mechanism. - **Open question (2026-06-08):** The vault currently has a `vault-conventions.md` file, not - `CONVENTIONS.md`. Whether to rename/align, or treat `vault-conventions.md` as the canonical - name, is undecided. Resolve before the migration scaffolding deliverable is finalized. + **Naming resolved (2026-06-09):** `vault-conventions.md` is the canonical name (not + `CONVENTIONS.md`). The file exists at `~/Documents/SecondBrain/vault-conventions.md`. - Seed a few real notes (e.g. `tool/semrush`, `client/`) to use as extraction test cases in Step 2. -**Status: NOT STARTED** +**Status: COMPLETE (2026-06-09)** +- `vault-conventions.md` (renamed 2026-06-09 from `CONVENTIONS.md`) exists in the vault at + `~/Documents/SecondBrain/vault-conventions.md` — frontmatter contract + tag taxonomy. +- All 6 fixture notes exist in the vault (seeded for extraction testing in Step 2c). +- 14 Graphify handbook + memory-system design notes migrated to the vault (2026-06-09) as + part of migration scaffolding — first-class deliverable per the empirical finding locked + 2026-06-05. ### Step 2 — Graphify + Ollama setup (the knowledge graph layer)