What this category's data looks like
This page addresses off-campus training compliance filing and penalty response scenarios. Materials come from three types of records: school operating licenses, course filing materials, and fee disclosure. They are updated by batch and semester, and their field characteristics center on names, quantities, dates, signatures, and receipts. When the school operating license enters this function, it serves as the underlying document for subject qualification; course filing materials serve as the basis for course scope and class hours; fee disclosure serves as the source for amounts and refund criteria. The three types of materials each play a field-supply role in the drafting and handover stages: the license provides the subject name and validity period, course filing provides course names and class hour quantities, and fee disclosure provides fee items and disclosure dates. The names, quantities, and dates of the same record in two materials must be consistent, versions and dates must be synchronized, and signatures and receipts must be complete before the record can proceed to the next stage for acceptance.
Configuration and implementation checks
This step is executed by the memory turn count and prompt configuration in the application settings, which output the historical message range and answer constraints to reference. The model then completes the draftable materials and handover records. The memory turn count controls how many previous dialogue turns can be referenced at most when answering, and its value must match the prior context range required by the question.
| Object | Check | Verification action |
|---|---|---|
| School operating license | The subject name, validity period, signature, and receipt must be consistent with the course filing materials | Check the current value in the application settings, run a trial with two consecutive questions, and see whether messages and variables carry forward the prior reference |
| Course filing materials | The course name, class hour quantity, and date must match the fee disclosure, and versions must be synchronized | Compare the usage records of two runs, and check whether the version and date in the session corresponding to chatId are consistent |
| Fee disclosure | The fee items, amount criteria, and disclosure date must be consistent with the school operating license and course filing materials | Run a trial with two consecutive questions, confirm that when the second question refers to a fee item the answer is not off-topic, and check whether the signature and receipt are complete |
Three common errors
- Phenomenon: The name and date of the same record do not match between the school operating license and the course filing materials. Cause: The two materials were drafted separately, without field alignment and version synchronization.
- Phenomenon: The class hour quantity and number of fee items in the fee disclosure and course filing materials are inconsistent. Cause: The update rhythms differ, old versions were not replaced, and items were not checked one by one during handover.
- Phenomenon: The material draft lacks a signature or receipt, so the next stage cannot accept it. Cause: The handover record did not specify the responsible person, and the version and date were not synchronized.
How to verify the setup
This function's acceptance: use two consecutive follow-up questions to see whether the second question carries forward the reference from the first; check the current value of the memory turn count in the application settings, and check whether messages, variables, and the session corresponding to chatId bring in the correct prior context range.
Business test: draft one according to the template and complete one handover, and see whether missing items are blocked.
- Check the current value of the memory turn count in the application settings, and confirm that it matches the prior context range required by the question.
- Run a trial with two consecutive questions, check whether the reference in the second question is correctly carried forward, and compare the usage records of the two runs.