Specialized-Agent Personal Memory

Technical contract and phased rollout for isolated durable memory owned by specialized agents.

Specialized agents have a durable personal notebook that is separate from shared company, room, conversation, and owner memory. The notebook is identified by the Memory v2 audience tuple audience_kind='agent' plus audience_key=<specialized-agent-id>. Its legacy projection uses agent_memories.memory_scope='agent', private visibility, and metadata.specializedAgentId for auditability.

P1: namespace, tagging, and scoped tools

P1 ships the invisible storage and isolation foundation:

  • enabled specialist runs write extracted and explicit memories to their own agent audience, including room and channel runs
  • memory_search and context_search accept scope="personal"|"shared"|"all"; memory_store accepts scope="personal"|"shared"
  • specialist search defaults to all, specialist storage defaults to personal, and main-agent behavior remains shared
  • personal access is always resolved from the active runtime envelope; callers cannot supply another specialist id
  • main bootstrap, Learning prompt injection, Wiki, Dreaming, and workspace Knowledge Graph builds exclude personal memory by default; self-acting agents additionally project it into an isolated per-agent graph (scope_key='agent:<id>') that remains invisible to workspace builds, Wiki, Dreaming, users, and other agents
  • personal_memory_enabled is stored and forwarded with the specialist runtime envelope; admins can control it in the specialist editor, and self-acting heartbeat runs receive the same envelope automatically

Rollout phases

  • P2 — prompt injection (shipped): selectively inject the current specialist's personal notebook into its prompt/bootstrap context.
  • P3 — self-acting Knowledge Graph (shipped): project approved personal memory for self-acting agents into isolated per-agent graph builds and expose it only to that agent's knowledge_* tools.
  • P4 — UI (planned): extend the shipped enable/disable control with notebook inspection, audit views, and direct memory management.

P1 deliberately does not seed notebooks, inject personal facts automatically, promote personal facts into shared knowledge, or change Apple clients.