jared
/
cc-os
1
0
Fork 0
Code Issues 18 Pull Requests Packages Projects Releases Wiki Activity

Document vault conventions completion and migration scaffolding seeding 

Step 1 (vault conventions initialization) is now complete: vault-
conventions.md exists at ~/Documents/SecondBrain/ (canonical naming
resolved), all 6 fixture notes are seeded for Graphify extraction
testing, and 14 handbook + design notes have been migrated to the
vault as first-class migration scaffolding per the empirical finding
locked 2026-06-05. Update CLAUDE.md and build-plan.md to reflect
completion and implementation status.
This commit is contained in:
jared 2026-06-09 09:41:27 -04:00
parent 5834036370
commit 61a33f137b
2 changed files with 13 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
CLAUDE.md
View File

@ -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`). **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 ## Implemented Components
@ -74,9 +74,9 @@ to those two and fix the stale doc.
**Graphify** — v0.8.31 at `/home/jared/.local/bin/graphify` **Graphify** — v0.8.31 at `/home/jared/.local/bin/graphify`
- Vault graph: `~/Documents/SecondBrain/graphify-out/` — disposable, rebuilt by SessionStart hook - Vault graph: `~/Documents/SecondBrain/graphify-out/` — disposable, rebuilt by SessionStart hook
- Project graph: `<project-root>/graphify-out/` — same pattern; gitignore it in each project repo - Project graph: `<project-root>/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 ## OpenSpec workflow

15
docs/memory-system/04-build-plan.md
View File

@ -1,6 +1,6 @@
# Build Plan # 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: 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 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 `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 does not generate) and `scope` (`scope/global` or `scope/project`). Tags are now
supplementary, not the primary query mechanism. supplementary, not the primary query mechanism.
**Open question (2026-06-08):** The vault currently has a `vault-conventions.md` file, not **Naming resolved (2026-06-09):** `vault-conventions.md` is the canonical name (not
`CONVENTIONS.md`. Whether to rename/align, or treat `vault-conventions.md` as the canonical `CONVENTIONS.md`). The file exists at `~/Documents/SecondBrain/vault-conventions.md`.
name, is undecided. Resolve before the migration scaffolding deliverable is finalized.
- Seed a few real notes (e.g. `tool/semrush`, `client/<x>`) to use as extraction test cases - Seed a few real notes (e.g. `tool/semrush`, `client/<x>`) to use as extraction test cases
in Step 2. 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) ### Step 2 — Graphify + Ollama setup (the knowledge graph layer)