A utility's prebuilt field copilot already summarizes the work order for the crew. It does not know the local rule that says when a crew must stop and call the control room. What should the architect add?
Select an answer to reveal the explanation.
Short Explanation
The crew already gets a usable briefing of the work order. You add a tool for the stop-and-call rule the field copilot lacks, and you leave the summary on that prebuilt copilot. Telling it to be careful does not teach the rule.
Full Explanation
The prebuilt field copilot already summarizes the work order, so that summary stays. The gap is the local rule for when a crew must stop and call the control room, and the architect adds a tool for that rule only. A replacement agent that writes the work-order summary again and still leaves the local rule out duplicates a summary the field copilot already produces and does not close the gap. A custom vision model trained on truck photos, with the work-order summary removed from the crew view, swaps a text summary for an image model and still does not state the stop-and-call rule. A longer instruction that tells the field copilot to be careful and adds no tool for the local rule is a caution sentence, and the crew still has no tool that applies the rule. The size of the gap is one rule. Exam caveat: the tool states when to stop and call. It does not itself send a switching order onto the live network. Operational check: open a test work order, confirm the prebuilt summary still appears, and confirm the new tool returns the stop-and-call rule for a case that matches it.