A manufacturer copied torque specifications into a chat log that only the night-shift agent reads. Day-shift agents need the same specifications, and the controlled-document library is the approved source. What should the architect do?
Select an answer to reveal the explanation.
Short Explanation
A torque value pasted into last night's chat is a scrap of paper, not the controlled document. You point every plant agent at the controlled-document library and stop using that chat log as the torque source. Copying the log to the day shift spreads the scrap.
Full Explanation
Torque specifications are controlled documents, and every plant agent that quotes them should read the controlled-document library. The chat log is a copy one night shift happened to keep, so it stops being the torque source once the agents point at the library. Copying that log into the day-shift instructions gives the day shift the same unofficial paste and leaves both shifts off the library when the specification is revised. Fine-tuning a model on the chat log teaches the pasted numbers as if a conversation were the standard, and the next controlled revision will not update a memory built from the log. Removing torque questions from the day-shift agent avoids the conflict by refusing the day shift an answer the plant still needs, and the night shift remains tied to the chat. The library is the shared source, and the chat can stay a transcript of the shift without being grounding data. Exam caveat: a value that was right on the night it was pasted is still the wrong source once a controlled library exists. Operational check: ask a day-shift agent and a night-shift agent for the same torque and confirm both cite the library, with the chat log out of both grounding sets.