What this category's data looks like
This category's data looks like this: National Key R&D Program project applications involve three types of materials: the project application, the budget application, and the cooperation agreement. The project application focuses on research content, technical route, and assessment indicators; the budget application focuses on funding composition, subject amounts, and calculation basis; the cooperation agreement focuses on task division, intellectual property, and signature pages. When these three types of materials enter the model access and configuration stage, each plays a different role: the project application provides research tasks and indicator definitions, the budget application provides budget subjects and amount definitions, and the cooperation agreement provides partner names, task division, and signature information. The material sources are drafts and attachments submitted by each participating unit, the update rhythm is multiple rounds of revision during the application window, and the field characteristics are concentrated in names, quantities, dates, signatures, and version numbers, which need to be aligned item by item before entering drafting and handover.
Configuration and implementation checks
This step is executed by the server-side model channel configuration, outputting model binding relationships and channel responses. "Issuable material drafts and handover records" are completed afterward by subsequent AI nodes, code nodes, or manual work. The five types of models—language, indexing, reranking, speech synthesis, and speech recognition—are bound to their corresponding stages respectively. The configuration result only determines the invocation relationships and responses, not the material content or permissions.
| Object | Check | Verification action |
|---|---|---|
| Project application | Names, quantities, dates, and signatures must be consistent with the budget application and cooperation agreement | Compare the participating unit names, task quantities, start and end dates, and signature pages of the three materials item by item; if a signature or receipt is missing, stop it |
| Budget application | Budget subject amounts and calculation definitions must correspond to the tasks in the project application | Check whether the subject names, amounts, calculation explanations, and project application task numbers correspond one to one; version numbers and dates must be synchronized |
| Cooperation agreement | Partner names, task division, and intellectual property clauses must be consistent with the application | Check the signatures and receipts on the signature page, and confirm that names, task quantities, and dates do not conflict with the application and budget |
| Model binding relationships | Language, indexing, reranking, speech synthesis, and speech recognition are bound to their corresponding stages respectively | In the model configuration, check the type labels, channel and key sources, and model identifiers, and verify whether the values of maxContext, maxTokens, quoteMaxToken, and toolChoice are consistent with the documentation |
Three common errors
- Symptom: the same participating unit has inconsistent names in the project application and cooperation agreement. Cause: the two materials were drafted separately, name and date alignment was not done, and receipts were missing at handover.
- Symptom: the budget application amount does not match the number of tasks in the project application. Cause: versions were not synchronized; after revision, only one material was changed while the other remained the old version.
- Symptom: retrieval reports indexing model-related errors or authentication failures. Cause: the channel and key are inconsistent with the accessed service, and the model identifier does not match the name listed in the documentation.
How to verify the setup
This feature acceptance: run one conversation and one retrieval, check the model identifiers and binding relationships in the responses, and confirm that the language model and indexing model correspond to the correct stages respectively.
Business test: draft one document according to the template and complete one handover, and see whether missing items are stopped.
- Check the model identifier against the model name returned by the channel, and confirm it is consistent with the name listed in the documentation.
- Check the channel configuration and key source, and confirm they are consistent with the accessed service.