What this category's data looks like
This page addresses exception tracing and manual review for off-campus training compliance filing and penalty response. The materials come from three categories: school operating licenses, course filing materials, and fee disclosure. The school operating license records the institution name, address, validity period, and issuance date; the signature field and receipt are the starting point for review. Course filing materials include the course name, class hours, class count, start date, and instructor; the version number and filing receipt determine whether they are current. Fee disclosure includes fee items, amount unit, disclosure date, and refund explanation, and must correspond item by item with the class count and dates in the course filing. The three material categories are updated monthly or by batch; old versions are retained but no longer serve as the current basis, and historical versions are used for tracing. When materials enter the function, the school operating license and fee disclosure serve as the comparison baseline, and the course filing materials serve as the object being compared; exception records are generated by the model as a list based on prior dialogue turns and constraints, and are signed off after manual review.
Configuration and implementation checks
This part is executed by the memory turn count and prompt configuration in the app settings, which output the referenced historical message range and answer constraints. The exception list and review conclusions are then completed by the model, while the external entry point and authorization are handled by the publishing service and file permissions.
| Object | Check | Verification action |
|---|---|---|
| School operating license | The institution name, address, validity period, and issuance date must be consistent with the course filing materials, and the signature field and receipt must not be blank | Check the memory turn count value in the app settings, use chatId to locate the institution's historical conversation, retrieve the original license and course filing materials, and compare them field by field |
| Course filing materials | The course name, class hours, class count, and start date must correspond to the fee disclosure, and the version number and filing receipt must be the current version | Use messages to review the course fields already confirmed in prior turns, check them item by item against the class count and dates in the fee disclosure, and mark items whose versions are not synchronized |
| Fee disclosure | The fee items, amount unit, disclosure date, and refund explanation must be consistent with the course filing materials, and the disclosure receipt must be retained | Use variables to record the discrepant fields during comparison, generate an exception record with the source of the original materials, and hand it to the person in charge for handling |
Three common errors
- Phenomenon: The name, quantity, and date of the same course do not match across two materials. Cause: The filing materials and fee disclosure are updated separately, no field-level comparison was performed, and the old version is still in circulation.
- Phenomenon: The version of the course filing materials is not synchronized, and the current version and the retained version are mixed in use. Cause: The version number and filing receipt were not updated with the batch, and the receipt date was not verified during review.
- Phenomenon: The school operating license or fee disclosure lacks a signature or receipt, and the exception record cannot be traced back to the source. Cause: The signature pages and receipts were not fully collected when the materials were archived, and no completeness check was performed during the review step.
How to verify the setup
This function's acceptance: ask two consecutive follow-up questions, see whether the second question inherits the reference from the first question, check in the app settings whether the memory turn count matches the required prior context range, and use chatId to locate the same conversation.
Business test: create an exception record and see whether it can be traced back to the source material
- Check the current value of the memory turn count in the app settings, run a trial with two consecutive questions, and confirm that the second question correctly inherits the reference from the first question.
- Compare the usage records of two runs, confirm that the run consumption changes accordingly after adjusting the turn count, and check that the opening message is not treated as prior context.