What this category's data looks like
This category's data covers three types of materials: program plans, course syllabi, and credit structure tables. A program plan contains the major name, course modules, credit requirements, and revision date; a course syllabus contains the course name, class hours, assessment method, and author signature; a credit structure table contains the credit count, proportion, and review receipt for each module. The materials come from academic affairs system exports and departmental submissions, and the update cadence is synchronized by revision batch. When entering the authorized access and external services feature, the program plan serves as the main record carrying the visible scope of the external entry point, while course syllabi and credit structure tables are displayed as attachments following the main record. When parents or higher-level authorities access, only published versions and the corresponding signature receipts are visible; unsynchronized versions and missing signature items do not enter the visible scope. Field verification focuses on consistency of names, quantities, dates, and signatures.
Configuration and implementation checks
This part is executed by the memory turns and prompt configuration in the app settings, outputting the referenced historical message range and answer constraints. The externally available entry points and authorization scope are determined by the publishing service and file permissions, and the model only processes filtered materials. The publishing service and file permissions handle the actual entry points and authentication, and the model answers accordingly.
| Object | Check | Verification action |
|---|---|---|
| Program plan | Names, dates, and signatures are consistent across versions, and match the course syllabi and credit structure table | Check the current value of memory turns in the app settings, run a trial with two consecutive follow-up questions, and check whether the second round carries over the references from the first round; inspect the records corresponding to messages and chatId |
| Course syllabus | Course names, class hour counts, and assessment methods are consistent across the two materials, and the author signature and receipt are complete | Compare the course names, quantities, and dates in the program plan and course syllabus; check whether the signature field and receipt are missing; verify the version identifier passed in variables |
| Credit structure table | The credit counts and proportions of each module are consistent between the program plan and the structure table, and the review signature and date are synchronized | Compare the credit counts and dates in the two materials; confirm version synchronization; access once with a restricted identity and see whether the visible scope matches the settings |
| Memory turns | Matches the preceding context range required by the question, and running consumption changes accordingly after the turn count is adjusted | Check the current value in the app settings; run a trial with two consecutive questions; compare the usage records of the two runs |
Three common errors
- Symptom: the name and quantity of the same course do not match between the program plan and the course syllabus. Cause: revision batches are not synchronized, the two materials are updated separately, and no cross-check was performed.
- Symptom: the version of the credit structure table is not synchronized, and dates and signatures are missing. Cause: the old structure table was submitted together with the new program plan, and the receipt was not completed.
- Symptom: when the second question uses a reference, the answer misses the point, and responses become slower with higher consumption. Cause: the memory turn count is too large and brings in irrelevant preceding text, or the opening message is treated as preceding text.
How to verify the setup
Feature acceptance: ask two consecutive follow-up questions and see whether the second question carries over the references from the first; check the records corresponding to messages and chatId, and confirm that the version identifier passed in variables matches the visible scope.
Business test: access once with a restricted identity and see whether the visible scope matches the settings.
- Check the current value of memory turns in the app settings, run a trial with two consecutive questions, and confirm that the second round carries over the references from the first round.
- Compare the names, quantities, dates, and signatures of the program plan, course syllabi, and credit structure table, and confirm that versions are synchronized and receipts are complete.