A hospital keeps allergy lists in a file that only one departmental bot can open. The chart agent and the pharmacy agent both need those lists, and access must stay governed. What should the architect do?
Select an answer to reveal the explanation.
Short Explanation
You can keep both agents aligned by moving the allergy lists into a governed store that the chart agent and pharmacy agent can read under the same access rules. Pasting daily copies into their instructions can let them drift apart.
Full Explanation
Shared clinical facts need one governed store that each authorized agent can read, rather than a file only one departmental bot can open. Because both the chart agent and the pharmacy agent need the allergy lists under the same access rules, moving the lists into that store gives them a common, governed source. Pasting each day’s list into both agents’ instructions creates separate copies that can diverge when only one is updated. Having the pharmacy agent read the departmental bot’s private chat exposes clinical data in a transcript and may reveal other content from that chat; it also leaves the allergy file private. Training a separate custom model for each agent avoids opening the file, but each model can reflect only a snapshot of the allergies, with no governed place for later changes to land. Exam caveat: a governed store still requires an access review; moving the lists does not determine who is allowed to read them. Practical check: update an allergy in the store, confirm both agents see the change, and verify that neither relies on the private bot file as its source.