A multi-turn housing-intake chat must remember the current session's income answers without permanently storing them. Which memory design matches that requirement?
Select an answer to reveal the explanation.
Short Explanation
Session sticky notes, not a forever filing cabinet. Income answers need to hang around for this chat so the form makes sense—then they shouldn't automatically become permanent city memory.
Full Explanation
Multi-turn housing-intake that must remember income answers for the current session without permanently storing them calls for short-term conversational memory scoped to the session, with long-term retention avoided by default. That design preserves dialogue continuity for eligibility questioning while respecting civic privacy expectations for sensitive financial answers.
Writing every income answer into a permanent lifelong resident profile fails because the stem forbids permanent storage by default. Publishing income answers to an open municipal data portal fails by concept as a confidentiality breach, not a memory architecture. Discarding context after every single user message fails because multi-turn intake becomes impossible without session memory.
Exam caveat: distinguish short-term/session memory from long-term memory. Session continuity ≠ lifelong profile writing, and privacy-minimizing defaults are often the tested point in civic scenarios.
Operational check: complete a multi-turn intake, confirm later turns still see earlier income answers; end the session and verify those answers are not present in long-term stores; start a new session and confirm prior income values are not auto-loaded.