During a multi-turn conversation, an owner says "show me Bella's last visit," and two turns later asks "and her next appointment?" without repeating the patient's name. For the agent to resolve "her" correctly, what mechanism is holding the identified patient across turns?
Select an answer to reveal the explanation.
Short Explanation
Once the agent has figured out "Bella" means Patient 0031, it shouldn't have to solve that riddle again two turns later. A variable is the sticky note it keeps on the desk for the rest of the conversation.
Full Explanation
Variables are the mechanism for carrying resolved context, such as an identified patient, across turns in the same session so later actions and topics can reference it without re-resolving it from scratch every time. Once "Bella" is matched to a specific Patient record, storing that as a variable lets subsequent actions like fetching the next appointment operate on the correct record deterministically, rather than re-inferring identity from ambiguous pronouns. Zero data retention is a Trust Layer property about not persisting prompts and responses with the model provider after processing; it is a privacy control, not a session-context mechanism, and it does not explain how "her" resolves correctly. A dedicated topic for tracking pronouns misunderstands what topics do: topics govern classification and instructions for a category of request, they are not a state-storage mechanism. Relying on the classification description to re-infer the patient from context each time is fragile and is exactly the kind of ambiguity variables are meant to eliminate. The adjacent fact worth knowing: variables can be scoped to a session so they reset appropriately when a new conversation begins with a different owner.