What this category's data looks like
This page addresses corporate compliance and security training scenarios. The core materials fall into three categories: compliance training courseware, security operating procedures, and exam records. Compliance training courseware is compiled by the training department according to the annual compliance theme and is revised when regulations are updated; security operating procedures are issued by the security management department according to equipment and positions and are synchronized with process changes; exam records are generated by the training execution party by session and include participants, subjects, scores, signatures, and receipts. When these three types of materials enter the material verification and discrepancy localization function, the courseware and procedures serve as the baseline source, and the exam records serve as the object to be verified, each taking on the roles of field comparison, date comparison, and signature/receipt checking. Field characteristics center on names, quantities, dates, signatures, and version numbers. The update cadence is driven by compliance cycles and security reviews, and unsynchronized versions and missing signatures are the main sources of discrepancies.
Configuration and implementation checks
This step is executed by the tool calling node in the workflow (the model decides whether to call, and the node executes), outputting the tool call result (the input parameters and return in the call record). The "discrepancy list" is then completed by a subsequent AI node or manual verification. Based on the tool description, parameter description, and whether parameters are required, the model determines whether to call the tool this time; when there are no required parameters, the model may fabricate parameter values on its own, and when there are required parameters but no suitable values in the context, it may not call.
| Object | Check | Verification action |
|---|---|---|
| Compliance training courseware | Whether the courseware name, training date, and version number are consistent with the exam records, and whether signatures and receipts are complete | Open the tool node description field, check whether the courseware name and date parameters are required, run a test with a question missing the date, and see whether the call record shows a follow-up question or a call according to the description |
| Security operating procedures | Whether the procedure name, quantity, and effective date match the exam records, and whether the version is synchronized | Open each parameter configuration one by one, check the description and whether it is required, check that the diamond interface is connected to the target tool, and confirm the values of functionCall and toolChoice in the call record |
| Exam records | Whether the participants, subjects, scores, signatures, and receipts are consistent with the courseware and procedures | Use a real record to find fields inconsistent with the ledger, check whether the returned result contains values that do not exist in the business materials, and avoid results cross-contaminating each other after multiple tools are chained |
Three common errors
- Symptom: The name, quantity, and date of the same record do not match between the courseware and the exam records. Cause: The tool description does not specify the comparison fields, so the model matches by semantics on its own rather than using the material fields as the standard.
- Symptom: The version of the security operating procedure is not synchronized, and old-version parameters are still called. Cause: The parameter description does not indicate the version value, whether it is required does not correspond to the business fields, and the model does not ask follow-up questions.
- Symptom: The exam record lacks a signature or receipt, but the discrepancy list still shows consistency. Cause: The required parameters do not cover the signature field, and the model does not call the tool and directly gives an answer.
How to verify the setup
Acceptance of this function: run a test with a question missing a required parameter, check the input parameters and return in the call record, and confirm whether it asks a follow-up question or calls according to the description; check toolChoice, functionCall, and the diamond connection status.
Business test: use a real record to find fields inconsistent with the ledger, write back the discrepancy list, and submit it to the reviewer for confirmation.
- Open the tool node description field, check whether this description can be understood when taken out on its own, and verify the parameter description and whether it is required.
- On the canvas, check the diamond connection and node status, run a test with a question missing that field, and see whether it asks a follow-up question first instead of directly fabricating.