memory-palace

# Memory Palace Hierarchical, persistent memory system for Claude Code sessions. Organizes knowledge so agents never lose context across sessions. ## Architecture ``` Palace (global) Wing: project-name Room: authentication Drawer: "chose JWT over sessions" (2026-04-07) Drawer: "rate limiting at 100 req/min" (2026-04-06) Room: database Drawer: "PostgreSQL with pgvector" (2026-04-05) Drawer: "migration strategy: blue-green" (2026-04-04) Room: deployment Drawer: "Vercel + GitHub Actions" (2026-04-03) Wing: another-project Room: ... ``` ## Storage Format All memories stored in `~/.claude/palace/` as flat JSONL files per wing: ``` ~/.claude/palace/ index.json # Wing registry my-project.jsonl # All drawers for this wing other-project.jsonl # All drawers for this wing ``` ### Drawer Entry Format ```json { "id": "d-abc123", "wing": "my-project", "room": "authentication", "content": "Chose JWT with refresh tokens over session-based auth. Reason: stateless, mobile-friendly, scalable.", "tags": ["auth", "jwt", "architecture"], "timestamp": "2026-04-07T14:30:00Z", "session_id": "s-xyz789", "agent": "architect", "type": "decision" } ``` ### Entry Types - `decision` - Architectural or design choice with reasoning - `discovery` - Something learned about the codebase - `error` - Error encountered and how it was resolved - `constraint` - External limitation or requirement - `pattern` - Recurring code...