A review queue with reasons, not just a score

An automated quality result should narrow the work, not hide the decision. A reviewer needs the evidence, the score, the model version, and the reasons that made the case accepted, rejected, or ready for a rescan.

VEQO stores those details with the review case. The operations console can show what is waiting, why it is waiting, and who decided. The field team can then receive a rescan request without creating a second identity record.

That is the difference between an AI score and an operational control: the result is versioned, reviewable, and attached to the same evidence boundary as the enrollment.