memory-architecturelisted

# Memory Architecture Worclaude projects use **five distinct memory layers**. Each has a different scope, owner, and lifecycle. Routing a fact to the correct layer is a load-bearing decision — the wrong layer means the fact is invisible when needed, or noisy when not. ## The Five Layers | Layer | Scope | Owner | Lifecycle | | ------------------------- | -------- | ----------------------- | -------------------------------- | | `CLAUDE.md` | Team | Manual (humans + Claude via `/update-claude-md`) | Stable, lean (target ~200 lines) | | `.claude/rules/` | Team | Manual, topic-organized | Stable; optionally path-scoped (deferred — see BACKLOG) | | `.claude/learnings/` | Team | Hook-captured (`learn-capture.cjs`) | Append-only; transient inputs to promotion | | `CLAUDE.local.md` | Personal | Manual; gitignored | Per-machine sandbox; never shared | | Claude Code auto memory | Personal | Autonomous (Claude) | Active, self-pruning | The line between team and personal is the most important boundary. Team layers are committed and shared with collaborators; personal layers stay on the local machine. ## Routing Contract When a fact, rule, or pattern surfaces during a session, route it like this: | Source | Destination | | --------------------------------------------------- | -------