Deterministic layer: audit/bin/audit-stats (Ruby) composes the existing extract fact-sheets across all production transcripts since the last run, writes per-run stats/flags/sheets to ~/.local/state/os-orchestration/audit/, and appends the metrics.tsv trend ledger (seeded with the 2026-07-10 run: 23 sessions). Judgment layer: new /os-orchestration:audit-sessions skill — sonnet auditor fan-out over precomputed flagged regions only, tiered synthesis with run-over-run trend verdicts, stops before any wording edit. Nudge: os-status check orchestration-audit-due warns when the ledger is >=14 days stale (missing ledger = machine not opted in). Planka recurrence entry deferred: gem offsets are +1y/+6m/+3m/+1m by design; +2w blocked on parked gem versioning decisions. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01XknQRvihHDpYE47RTmUR4N |
||
|---|---|---|
| bin | ||
| docs | ||
| openspec | ||
| plugins | ||
| .gitignore | ||
| CLAUDE.md | ||
| README.md | ||
| graphify-interview | ||
| memory-systems-compared060326 | ||
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-writestores 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) |