jared
/
cc-os
1
0
Fork 0
Code Issues 18 Pull Requests Packages Projects Releases Wiki Activity
34 Commits 2 Branches 0 Tags 3.1 MiB
Python 57.4%
Ruby 33.6%
Shell 8.2%
JavaScript 0.8%
Go to file
jared 4a87acc97f Harden SB content + findability plans via round-table review 
Key changes:
- Plan B Phase 3: replace on-demand-only framing with queue-and-defer
  pattern (SessionEnd writes candidate queue fast in Python; next
  SessionStart processes it with already-running LLM — no API call,
  no terminal block, one-session lag is acceptable)
- Plan B Phase 3: cut Part B (discrepancy detection) until vault has
  25+ active howto notes
- Plan B Phase 2: fix injection hook name (session_context.py, not
  session_start.py — the latter has no output channel)
- Plan B Phase 1: add generated_at timestamp to vault-index.json
  structure so /memory-find can surface staleness
- Plan B: add silent hook failure risk row to Risks table
- Plan B: update Open Questions to reflect queue-and-defer decisions
- Plan A Layer 1: clarify opt-out framing for inline classification
- Plan A Layer 2: add cross-ref to Plan B Phase 3 invocation decision
- CLAUDE.md: clarify Graphify vault graph vs vault-index.json roles

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
 		2026-06-28 16:51:43 -04:00
docs Harden SB content + findability plans via round-table review 2026-06-28 16:51:43 -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 Harden SB content + findability plans via round-table review 2026-06-28 16:51:43 -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)