A shared library needs keys.
Your notebook can be simple because you know whose notes they are. In a shared library, every shelf needs an owner, every reader needs permission, and every important change needs a history.
Source book by 递归客 (diguike) · Full attribution
A shared door is not an open door
A team memory system has to identify the caller and decide which records they may see. Authentication answers ‘who are you?’ Authorization answers ‘what are you allowed to read or change?’ Both are necessary.
Separate personal notes, project notes, and team-wide knowledge. A discovery that is safe to share within one project may contain information another project should never receive. Search must respect those boundaries before returning results, not merely hide forbidden notes in the interface.
Try the keys to the shared library
The same query can return a different allowed set for each reader. This simulation changes labels only; real access rules must be enforced by the service.
Fictional example. This experiment runs locally and does not call an AI or access your memory.
The library’s machinery grows
Moving from one local user to many users changes storage, queues, reliability, and operations. The book explores replacing a local database with shared infrastructure and distributing processing across workers.
Those are architecture proposals, not features every Claude-Mem installation already has. Scaling the number of readers is different from increasing the number of notes a model can read in one request. The archive can hold millions of records while an individual task reads a small selection.
Keep an accountable notebook
Retention rules decide how long records remain. Redaction removes information that should not be stored or shared. Audit records show who accessed or changed important material. These are practical responsibilities when memories contain someone else’s work.
When two agents contribute conflicting observations, preserve the evidence and surface the conflict. A shared notebook should help people resolve disagreement. It should not turn the last writer into the authority by accident.
Behind this lesson
Related chapters in 递归客’s original book:
The source examines Claude-Mem v12.6.2. Links are pinned to the book revision used for this course; current implementation details may differ.