Go to file

jared 638c6d03ed os-vault: WS2 write-behavior eval harness + untuned baseline grid plugins/os-vault/eval/ — held-out unprompted vault-write discrimination eval: ambiguity ladder L1 explicit -> L3 conceptual, paired positives/negatives, 6 run-set scenarios on a new reportgen Ruby fixture + 6 frozen reserve twins, isolated sandbox vault, headless-only runner, deterministic-first Ruby checker (narrow judge fallback stubbable via OS_VAULT_EVAL_JUDGE_CMD), model-free self-test 21/21. Scenario Task blocks are held-out; reserve never read. Isolation seam: OS_VAULT_PATH overrides vault_path via config.load_config(); OS_VAULT_SKIP_REBUILD suppresses the SessionStart graphify rebuild. Write SKILL.md contract fix (defers to vault-conventions.md) + Vault location section. Baseline grid (run-set x sonnet/haiku x 3 reps + 1 counted canary, 37 reps): positives 1/19, negatives 18/18. L1 persists every rep but routes to built-in auto-memory instead of the vault; L2/L3 mostly don't persist; zero over-triggering. Wording loop (step 4, not started) targets: trigger at L2/L3, route to vault at L1. Loop-input candidates: vault note os-vault-write-eval-baseline-grid-results. CLAUDE.md pointers updated for this and os-status. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>		2026-07-07 12:46:22 -04:00
bin	Fix skill namespacing (drop name: frontmatter), add refresh-plugins, wire eval howto	2026-07-04 14:01:58 -04:00
docs	os-vault: WS2 write-behavior eval harness + untuned baseline grid	2026-07-07 12:46:22 -04:00
openspec	os-status: aggregated in-process SessionStart status checks (ADR-022)	2026-07-07 12:46:10 -04:00
plugins	os-vault: WS2 write-behavior eval harness + untuned baseline grid	2026-07-07 12:46:22 -04:00
.gitignore	os-status: aggregated in-process SessionStart status checks (ADR-022)	2026-07-07 12:46:10 -04:00
CLAUDE.md	os-vault: WS2 write-behavior eval harness + untuned baseline grid	2026-07-07 12:46:22 -04:00
README.md	Archive memsearch-episodic-layer change	2026-06-09 14:35:50 -04:00
graphify-interview	Add Graphify setup & best-practices guide (11 docs + research)	2026-06-03 16:45:07 -04:00
memory-systems-compared060326	Add Graphify setup & best-practices guide (11 docs + research)	2026-06-03 16:45:07 -04:00

README.md

cc-os — Cross-Project Memory for Claude Code

A personal memory system for Claude Code, designed for a multi-client freelancer. The system captures knowledge across projects and surfaces it automatically at the start of each Claude Code session.

Status

The memory plugin is live and working. Design documentation lives in docs/. Both episodic memory (memsearch) and semantic/knowledge memory (Graphify + Obsidian vault) are active.

What it does for you

Injects vault context at session start — Claude sees your SecondBrain graph summary, your conventions, and today's journal path before you type the first message.
Surfaces project structure on demand — run one command to build a graph of any project; Claude can then query it for patterns, architecture, and conventions.
Remembers conventions automatically — memory-write stores evergreen knowledge (coding patterns, client rules, recurring decisions) in the correct vault location with proper tags.
Stays fresh without a daemon — the vault graph rebuilds in the background when stale; vault writes immediately invalidate the timestamp so the next session picks up changes.
Keeps project repos clean — all indexes are build artifacts (graphify-out/); nothing is committed to project repos.

User guide

See docs/USER-GUIDE.md for setup, onboarding new projects, using the skills, and known limitations.

Directory layout

Path	Contents
`docs/memory-system/`	Architecture, ADRs, build plan, Graphify evaluation
`docs/graphify/`	Verified Graphify command handbook
`docs/USER-GUIDE.md`	Practical usage guide
`openspec/`	Spec-driven change management (changes, specs)
`graphify-interview`, `memory-systems-compared060326`	Raw source transcripts (do not cite as fact)