jared
/
cc-os
1
0
Fork 0
Code Issues 18 Pull Requests Packages Projects Releases Wiki Activity
33 Commits 2 Branches 0 Tags 3.1 MiB
Python 57.4%
Ruby 33.6%
Shell 8.2%
JavaScript 0.8%
Go to file
jared c582bb1928 Add Plan A + Plan B for SecondBrain active use 
Refactors 08-sb-active-use-plan.md into two focused plans following a
design session that diagnosed separate content and findability problems.

Plan A (09): note types (convention/reference/howto), templates, value
gate, two-layer write mechanism, and vault population build order.
Plan B (10): vault-index.json, /memory-find skill, SessionStart
injection, and SessionEnd agent for self-evolving knowledge capture.

08 is retained with a superseded notice linking to the new plans.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
 		2026-06-27 17:54:03 -04:00
docs Add Plan A + Plan B for SecondBrain active use 2026-06-27 17:54:03 -04:00
openspec Source memory plugin in git; port hooks to Python; archive change 2026-06-12 12:42:05 -04:00
plugins/memory Refine memory-project onboarding: type-based exclude taxonomy + 16k-context model 2026-06-17 10:57:06 -04:00
.gitignore Complete memory plugin implementation — hooks, skills, and graph-connectivity findings 2026-06-05 16:39:49 -04:00
CLAUDE.md Refine memory-project onboarding: type-based exclude taxonomy + 16k-context model 2026-06-17 10:57:06 -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)