What this category's data looks like
This page centers on the scenario of annual progress and acceptance of research projects; the materials include annual progress reports, mid-term review materials, and acceptance reports. Annual progress reports are submitted at annual milestones, with fields including project name, principal investigator, start and end dates, phase objectives, budget execution, and signatures; mid-term review materials are updated according to the review cycle, with fields including indicator completion amounts, milestones, issue lists, and review comments; acceptance reports are formed at project closure, with fields including deliverable lists, test conclusions, dates, and multi-party signatures. When these three types of materials enter this feature, the annual progress report serves as the phase basis, the mid-term review materials serve as the process verification basis, and the acceptance report serves as the final conclusion basis. The update cadence is synchronized with project milestones, and the currently effective version prevails. Field characteristics are concentrated in names, quantities, dates, signatures, and receipts; cross-material comparison requires referring back to the original text entries.
Configuration and implementation checks
This part is executed by application settings (response limit, etc.), which determine the length of a single answer and the range of context that can be accommodated. "Basis entries that can be traced back to the original text" are 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.
| Object | Check | Verification action |
|---|---|---|
| Response limit | Matches the answer length required by the page | Check the switch and slider position in application settings, and confirm how maxResponse works with maxContext and quoteMaxToken |
| Annual progress report | Fields, dates, and signatures are complete, and it is the currently effective version | Check the project name, principal investigator, start and end dates, phase objectives, and signatures, and refer back to the original text entries |
| Mid-term review materials | Indicator completion amounts, milestones, and review comments match the original text | Check quantities, dates, and review comments, record the number of cited entries, and separately check the quoteMaxToken budget |
| Acceptance report | Deliverable list, test conclusions, dates, and multi-party signatures are consistent | Check deliverable names, quantities, dates, and signature receipts, and confirm there is no conflict with the annual progress report or mid-term review materials |
Three common errors
- Symptom: the name and quantity of the same record do not match between the annual progress report and the acceptance report. Cause: the two materials are updated separately, and no cross-material back-reference comparison was performed.
- Symptom: the version of the mid-term review materials is not synchronized, and old-version entries are cited. Cause: the currently effective version is not marked, and the model answers based on the old text.
- Symptom: the acceptance report lacks signatures or receipts, and entries cannot be traced back. Cause: material archiving is incomplete, and the basis entries lack a verifiable original text location.
How to verify the setup
Feature acceptance: ask a question that requires a long answer, see whether the ending is complete, and confirm that the response limit matches the truncation behavior.
Business test: ask a cross-material basis question, see whether the answer provides traceable sources, and check the number of cited entries against the quoteMaxToken budget.
- Check the response limit switch and slider position in application settings, and compare the usage changes between two runs.
- Check the annual progress report, mid-term review materials, and acceptance report item by item for names, quantities, dates, and signatures, and mark the currently effective version.