A hierarchical knowledge graph that captures the people, projects, and decisions you discuss with Claude — and brings them back into context every session, automatically. No hooks to wire, no prompts to engineer.
Claude Code has no memory between sessions. Open a new terminal tomorrow and the model knows nothing about Alice, the migration you've been planning, or the decision you made last week.
You can paste context. You can write CLAUDE.md files. You can call tools and hope. But none of that accumulates — there's no growing understanding of your work, no graph of who-does-what.
pamiec fills that gap with a knowledge graph maintained in the background. It captures conversation turns, extracts the entities that matter, and surfaces the right slice when you need it.
Inspired by GAM (arxiv 2604.12285). Real-time turn capture never contaminates the stable entity graph. Each layer has a different lifecycle, a different cost profile, and is queryable independently.
Real-time capture, semantic-boundary archive, and stable entity graph — the three layers GAM defines, with the same strict no-contamination contract between them.
Every entity has both a one-line summary (csum)
and a structured detail block (craw) — fast
retrieval up top, full context on demand.
GAM optimises for episodic memory within a long conversation. pamiec optimises for entity memory across all sessions — what do I know about Alice / Acme / ProjectX, ever.
Boundary detection uses sliding-window centroid similarity — no LLM call. Edge confidence comes from Haiku, but never the cross-encoder rerank. Cheaper to run, easier to reason about.