A collaborative multi-agent design needs (1) per-user session state, (2) shared team workspace state for agents cooperating on one case, and (3) long-term semantic memory across cases, each with different lifecycle and isolation rules. Which persistence approach should you specify?
Select an answer to reveal the explanation.
Short Explanation
You need multi-tier state persistence: session store, shared case/team state store, and long-term semantic memory, each with lifecycle and tenant-isolation policies. Public unkeyed Redis, single-instance in-process memory, and email-as-record don't give you isolation, durability, or operational control. Define who can read/write each tier and how long data lives.
Full Explanation
Architecture guidance calls for multi-tier state persistence: session store, shared case/team state store, and long-term semantic memory, each with lifecycle and tenant-isolation policies. This covers all three state types. Anonymous public Redis without keys or expiration settings lacks isolation and lifecycle. In-process memory on one orchestrator fails multi-instance sharing and durability. Emailing state to a distribution list is not an operational state store. Align encryption and role-based access control with each tier’s sensitivity.