What this category's data looks like
During the admissions season, college admissions physical examination organization centrally processes three types of materials: physical examination forms, re-examination applications, and restricted-major notifications. Physical examination forms come from various examination stations and are aggregated by batch; their fields include name, candidate number, physical examination conclusion, restriction code, date, and physician signature. Re-examination applications are submitted by candidates or middle schools; their fields include application reason, original examination date, re-examination items, and receipt. Restricted-major notifications are generated by the admissions office based on the conclusion; their fields include major name, restriction basis, notification date, and candidate acknowledgment. The three types of materials update at different rhythms: physical examination forms roll forward with batches, re-examination applications enter immediately on a case-by-case basis, and notifications are written back in bulk according to admission milestones. When materials enter the verification function, physical examination forms serve as the baseline ledger, while re-examination applications and notifications serve as objects to be verified, each providing name, quantity, date, and signature fields for item-by-item comparison and discrepancy localization.
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. The response limit uses a slider to control the length of a single answer; if set too low, the answer will be truncated, and if set too high, consumption will increase. The context range is jointly defined by maxContext and maxResponse, and the quoted content budget is controlled separately by quoteMaxToken.
| Object | Check | Verification action |
|---|---|---|
| Physical examination form | The name, quantity, and date of the same record are consistent between the physical examination form and the re-examination application | Check name, candidate number, physical examination conclusion, restriction code, date, and physician signature, and compare field by field |
| Re-examination application | The application reason, original examination date, re-examination items, and receipt are complete, and the version is synchronized with the ledger | Check the application reason, original examination date, re-examination items, and receipt, and inspect for missing signatures or receipts |
| Restricted-major notification | The major name, restriction basis, notification date, and candidate acknowledgment are consistent with the conclusion | Check the major name, restriction basis, notification date, and acknowledgment, and confirm items whose versions are not synchronized |
| Context and token | The length of a single answer matches the range of context that can be accommodated and the page requirements | In application settings, check the response limit switch and slider position, and record maxContext, quoteMaxToken, and maxResponse |
Three common errors
- Symptom: The name or candidate number of the same candidate does not match between the physical examination form and the re-examination application. Cause: The ledger fields were not used to backfill during entry, and the discrepancy was not localized.
- Symptom: The major name in the restricted-major notification is not synchronized with the version of the physical examination conclusion. Cause: The notification was generated in bulk based on the old conclusion and was not written back with the re-examination result.
- Symptom: The re-examination application lacks a signature or receipt, and the notification lacks candidate acknowledgment. Cause: Receipts were not fully collected at the material circulation nodes, and missing items were not marked during verification.
How to verify the setup
This function's acceptance: ask a question that requires a long answer, see whether the ending is complete, confirm that the response limit matches maxResponse and the page requirements, and that the answer does not break off in the middle of a sentence.
Business test: use one real record to find fields inconsistent with the ledger, write them into the discrepancy list, and after confirmation by the reviewer, write them back.
- In application settings, check the response limit switch and slider position, and compare the usage changes between two runs
- Check the tokens of the quoted text against
quoteMaxToken, record the number of array items separately, and do not compare it for equality with the budget