Concepts¶
These pages explain what PMB is made of, how memory moves through the system, and why the design is local-first.
flowchart TB
Agent["Agent host"] --> Integration["MCP tools and lifecycle hooks"]
Integration --> Daemon["Warm daemon"]
Daemon --> Engine["Engine"]
Engine --> Retrieval["Hybrid recall"]
Engine --> Storage["SQLite, LanceDB, BM25"]
Engine --> Core["Core queues, caches, and schema"]
Retrieval --> Context["Relevant context block"]
Context --> Agent
-
Architecture
Component map, storage layout, hooks, daemon, and where to look in code.
-
How it works
Step-by-step read path, write path, daemon behavior, and recall internals.
-
Memory model
The kinds of memory PMB keeps, keyed facts, importance, tiers, and decay.
-
Core engine
Implementation-level map of the Engine, storage schema, queues, and code paths.
-
Design and technology
The design patterns, tradeoffs, and stack choices behind PMB.
-
Privacy and security
Local-first guarantees, secret redaction, bearer-token team mode, and encrypted export.