What this category's data looks like
In the training institution scheduling and class-hour deduction category, materials come from three types: class schedules, class-hour deduction records, and schedule change requests. Class schedules are generated weekly or monthly, recording classes, courses, teachers, classrooms, time slots, and student rosters; class-hour deduction records are produced after each class, containing the student, course, date, number of class hours, and signature field; schedule change requests are submitted when changes occur, containing the original time slot, new time slot, reason, and approval receipt. The three types of materials update at different rhythms: class schedules adjust with scheduling plans, class-hour deduction records are appended one by one as classes occur, and schedule change requests circulate at approval nodes. When the materials enter the multi-turn dialogue and prompt feature, each plays a different role: class schedules provide baseline scheduling facts, class-hour deduction records provide actual consumption facts, and schedule change requests provide the basis for changes and approval traces. Together, the three support exception tracing and manual review.
Configuration and implementation checks
This part is executed by the memory turn count and prompt configuration in the application settings, outputting 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 |
|---|---|---|
| Class schedule | Whether the class, course, teacher, classroom, time slot, student roster, and version date match the class-hour deduction records item by item | Check the memory turn count value in the application settings, run a trial with two consecutive follow-up questions, and see whether the prior context range in messages covers the class schedule baseline fields |
| Class-hour deduction record | Whether the date, number of class hours, signature or receipt for the same student and same course are consistent with the class schedule and schedule change request | Compare the usage records of two runs to confirm that after adjusting the turn count, the historical message range corresponding to chatId can bring back the original entries of the class-hour deduction record |
| Schedule change request | Whether the original time slot, new time slot, approval receipt, and class schedule version are synchronized, and whether entries missing a signature or receipt can be located | Use variables to mark the schedule change request version, ask a second consecutive follow-up question that refers to the schedule change form in the first question, and see whether the answer carries it forward |
| Exception list | Whether each exception is supported by original records, and whether the reviewer signature field is complete | Create an exception record and trace it back along messages to the source material in the class schedule, class-hour deduction record, or schedule change request |
Three common errors
- Phenomenon: The name or number of class hours for the same student and same course does not match between the class schedule and the class-hour deduction record. Cause: The two materials update at different rhythms, and after the class-hour deduction record is appended, the class schedule version is not written back.
- Phenomenon: The schedule change request has been approved, but the class schedule still shows the original time slot, and the dates do not match. Cause: The versions are not synchronized, the approval receipt does not trigger a class schedule update, and the historical message range only brings back the old version.
- Phenomenon: The class-hour deduction record is missing a signature or the schedule change request is missing a receipt, so the review conclusion cannot be signed off. Cause: A step in the material circulation was omitted, and the exception list lacks support from original records.
How to verify the setup
Acceptance for this feature: run a trial with two consecutive follow-up questions, with the second question using a reference to carry forward the first question, check whether the second question carries forward the reference from the first question, and verify whether the referenced historical message range in messages matches the prompt constraints.
Business test: create an exception record, see whether it can be traced to the source material, and confirm that the fields, dates, and signatures of the class schedule, class-hour deduction record, and schedule change request can be matched item by item.
- Check the current memory turn count value in the application settings, match it with the prior context range required by the question, and compare the usage records of two runs.
- Run a trial with two consecutive questions, with the second question using a reference to carry forward the first question, and check whether the answer carries it forward and does not treat the opening message as prior context.