What this category's data looks like
This category's data covers three types of materials: school operation licenses, course filing materials, and fee disclosure. The school operation license comes from the approving authority and includes the institution name, address, validity period, scope of operation, and signature and seal; course filing materials are submitted by the teaching department by class session and include the course name, class hours, instructor, start date, and signature of the person in charge; fee disclosure is updated periodically by the finance or enrollment department and includes fee items, standards, refund rules, and disclosure date. The three types of materials enter the same verification process, each playing a different role: the license provides subject qualification and scope of operation, course filing provides teaching arrangements and timeline, and fee disclosure provides funding and refund criteria. In terms of update cadence, the license is triggered by license renewal or changes, course filing rolls over by semester or class session, and fee disclosure is adjusted by fee cycle. Field characteristics center on names, quantities, dates, signatures, and receipts. The same object often shows discrepancies between two materials due to unsynchronized versions or different criteria, requiring field-by-field localization and the formation of a discrepancy list.
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. The "discrepancy list" is then completed by the model, and entry and authorization are handled by the publishing service and file permissions.
| Object | Check | Verification action |
|---|---|---|
| School operation license | Whether the institution name, address, validity period, and signature and seal are consistent with the course filing materials | Compare the names and dates of the two materials field by field, record inconsistent items, and note the field locations |
| Course filing materials | Whether the course name, class hours, instructor, and start date are consistent with the corresponding records in the fee disclosure | Extract one record by class session, verify the quantity and dates, and check whether the signature of the person in charge and the receipt are complete |
| Fee disclosure | Whether the fee items, standards, refund rules, and disclosure date are synchronized with the ledger version | Verify the disclosure date and version number, confirm whether signatures or receipts are missing, and write them into the discrepancy list |
| Discrepancy list | Whether the names, quantities, and dates of the same object match across the two materials | Summarize inconsistent fields, submit them to the reviewer for confirmation and write back; verify the scope of use of maxResponse, maxContext, and quoteMaxToken |
Three common errors
- Symptom: The names of the same record do not match across the two materials. Cause: Course filing materials and fee disclosure each maintain their own names, and unsynchronized versions lead to field discrepancies.
- Symptom: Quantities or dates are inconsistent across the two materials. Cause: Course filing is updated on a rolling basis by class session, while fee disclosure is adjusted by fee cycle, so the time criteria are not aligned.
- Symptom: Materials are missing signatures or receipts. Cause: The submission step did not check signatures and receipts item by item, so the discrepancy list cannot be fully written back to the reviewer.
How to verify the setup
Feature acceptance: Ask a question that requires a long answer, check whether the ending is complete, and confirm that the response limit and truncation behavior match the page requirements.
Business test: Use a real record to find fields inconsistent with the ledger, write them into the discrepancy list, and submit them to the reviewer for confirmation.
- In the application settings, check the response limit switch and slider position, and confirm that the single-answer length matches the page requirements.
- Compare usage across two runs to confirm the change in single-run usage after adjusting the limit; verify the applicable scope of
maxResponse,maxContext, andquoteMaxToken.