Jev choice order replay sends each of three original status inputs in two label orders. The factual text and question stay the same within a pair. Ready, Pending review and Blocked appear forward in one request and reversed in the other. The downloadable observations retain each call; the local consumer compares label names rather than array positions.
An API-collected X discussion separated answer accuracy from calibration when comparing typed decision models. Our original exercise checks a narrower integration property: exact option layouts and label-based replay. It does not reproduce the source benchmark, compare provider accuracy or measure calibration. Every observed call uses the actual TypeSafe Jev SDK with the fixed Choice question.
Changing the option order still changes the exact request. Even if two calls choose the same semantic label, one response cannot stand in for the other. The original fixture records both ordered arrays and hashes them separately. That makes a mistaken cache lookup or index-based payload mapping visible before an application adds external actions.