What this category's data looks like
This page addresses the scenario of annual progress and acceptance of research projects. The materials cover three categories: annual progress reports, mid-term review materials, and acceptance reports. The sources are the original records and supporting attachments submitted by the project team at cycle nodes, and the update cadence follows node rollovers and rectification backfilling. Field characteristics center on name, quantity, date, version number, signature, and receipt: annual progress reports emphasize phase tasks and budget execution, mid-term review materials emphasize indicator achievement and adjustment explanations, and acceptance reports emphasize conclusive data and the signature chain. When the three material types enter the dialogue function, the annual progress report provides baseline fields, the mid-term review materials provide the basis for deviations and corrections, and the acceptance report provides the final-caliber statement. Together they constrain the consistency of the same record in name, quantity, and date, and support the generation of issuable material drafts and handover records.
Configuration and implementation checks
This part is executed by the memory turn count and prompt configuration in the application settings, and the output references the historical message range and answer constraints. "Issuable material drafts and handover records" are then completed by the model. The memory turn count controls how many previous dialogue turns can be referenced at most when answering. If the value is too small, the preceding text cannot be used; if the value is too large, irrelevant content is brought in and consumption increases.
| Object | Check | Verification action |
|---|---|---|
| Memory turn count | Matches the range of preceding text required by the annual progress report, mid-term review materials, and acceptance report | Check the current value in the application settings, and run a trial with two consecutive follow-up questions to confirm that the second round can carry forward the references from the first round |
| Annual progress report | Fields are complete, the responsible person is clear, the version and date are consistent, and the name, quantity, and date match those in the mid-term review materials | Draft one according to the template, and check whether the historical turns referenced in messages cover the fields of the previous version and whether missing items are blocked |
| Mid-term review materials | The name, quantity, and date of the same record in the annual progress report and acceptance report are consistent, and the version number is synchronized | Compare the corresponding fields of the two materials, and check whether chatId and variables are correctly brought in with the session |
| Acceptance report | Signatures and receipts are complete, and the conclusive data and the deviation explanations in the mid-term review materials are traceable | Complete one handover, check whether the handover record contains the responsible person, date, and version, and whether missing signatures or receipts are blocked |
Three common errors
- Phenomenon: The name, quantity, and date of the same record do not match between the annual progress report and the acceptance report. Cause: The two dialogue rounds reference different historical message ranges, and the baseline fields are not aligned.
- Phenomenon: The mid-term review materials have been changed, but the annual progress report still uses the old version. Cause: The memory turn count brings in earlier turns, and the version is not synchronized to the current session.
- Phenomenon: The handover record lacks a signature or receipt, but the material is still treated as issuable. Cause: The answer constraints do not cover the signature fields, and missing items are not blocked.
How to verify the setup
Acceptance of this feature: Ask two consecutive follow-up questions, see whether the second question carries forward the references from the first question, and check whether the historical message range referenced in messages matches the required preceding text.
Business test: Draft one according to the template and complete one handover, and see whether missing items are blocked.
- Check the current value of the memory turn count in the application settings, run a trial with two consecutive question sentences, and confirm that the second round correctly carries forward the references from the first round.
- Compare the usage records of two runs, confirm that usage changes accordingly after the turn count is adjusted, and check whether
chatIdandvariablesare correctly brought in with the session.