9a. Private working memory (Blended Memory)#

Your agent gets a private scratchpad that only you can see, plus a single call that rehydrates a session by blending that private memory with the team knowledge base. This is the "pick up where I left off" tier — it keeps an agent's continuity without ever mixing your private working notes into the shared brain. It needs a "Read + remember" token (§9); retrieval works with any member token.

Three tools (and their REST twins, §13):

• remember_context — save distilled facts from the current session to your private memory. Each item is a short statement with an optional kind (fact, decision, preference, open_loop) and optional referenced_ids (concept/document ids it touched). Pass a stable thread_key to group a conversation so it can be rehydrated later. Re-saving the same statement updates it in place rather than duplicating.
• retrieve_context — rehydrate. Returns two labelled lists: private (your own prior context, ranked by relevance to the query) and reference (relevant team knowledge — playbooks and curated concepts). Pass a thread_key to narrow the private half to one conversation.
• promote_context — take one of your private items (by the context_id from retrieve_context) and propose it to the whole team. It lands in the Review queue exactly like remember_knowledge — a human curates before it can become authoritative. Nothing is promoted automatically.

What's private stays private. Your working memory lives in a separate, member-scoped store — it is not part of the knowledge base, never appears in anyone else's search_knowledge, and isn't visible to admins or on the dashboard. Isolation is structural and fail-closed: a query can only ever see its own member's rows. We store the distilled facts your agent writes, not your transcripts — the conversation itself never lands in KnowledgeV8.

referenced_ids are just pointers, never a back door: to actually re-open a referenced concept your agent calls read_concept, which re-applies your live permissions — a pointer to something you can no longer see resolves to nothing.

Retention (admin). Private working memory is kept until deleted by default. An admin can set an expiry under Settings → retention (Private working memory, in days); after that, expired private context is purged automatically on the daily sweep. This never touches the shared knowledge base.

remember vs. remember_context: remember_knowledge proposes a fact to the whole team (reviewable, §9); remember_context keeps it private to you. Use context for an agent's own continuity; use knowledge (or promote_context) when the team should have it.