override signal

A signal generated when users correct, reject, or bypass system output — one of the most valuable inputs for improving evals and workflow design.
The override signal revealed that the model misunderstood one policy clause.

workflow context

The information needed to make a workflow step useful: user role, current task, relevant object, policy, history, and next action. FDEs pass exactly what's needed, not the whole ticket.
The FDE passed workflow context into the agent instead of dumping the whole ticket.

paper cut

A small UX, data, or workflow friction that seems minor but harms adoption when repeated on every case.
The paper cut was one extra click on every case.

success metric

A concrete measure used to judge whether the deployment is working: hours saved, cycle time, adoption, error reduction, or revenue impact. Agreed before launch, not invented after.
The success metric was time from ticket creation to first useful response.