Question 370
At Foxhaven Engineering, a fine-tuned classifier is registered but its application keeps calling the earlier checkpoint. What ongoing assurance step addresses the source of this defect?
Answer and explanations
The appropriate recurring control at Foxhaven Engineering is: Audit model lineage and serving tags at every promotion or rollback. It addresses the original observation: a fine-tuned classifier is registered but its application keeps calling the earlier checkpoint.
Reviewing cortex analyst semantic metric grounding would monitor another dependency. At Foxhaven Engineering, a fine-tuned classifier is registered but its application keeps calling the earlier checkpoint. Prevent recurrence by: Audit model lineage and serving tags at every promotion or rollback.
The Foxhaven Engineering case reports that a fine-tuned classifier is registered but its application keeps calling the earlier checkpoint. A check of cortex search refresh visibility would not follow this failure mode. The relevant continuing control is: Audit model lineage and serving tags at every promotion or rollback.
The Foxhaven Engineering case reports that a fine-tuned classifier is registered but its application keeps calling the earlier checkpoint. A check of agent routing between structured and text tools would not follow this failure mode. The relevant continuing control is: Audit model lineage and serving tags at every promotion or rollback.