Concepts

Before you go deeper into the API or the cookbook, four ideas anchor everything else.

• Memory model — How MemHQ separates per-user memories, shared group knowledge, and the hybrid graph that lets them coexist.
• RBAC — Storage-layer access control. Why MemHQ enforces permissions in the retrieval path, not the application layer.
• Ingestion pipeline — The 7-phase pipeline from raw text to typed, embedded, reconciled memories.
• Reconciliation — How MemHQ detects duplicates, supersession, and contradictions when new memories arrive.

If you're trying to decide whether MemHQ is the right shape for your problem, start with the memory model. It's the single biggest divergence from how most other memory libraries are designed.