What this category's data looks like
This category's data in the signing stage of research project task books includes project task books, subject task breakdown tables, and budget books. The task book provides research objectives, assessment indicators, and the signature page; the breakdown table gives subject names, undertaking units, start and end dates, and responsible persons; the budget book lists subject amounts, calculation bases, and approval signatures. The materials come from the project application and approval process, are updated intensively during the signing stage, and versions iterate with approval nodes. The field characteristics are dense multilingual terminology, the same record reused across materials, and date and signature fields that must be closed. When entering the model access and configuration function, the task book and breakdown table are used to extract terminology context, and the budget book is used to check the consistency of names, quantities, and dates; together the three support the generation of a unified terminology list and a comparison draft.
Configuration and implementation checks
This step is executed by the server-side model channel configuration, outputting model binding relationships and channel responses. The "unified terminology list and comparison draft" is then completed by subsequent AI nodes, code nodes, or manual work. Models are divided into five categories: language, indexed, rerank, speech synthesis, and speech recognition, and different steps bind different model types.
| Object | Check | Verification action |
|---|---|---|
| Project task book | Terminology names and assessment indicators must correspond item by item with the breakdown table and budget book, and date and signature fields must not be blank | Check the subject names, start and end dates, and signature page in the task book, and confirm they are consistent with the breakdown table and budget book |
| Subject task breakdown table | Subject names, undertaking units, quantities, and dates must be traceable back to the original text of the task book, and version numbers must be synchronized | Compare the same record in the breakdown table and the task book, and check whether names, quantities, and dates match |
| Budget book | Subject amounts and calculation bases must be consistent with the task book and breakdown table, and approval signatures and receipts must be complete | Check the budget book subjects against the corresponding items in the task book and breakdown table, and check whether signatures and receipts are complete |
| Model channel configuration | Model types correspond to the steps to be used, channels and keys are consistent with the connected service, and model identifiers are consistent with the names listed in the documentation | In the model configuration, check the type labels, check the channel configuration and key source, and compare against the model name returned by the channel; when references are involved, check the quoteMaxToken budget, record the array count separately, and confirm the values of maxContext, maxTokens, and toolChoice |
Three common errors
- Symptom: the same subject name is written differently in the task book and the breakdown table. Cause: terminology is not unified, the two materials are maintained separately, and there is no comparison draft tracing back to the original text.
- Symptom: the budget book amount does not match the task book quantity, and versions are not synchronized. Cause: after an approval node update, the other material was not written back, and the old version continued to circulate.
- Symptom: the signature page or receipt is missing, and the materials cannot be archived. Cause: the signing process is not closed, and there is no signature and receipt verification step.
How to verify the setup
This function's acceptance: run one conversation and one retrieval, check the model identifier in the response, confirm it is consistent with the model name returned by the channel, and check that the quoteMaxToken reference budget and the array count are recorded separately.
Business test: sample three terms and check whether their spelling is consistent throughout the entire text
- In the model configuration, check the type labels and confirm that language, indexed, rerank, speech synthesis, and speech recognition are each bound to the corresponding step.
- Check the channel configuration and key source, confirm that the channel is consistent with the connected service, and check the model identifier against the model name returned by the channel.