What this category's data looks like
The business basis query for undergraduate program revision draws materials from three types of local materials: program plans, course syllabi, and credit structure tables. The update cadence is to synchronize versions and signed receipts after each round of revision. Program plans carry total credits and course module fields; course syllabi carry course names, credits, class hours, and signatures; credit structure tables carry the credit quantities of each category and dates. When materials enter this feature, the program plan serves as the primary basis, while course syllabi and credit structure tables serve as cross-check sources, jointly supporting basis entries that can be traced back to the original text. Field characteristics include course names, credit quantities, effective dates, and signature status. A common inconsistency is that the name, quantity, or date of the same record does not match across two materials.
Configuration and implementation checks
This part is executed by application settings (response limit, etc.), which output the length of a single answer and the range of context that can be accommodated. Basis entries that can be traced back to the original text are then completed by the model, while entry and authorization are handled by the publishing service and file permissions. The response limit is controlled by a slider for the length of a single answer. If set too low, the answer will be truncated; if set too high, consumption will increase.
| Object | Check | Verification action |
|---|---|---|
| Response limit | Matches the answer length required by the page | Check the switch and slider position in application settings, and confirm the maxResponse value |
| Program plan | Course names, credit quantities, effective dates, and signature status match the original text | Compare course names, credit quantities, dates, and signatures one by one, and record the quoteMaxToken budget |
| Course syllabus | Course names, credits, class hours, and signatures match the program plan | Check whether the name, quantity, and date of the same course are consistent across the two materials |
| Credit structure table | Credit quantities, dates, and signatures of each category match the program plan | Check credit quantities and dates, inspect for missing signatures or receipts, and record the maxContext range |
Three common errors
- Symptom: The name, quantity, or date of the same record does not match across two materials. Cause: The program plan and course syllabus were not revised in sync, so field sources are out of sync.
- Symptom: The version is not synchronized, and the basis entry points to an old version. Cause: After revision, the effective date and version identifier were not updated, and the material is still from the previous round.
- Symptom: Signatures or receipts are missing, and the basis entry cannot be traced back. Cause: The material circulation step did not complete signatures and receipts, so the entry lacks a verifiable source.
How to verify the setup
This feature's acceptance check: ask a question that requires a long answer, see whether the ending is complete, and check the settings of maxResponse and maxContext.
Business test: ask a basis question that spans materials, and see whether the answer provides a traceable source.
- Check the response limit switch and slider position in application settings, and ask a question that requires a long answer to see whether the ending is complete.
- Compare usage between two runs, check the change in single-run usage after adjusting the limit, and inspect whether the tokens of the quoted text and the number of array items are recorded separately.