What this category's data looks like
Undergraduate program revision involves three types of materials: program plans, course syllabi, and credit structure tables. The sources are departmental teaching committees and course-offering units, and the update cadence rolls forward by academic year or program cycle. Program plans contain the program name, course modules, total credits, study requirements, version number, and issue date; course syllabi contain the course name, hours and credits, assessment method, and responsible person's signature; credit structure tables contain the credit count, proportion, and corresponding course list for each module. When the materials enter the multi-turn dialogue and prompts feature, the program plan serves as the main record providing the curriculum system and credit framework, the course syllabus serves as the supporting record providing single-course details, and the credit structure table serves as the verification record providing quantities and proportions. Together, the three form a signable material draft and handover record. Only when the fields are complete, the responsible persons are clear, and the version and date are consistent can it be handed to the next stage for sign-off.
Configuration and implementation checks
This step is executed by the memory turns and prompt configuration in the app settings, and the output references the historical message range and answer constraints. The "signable material draft and handover record" is then completed by the model. Memory turns control how many previous rounds of dialogue can be referenced at most when answering. If the value is too small, the preceding text cannot be used; if the value is too large, irrelevant content is brought in and consumption increases.
| Object | Check | Verification action |
|---|---|---|
| Program plan | The program name, course modules, total credits, version number, and issue date are consistent between the program plan and the course syllabi | Compare the same record in the two materials, verify the name, quantity, and date, and check the current value of memory turns in the app settings |
| Course syllabus | The course name, hours and credits, assessment method, and responsible person's signature match the corresponding items in the credit structure table | Compare the fields item by item, check whether the signature and receipt are complete, and use two consecutive question rounds to test referential continuity |
| Credit structure table | The credit count, proportion, and corresponding course list of each module are synchronized with the program plan version | Check whether the version number and date are synchronized, compare the usage records of two runs, and confirm that usage changes accordingly after the turns are adjusted |
| Handover record | The responsible person, sign-off date, version number, and receipt are consistent between the handover record and the material draft | Check whether missing items are blocked, and confirm that chatId, messages, and variables are correctly passed in the session and variables |
Three common errors
- Phenomenon: The same course name is written differently in the program plan and the course syllabus, and the quantities and dates do not match. Cause: The two materials were drafted separately and were not checked against a unified field template.
- Phenomenon: The credit structure table has been updated, but the program plan is still the old version, and the version and date are not synchronized. Cause: No version synchronization checkpoint was set in the revision step, and the receipt was not checked during handover.
- Phenomenon: The course syllabus lacks the responsible person's signature or the handover record lacks a receipt, so the materials cannot be issued. Cause: Drafting and handover did not verify item by item according to the complete-field requirement, and missing items were not blocked.
How to verify the setup
Feature acceptance: Ask two consecutive follow-up questions and see whether the second question carries forward the reference from the first question, and check the passing of chatId, messages, and variables in the session.
Business test: Draft one copy according to the template and complete one handover, and see whether missing items are blocked.
- Check the current value of memory turns in the app settings, confirm that it matches the preceding text range required by the question, and compare the usage records of two runs.
- Check the name, quantity, date, version, and signature item by item according to the program plan, course syllabus, and credit structure table, and after confirming that missing items are blocked, hand it to the next stage for sign-off.