What this category's data looks like
The core objects of material verification and discrepancy location for enterprise compliance and safety training are three types of materials: compliance training courseware, safety operating procedures, and exam records. Courseware comes from the policy library and external regulatory documents, and is synchronized on a quarterly basis or when regulations are updated; operating procedures come from work sites and equipment changes, and are updated along with process adjustments; exam records come from training sign-ins and online answers, and are generated by batch. When these three types of materials enter the knowledge base retrieval node, each plays a different role: courseware and procedures provide the supporting original text, used to compare the name, quantity, and date of the same record; exam records provide signature and receipt fields, used to check discrepancies such as missing signatures, missing receipts, and unsynchronized versions. Field characteristics are concentrated in record name, quantity, date, signature, receipt, and version number. If the name, quantity, or date of the same record does not match across two materials, or the version is not synchronized, it is necessary to point back to the original passage through the citation source, form a discrepancy list, submit it to the reviewer for confirmation, and write it back.
Configuration and implementation checks
This step is executed by the citation output of the knowledge base retrieval node, which outputs an array of cited content, each item containing an original text fragment and a source identifier, and the length can be 0. The "discrepancy list" is completed subsequently by an AI node, a code node, or manually.
| Object | Check | Verification action |
|---|---|---|
| Compliance training courseware | The name, quantity, and date of the same record are consistent across the two materials; the version number and signature column are complete | In the citation array, point back one by one to the original courseware passages, verify the name, quantity, and date fields, and register quoteMaxToken and the array length separately |
| Safety operating procedures | The name, quantity, and date of the same record are consistent across the two materials; an unsynchronized version can be located | Compare the original procedure text with the exam records, verify the version number and effective date, use citation markers to point back to the passages, and check the source identifier in responseData (non-streaming module results returned with detailed output enabled) |
| Exam records | The signature and receipt fields are complete; the name, quantity, and date of the same record are consistent across the two materials | Open the citation markers to compare the sign-in and answer original text, verify the signature, receipt, and date, write missing items into the discrepancy list, and record each source item by item in quoteList |
Three common errors
- Symptom: the name, quantity, and date of the same record do not match across the two materials. Cause: the courseware and exam records are updated independently, and the fields are not cross-checked.
- Symptom: the version is not synchronized, and the old procedure version is still cited. Cause: after the materials are updated, they are not written back to the knowledge base, and retrieval hits the old passages.
- Symptom: a signature or receipt is missing, but the record still appears complete. Cause: the signature column and receipt field are not included in the comparison scope, and the cited fragments do not cover that field.
How to verify the setup
Acceptance of this feature: ask a question that has original-text support, and check whether the citation array and markers can point back to the original text; then ask a question with no matching materials, and confirm that the array is empty while the pipeline still runs through.
Business test: use a real record to find a field that is inconsistent with the ledger, record the number of citations and the quoteMaxToken budget, and do not compare the two for equality.
- In the node, check whether the selected knowledge base collections and their vector models are consistent
- Run a trial with a question that has no matching materials, see that the output is empty while the pipeline continues, and check the search parameters item by item