The internal rows this run read, and the supplier documents it read them against.
The video shows the example being run. This public page only shows the finished result, so the re-run button isn't shown here.
Each record needs evidence for every heat it declares, so a record spanning two heats counts as two things to cover. Every number on this page is read off the same run that produced the review queue.
| Run | 3fe7e4f13e02cf7c |
| Certificate PDFs read | 25 |
| Heats needing evidence | 26 |
| Status | Count | Meaning |
|---|---|---|
| EVIDENCED | 19 | Required identity and coverage evidence resolves and every configured check passes. |
| MISSING | 1 | No certificate carries this record's order reference, heat or lot identity. |
| CONFLICTING | 3 | A relevant certificate exists, but a checked requirement conflicts. |
| AMBIGUOUS | 2 | Certificate evidence is present, but the association cannot be established deterministically - several plausible candidates, or not enough identity evidence on the only one. The system refuses to choose. |
Every certificate in the folder is accounted for.
| Account | Count | Meaning |
|---|---|---|
| associated | 19 | Used as evidence for at least one received record. |
| considered, not associated | 5 | Anchored to a record, but a checked requirement conflicts or the association is not resolvable. |
| unrelated | 1 | Shares no transaction reference, heat or lot with any record in this batch. |
{
"certificate_accounts": {
"associated": 19,
"considered_not_associated": 5,
"unrelated": 1
},
"certificates_loaded": 25,
"coverage_requirements": 26,
"fully_evidenced": 19,
"need_qa_review": 6,
"run_id": "3fe7e4f13e02cf7c",
"status_counts": {
"AMBIGUOUS": 2,
"CONFLICTING": 3,
"EVIDENCED": 19,
"MISSING": 1
},
"total_received_records": 25
}