What this category's data looks like
The exception tracing and manual review for undergraduate program revision draws on three types of documents: program plans, course syllabi, and credit structure tables. The program plan provides the curriculum system and the total credit framework; the course syllabus carries the class hours, assessment, and signatures for a single course; the credit structure table records the credit amounts and version dates for each module. Materials enter by semester revision batch, with fields including course name, course code, credits, class hours, semester offered, revision date, and signature field. When entering this feature, the three types of materials each serve as original record sources: the program plan and course syllabus are used to compare the name and date of the same course record, the credit structure table is used to check quantities and versions, the exception list must be able to point back to specific material rows, and the review conclusion must correspond to signatures and receipts.
Configuration and implementation checks
The memory turns and prompt configuration in the app settings only output the reference historical message range and answer constraints; the exception list and review conclusion are to be produced by the model next. The memory turns control how many previous turns of dialogue can be referenced at most when answering, and the prompt constrains the answer format and citation scope. The external entry point and authorization are handled by the publishing service and file permissions, and are not generated by this step.
| Object | Check | Verification action |
|---|---|---|
| Program plan | Course name, course code, revision date, and signature field must correspond item by item with the course syllabus; if the name or date of the same record does not match, it is an exception | Check the memory turns value in the app settings, run a trial with two consecutive follow-up questions, check whether the second question correctly carries the reference from the first question, and confirm the historical range in messages |
| Course syllabus | The class hours, credits, assessment method, and signature receipt of a single course must be consistent with the quantities in the credit structure table; missing signature or receipt is an exception | Create a record where the course syllabus and credit structure table quantities are inconsistent, trace it back to the original material row, and record chatId and variables for review |
| Credit structure table | The credit amounts and version dates of each module must be synchronized with the program plan; if the version is not synchronized or the quantities do not match, it is an exception | Compare the usage records of two runs, confirm the consumption change after adjusting the turns, and separately record the tokens of the cited text and the number of array items |
Three common errors
- Symptom: The name and credits of the same course do not match between the program plan and the course syllabus. Cause: The two materials are from different revision batches, and field-level comparison was not performed before entering review.
- Symptom: The version date of the credit structure table is earlier than the revision date of the program plan, but the quantities are still cited from the old version. Cause: The version was not synchronized, and the version number was not marked when the material entered.
- Symptom: The review conclusion lacks a signature or receipt, and the exception list cannot point back to the original material row. Cause: The signature field was not archived together with the exception record, and the traceability chain is broken.
How to verify the setup
Acceptance for this feature: with two consecutive follow-up questions, see whether the second question correctly carries the reference from the first question, and confirm the historical range under the memory turns value and prompt constraints.
Business test: create an exception record, see whether it can be traced to the source material, and check whether the exception list and review conclusion correspond to signatures and receipts.
- Check the current memory turns value in the app settings, run a trial with two consecutive questions, and check whether the reference in the second question is correctly carried.
- Compare the usage records of two runs, confirm the consumption change after adjusting the turns, and separately record the number of citation array items and the tokens of the cited text.