What this category's data looks like
This category's data involves three types of materials: annual progress reports, mid-term review materials, and acceptance reports. Annual progress reports are submitted on an annual cycle, with fields including project name, undertaking unit, start and end dates, budget execution, number of outputs, and signature of the person in charge; mid-term review materials are updated by milestone, focusing on stage indicators, personnel changes, budget milestones, expert opinions, and receipts; acceptance reports are consolidated at project closure, with fields including final name, quantity, date, signatures, and attachment list. When these three types of materials enter the material verification and discrepancy localization function, the annual progress report serves as the baseline ledger, the mid-term review materials serve as the stage comparison, and the acceptance report serves as the final-state verification. The update rhythm is annual submission, milestone supplementation, and closure consolidation. The field characteristic is that the same object differs across materials in name wording, quantity caliber, date format, and signature position, requiring field-by-field comparison.
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 for the length of a single answer; if set too low, the answer will be truncated, and if set too high, consumption will increase.
| Object | Check | Verification action |
|---|---|---|
| Annual progress report | Project name, quantity, and date are consistent with the ledger, and signatures are complete | Check the switch and slider position in application settings, extract fields and compare them item by item with the ledger, and record the answer length corresponding to maxResponse |
| Mid-term review materials | Stage indicators, dates, signatures, and receipts do not conflict with the annual progress report | Compare the name, quantity, and date of the same record in the two materials, record discrepancies, and check the range of context that can be accommodated by maxContext |
| Acceptance report | Final name, quantity, date, signatures, and attachment list are complete | Check whether versions are synchronized, inspect for missing signatures or receipts, mark fields pending review, and record the reference content budget corresponding to quoteMaxToken |
| maxResponse | The length of a single answer matches the answer length required by the page | Ask a question that requires a long answer, see whether the ending is complete, and compare usage across two runs |
Three common errors
- Symptom: the same record has different name wording in the annual progress report and the acceptance report. Cause: versions are not synchronized and field calibers are not unified, causing omissions in the discrepancy list.
- Symptom: the quantity and date in the mid-term review materials and the acceptance report do not match. Cause: stage updates were not written back to the ledger, and the two materials were filled in independently.
- Symptom: the acceptance report lacks signatures or receipts, and the discrepancy list cannot be closed. Cause: the signature page was not synchronized with the version, and the reviewer archived it without confirmation.
How to verify the setup
Acceptance of this function: ask a question that requires a long answer, see whether the ending is complete, confirm that the length of a single answer and the range of context that can be accommodated meet the page requirements, and check the values of maxResponse and maxContext.
Business test: use a real record to find fields inconsistent with the ledger, record discrepancies in name, quantity, and date, and submit them to the reviewer for confirmation and write-back.
- Check the switch and slider position of the response limit in application settings, confirm that it matches the answer length required by the page, and record the current value of
maxResponse. - Compare usage across two runs, check the change in single-run usage after adjusting the limit, avoid answers breaking off mid-sentence, and check
quoteMaxTokenand the number of references and record them separately.