What this category's data looks like
This page focuses on field consistency in material verification and discrepancy localization for primary and secondary school enrollment organizations. Material sources include enrollment plans, application material checklists, and admission lists; the update cadence advances with the enrollment season and is replaced version by version. Common fields include student name, application serial number, ID number, planned number, admitted number, date, and signed receipt. The three types of materials play different roles when entering this feature: the enrollment plan provides rules and time nodes, the application material checklist provides required fields and receipt requirements, and the admission list provides actual admission records. Discrepancy localization uses the same object as an anchor, comparing whether the names, quantities, and dates in the two materials are consistent, and outputs a discrepancy list for the reviewer to confirm and write back to the ledger.
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 |
|---|---|---|
| Enrollment plan | Whether the fields, dates, and signatures correspond to the application material checklist and admission list | Check the planned number, time nodes, and signature fields in the plan, and record fields inconsistent with the ledger |
| Application material checklist | Whether the name, quantity, and date of the same record are consistent with the admission list | Compare name, ID number, and receipt date item by item, and mark records missing signatures or receipts |
| Admission list | Whether the version is synchronized, and whether the quantity and date are consistent with the ledger | Check the list version number and date, and confirm entries whose name, quantity, or date do not match |
| Discrepancy list | Whether the output covers all inconsistent fields and can be written back for review | In application settings, check the position of the response limit slider, and confirm that the values of maxResponse, maxContext, and quoteMaxToken match the page requirements |
Three common errors
- Symptom: the name or ID number of the same student does not match between the plan and the admission list. Cause: during entry, comparison was not performed using the same object as an anchor, and the two materials were maintained separately.
- Symptom: there is a discrepancy between the quantity in the application material checklist and the quantity in the admission list. Cause: the versions were not synchronized, and the old checklist was not updated with the admission results.
- Symptom: the receipt or signature field is missing, and the discrepancy list cannot be submitted to the reviewer for confirmation. Cause: the material collection step did not verify the completeness of signatures and receipts.
How to verify the setup
Feature acceptance: ask a question that requires a long answer and see whether the ending is complete; if it cuts off in the middle of a sentence, check whether the response limit slider is too low, and verify the values of maxResponse, maxContext, and quoteMaxToken.
Business test: use one real record to find fields inconsistent with the ledger, mark entries whose name, quantity, or date do not match, and submit them to the reviewer for confirmation and write-back.
- In application settings, check the response limit switch and slider position so that the answer length matches the length of the discrepancy list
- Compare usage between two runs to confirm that the change in single-run usage after adjusting the limit is within the expected range