Emergency management wants an agent that remembers prior incident briefings across shift handoffs. Which Foundry planning choice addresses that need?

Emergency management agents that must remember prior incident briefings across shift handoffs require memory integration in the Foundry plan. Continuity is the requirement: the next operator should inherit briefing context rather than restarting from a blank turn. Memory is the planning construct that persists relevant conversation or briefing state across those handoffs for long-running civic agents.

Session scoping extension for the agent so briefing dialogue context continues across shifts fails because it merely stretches transient dialogue state instead of providing durable, retention-scoped memory that a new operator's new session can inherit at handoff. Retrieval augmentation for the agent so live situation report detail refreshes across shifts fails because it refreshes present conditions but does not carry prior briefing context forward; the business requirement is controlled persistence across shifts, not just current-data grounding. Structured tool-call logging for the agent so prior incident actions stay reviewable across shifts fails because logs keep actions reviewable after the fact but do not supply the agent with usable briefing context during the shift handoff.

Exam caveat: memory for emergencies must be retention-scoped, access-controlled, and appropriate for sensitive incident data—not infinite unconstrained chat logs. Operational check: simulate a shift handoff with a briefing stored in memory, start a new session as the next operator, confirm critical incident details are available, and verify purge or archival policies match emergency-management records rules.