What this category's data looks like
This category covers observation records, area plans, material placement lists, activity goal achievement records, and reflection-to-next-week plans. Materials come from daily class observations and area activity traces, updated on a rolling weekly plan basis, with field characteristics concentrated in three places: responsible person, version, and date. When materials enter the model access and configuration function, the correspondence between observation records and area plans serves as the retrieval source, material placement quantities and goal achievement records serve as the draft basis, and reflection-to-next-week plans serve as the handover destination. Model binding relationships determine which type of model processes these materials, and channel responses determine whether calls succeed; the readable scope of the materials themselves is still determined by knowledge base permissions and is unrelated to channel keys.
Configuration and implementation checks
This step is executed by the server-side model channel configuration, outputting model binding relationships and channel responses. "Material drafts and handover records that can be issued" are completed subsequently by AI nodes, code nodes, or manual work. The five types of models—language, indexing, reranking, speech synthesis, and speech recognition—correspond to different stages respectively, and binding relationships and response results must be checked item by item.
| Object | Check | Verification action |
|---|---|---|
| Observation records and area plans | Whether the correspondence between the two is consistent, and whether insufficient materials and mismatched goals can be exposed during the drafting stage | Check observation records item by item against the area plan, and examine whether material placement quantities and activity goals support each other |
| Material draft fields | Whether the responsible person, version, and date are complete, and whether missing items can be blocked | Draft one according to the template, check the responsible person, version, and date field by field, and verify whether the values of maxContext and maxTokens match the model used |
| Model binding relationships | Whether the three types of models—language, indexing, and reranking—are bound to the corresponding stages | Check the type annotations in the model configuration, verify the model identifiers against the model names returned by the channel, and confirm in the retrieval stage that both the indexing model and the reranking model are bound |
| Handover records | Whether the recipient, receipt time, and previous stage version are connected | Complete one handover, check the receipt fields and version date, and verify whether toolChoice and quoteMaxToken take effect in the retrieval and dialogue stages |
Three common errors
- Symptom: Material placement quantities do not match the area plan, and the quantity column in the draft is blank. Cause: The area plan was not reviewed during drafting, and insufficient materials were not blocked.
- Symptom: The activity goal achievement record is inconsistent with the observation record description, and it is returned after handover. Cause: Goals and observations do not match, and no corresponding check was made during the drafting stage.
- Symptom: The reflection-to-next-week plan is still the previous version, and the date and responsible person have not been updated. Cause: The plan was not updated, and the version and date were not checked item by item during handover.
How to verify the setup
This function's acceptance: run one dialogue and one retrieval, check whether the model identifiers in the responses are consistent with the names listed in the documentation, and confirm that the language model and indexing model are bound to the corresponding stages respectively.
Business test: draft one according to the template and complete one handover, and see whether missing items are blocked.
- Check the model type annotations, channel and key sources, and model identifiers item by item in the model configuration, and confirm that the three types of information are consistent with the connected service.
- During drafting, check observation records and material placement quantities against the area plan; during handover, check the recipient, version, and date, and separately record the tokens and array count of the quoted text.