What this category's data looks like
For the business basis query of kindergarten play activity organization, the materials come from the kindergarten's own observation records, area activity plans, material placement lists, activity objectives, and reflections converted into next week's plans. These materials are updated weekly or by theme, and the fields include date, area, material quantity, objective items, observation descriptions, and reflection conclusions. After entering model integration and configuration, observation records and area plans serve as retrieval corpus, the material placement list is used to check quantities, activity objectives are used to compare achievement, and reflections converted into next week's plans are used to track plan updates. The language model is responsible for dialogue generation, the indexing model is responsible for text chunk indexing, and the reranking model optimizes retrieval ranking. Each material has a different role: observation records provide source traceability, area plans provide version checking, material lists provide quantity comparison, and objectives and reflections provide cross-material linkage.
Configuration and implementation checks
The server-side model channel configuration only outputs the model binding relationships and channel responses; the basis items that can be traced back to the source text must be handled next by dialogue and retrieval. Different stages bind different model types: the retrieval stage requires an indexing model, and the dialogue stage requires a language model.
| Object | Check | Verification action |
|---|---|---|
| Observation records and area plans | The correspondence must be traceable item by item to the source text; if the plan is not updated, the basis becomes invalid | Check the observation date and area plan version, and confirm that the items match the source text |
| Material placement quantity | The quantity must be consistent with the list; if materials are insufficient, the activity objectives are difficult to achieve | Compare the list quantity with the observation description, and record the gap items |
| Activity objectives and observations | Objective achievement must be supported by observations; if the objectives and observations do not match, the basis does not hold | Compare objective items with observation descriptions one by one, and mark mismatches |
| Model type and stage | The type label must correspond to the stage of use; if retrieval reports an indexing-model-related error, the binding is incorrect | Check the type label in the model configuration, and inspect the model name returned by the channel |
Three common errors
- Phenomenon: the basis items returned by retrieval do not match the source text. Cause: the observation records and area plan versions are inconsistent, the plan has not been updated, and old items are still indexed.
- Phenomenon: activity objective items lack observational support. Cause: the objectives and observations do not match, the material placement quantity is insufficient, and the observation descriptions do not cover the objectives.
- Phenomenon: after changing models, the answer style changes abruptly, and the quoted content exceeds the budget. Cause: the model identifier is inconsistent with the name listed in the documentation, and
quoteMaxTokenhas not been checked against the tokens of the quoted text.
How to verify the setup
Acceptance for this feature: run one dialogue and one retrieval, check the model identifier in the response, confirm it is consistent with the name listed in the documentation, and check the values of maxContext, maxTokens, and quoteMaxToken.
Business test: ask a cross-material basis question, see whether the answer provides traceable sources, and confirm that the number of quoted items and the tokens of the quoted text are recorded separately.
- In the model configuration, check that the model type label corresponds to the stage of use, and inspect the channel configuration and key source.
- Compare observation records with area plans, material placement quantities, and activity objectives one by one, mark mismatches, and trace them back to the source text.