What this category's data looks like
In the course selection, scheduling, and classroom resource allocation scenario, material drafting and responsibility handover revolve around three types of materials: course offering plans, scheduling tables, and course selection rules. The course offering plan provides the course name, offering unit, semester, and planned number of classes, and is the source of scheduling and course selection; the scheduling table carries the class, teacher, week, period, and classroom number, and is the evidence of resource occupancy; the course selection rules specify the selection target, capacity, time window, and adjustment conditions. The three types of materials are updated according to the semester rhythm: first set the plan, then schedule, then publish the rules, and every adjustment must leave a version and date. When entering the model integration and configuration stage, these materials are the content to be read by dialogue and retrieval. The model binding relationship only determines which type of model the call goes to. Whether the material fields are complete and whether the responsible person and sign-off are in place are still guaranteed by the drafting and handover process itself.
Configuration and implementation checks
This stage is executed by the server-side model channel configuration, which outputs the model binding relationship and channel response. The signable material drafts and handover records are completed subsequently by AI nodes, code nodes, or manual work. The channel configuration only binds the five types of models—language, indexing, reranking, speech synthesis, and speech recognition—to the corresponding stages, and the material content fields and responsibility attribution do not change accordingly.
| Object | Check | Verification action |
|---|---|---|
| Course offering plan | Fields include course name, offering unit, semester, and planned number of classes; date and signature are complete | Check course name and semester item by item against the scheduling table, check whether the version number and issuance date are consistent, and confirm that the handover receipt has been signed |
| Scheduling table | Fields include class, teacher, week, period, and classroom number, and the quantity matches the course offering plan | Compare the number of classes, weeks, and classroom numbers in the two materials, check the version and date, and check whether missing items are blocked by the template |
| Course selection rules | Fields include selection target, capacity, time window, and adjustment conditions; the responsible person and effective date are clear | Check whether the rule capacity is consistent with the classroom capacity in the scheduling table, and confirm that the issuer and sign-off records are complete |
| Model binding relationship | Language, indexing, reranking, speech synthesis, and speech recognition are bound correspondingly by stage | Check the type labels in the model configuration, compare them with the model names returned by the channel, and check whether maxContext, maxTokens, quoteMaxToken match the stage |
Three common errors
- Symptom: The name or number of classes for the same course does not match between the course offering plan and the scheduling table. Cause: The two materials were modified separately, without field-level comparison and version synchronization.
- Symptom: The material has been issued but the next stage has not acknowledged it, and responsibility attribution is unclear. Cause: The handover record lacks the signer and date, and missing items were not blocked by the template.
- Symptom: Retrieval reports an indexing model-related error, or the answer style changes abruptly after switching models. Cause: The model type and stage binding are inconsistent, and the model identifier does not match the name returned by the channel.
How to verify the setup
Acceptance of this feature: run one dialogue and one retrieval, check whether the model identifier in the response is consistent with the bound language model and indexing model, and check whether the values of maxContext, maxTokens, quoteMaxToken meet the needs of the stage.
Business test: draft one copy according to the template and complete one handover, and see whether missing items are blocked.
- In the model configuration, check the model type labels and stage correspondence item by item, and compare them with the model names returned by the channel to confirm that the model identifiers are consistent.
- Draft one copy each of the course offering plan, scheduling table, and course selection rules according to the template, compare names, quantities, and dates field by field, and after confirming that signatures and receipts are complete, hand them to the next stage for sign-off.