What this category's data looks like
This page addresses the vocational school student internship management scenario, with materials drawn from three categories: internship agreements, internship plans, and internship logs. Agreements are signed by three parties—the school, the enterprise, and the student—and then archived, with the update cadence adjusted per batch; plans are compiled by supervising teachers per semester, with versions revised as positions change; logs are filled in by students daily, with dates and signatures. When the three material categories enter the material verification and discrepancy localization function, agreements take the role of the baseline ledger, plans take the role of task-and-time cross-reference, and logs take the role of process records. Field characteristics concentrate in four categories: name, quantity, date, and signature. The same object is often written with a mix of abbreviations and full names across different materials, date formats are not uniform, and when signatures and receipts are missing it is difficult to judge directly. The verification goal is that the name, quantity, and date of the same object are consistent across two materials, and the discrepancy list is handed to the reviewer for confirmation and written back.
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 is controlled by a slider that sets the length of a single answer; if set too low the answer will be truncated, and if set too high consumption will increase; the number of quotes and quoteMaxToken are each independent—the number of quotes is the array length, and quoteMaxToken is the budget for quoted content, and the two are not compared for equality.
| Object | Check | Verification action |
|---|---|---|
| Internship agreement | The name, quantity, and date of the same object are consistent across two materials, and signatures and receipts are complete | In application settings, check the response limit switch and slider position, compare the name, quantity, and date fields of the agreement and the ledger, and check the signature column and receipts; when long answers are involved, note the effect of maxResponse on the ending |
| Internship plan | The dates and position names in the plan correspond item by item with the agreement and logs, and version numbers are in sync | Compare the dates and names of the plan and the agreement item by item, and check whether version numbers are consistent; when verifying long text, observe whether the coordination of maxContext and maxResponse keeps the ending complete |
| Internship log | The log's dates, quantities, and signatures are consistent with the plan and agreement, with no missing signatures or receipts | Sort by date and compare the names and quantities of the logs with the plan and agreement, and mark records missing signatures or receipts; record the number of quotes separately, and use quoteMaxToken only to check the tokens of quoted text |
| Discrepancy list | Discrepancy fields are located to the specific material and row, and handed to the reviewer for confirmation and write-back | Summarize inconsistent items in name, quantity, and date and items whose versions are not in sync, mark missing signatures or receipts, form a list, hand it to the reviewer for confirmation, and then write it back to the ledger |
Three common errors
- Symptom: the same record has different name spellings in the agreement and the log, and the quantity and date also do not match. Cause: abbreviations and full names are mixed, date formats are not unified, and field-by-field comparison was not performed.
- Symptom: the plan has been revised, but the log and agreement still reference the old version, and the discrepancy list omits items. Cause: versions are not in sync, material update cadences are inconsistent, and version numbers were not checked during verification.
- Symptom: the log is missing a signature or receipt, and the discrepancy list cannot locate the responsible field. Cause: signatures and receipts were not archived with the materials, and the verification action only compared fields without checking the signature column.
How to verify the setup
This function's acceptance: ask a question that requires a long answer and see whether the ending is complete; if it breaks off in the middle of a sentence, check the response limit slider position and the maxResponse setting, then compare usage across two runs.
Business test: use one real record to find fields inconsistent with the ledger, record discrepancies in name, quantity, date, and signature, hand them to the reviewer for confirmation, and write them back.
- In application settings, check the response limit switch and slider position, observe whether the ending of a longer answer is complete, and compare usage changes across two runs.
- Sort by date and compare the names, quantities, dates, and signatures of the agreement, plan, and log, mark items whose versions are not in sync and items missing signatures or receipts, and form a discrepancy list.