An insurer's test agent and production agent both read one policy library, so a wording edit made in test shows up in production answers the same day. What should the architect change?
Select an answer to reveal the explanation.
Short Explanation
A test kitchen that cooks from the dining room's only recipe box will change what the guests are served. You give the test agent its own policy library so a trial edit cannot change production answers. A longer prompt leaves both agents reading one book.
Full Explanation
Grounding data has its own lifecycle, separate from the agent that reads it. Here the test agent and the production agent point at one policy library, so a wording save in test is already a production change and the next live answer can cite unapproved text. The architect splits that data: the test agent gets its own policy library, and production stays on a library the test environment cannot edit. Keeping both agents on the shared library and relying on testers not to save still leaves one store, and one save still changes live answers. Pasting the policy text into both agents' instructions retires the library without giving each environment a promotable data store, and the two instruction copies can drift the next time a clause changes. Keeping the shared library and lengthening the system prompt so production skips test wording leaves the data shared, and a prompt does not stop a test write from becoming a production read. Exam caveat: a separate test library is not an approval of new policy text. Production still needs an owner and a deliberate promotion of the data. Operational check: edit one clause only in the test library, ask the production agent the matching question, and confirm the production wording did not change.