Jev decision handoff audit checks whether software followed a supplied decision-to-route contract. A model can return the expected label while wrapper code sends the work elsewhere. This demonstration audits that handoff without classifying the original ticket again.
The API-collected source describes an evaluator finding a bug in its own application logic: the model record and the software decision did not agree. Our original support-queue example isolates that problem using explicit synthetic records. It does not reproduce the source company analysis, timing or financial decisions. The editable window makes a real Jev request to audit the supplied record.
Each record contains a mapping contract, probabilities for the inner decision and the route the application reports. These inner records are caller-authored examples, not measured source responses or authenticated logs. The six outer audit responses are actual API observations. Keep that distinction when interpreting the table or replacing a fixture with your own application evidence.