What this category's data looks like
This page addresses the drafting of materials and handover of responsibilities in kindergarten childcare daily life management, involving three types of materials: the daily life schedule, morning and afternoon health check records, and child health observation records. The daily life schedule is updated weekly or daily, with fields including time slot, activity name, venue, and signatures of the responsible teacher and childcare worker; morning and afternoon health check records are filled in twice, in the morning and at noon, with fields including child's name, body temperature, oral and skin observations, abnormality flags, and signatures of the inspector and reviewer; child health observation records are updated as needed or daily, with fields including observation time, symptom description, handling method, parent notification, and handover receipt. When these three types of materials enter the model access and configuration stage, they respectively take on the roles of time-slot arrangement verification, health abnormality screening, and individual tracking records, and their fields, dates, and signatures must be compared item by item during handover to ensure they can be issued.
Configuration and implementation checks
This step is executed by the server-side model channel configuration, outputting model binding relationships and channel responses. The issuable material drafts and handover records are then completed by subsequent AI nodes, code nodes, or manual work. Models are divided into five categories: language, indexing, reranking, speech synthesis, and speech recognition. Different steps bind different model types, and the type labels must be checked in the model configuration.
| Object | Check | Verification action |
|---|---|---|
| Daily life schedule | Time slots, activity names, venues, and signatures of the responsible teacher and childcare worker are complete, and the date and version are consistent | Check whether the time slots and activity names in the table are consistent with the dates and classes in the morning and afternoon health check records and health observation records, check whether the signature fields for the responsible teacher and childcare worker are filled in, and compare the version number and issue date |
| Morning and afternoon health check records | Child's name, body temperature, oral and skin observations, abnormality flags, and signatures of the inspector and reviewer are complete | Check whether the child names, counts, and dates in the morning and noon records correspond to the daily life schedule, check whether the abnormality flags connect with the handling methods in the health observation records, and confirm the reviewer's signature and receipt |
| Child health observation records | Observation time, symptom description, handling method, parent notification, and handover receipt are complete | Check whether the symptom description and handling method are consistent with the abnormality flags in the morning and afternoon health check records, check the signatures for parent notification and handover receipt, and confirm that the date and version are synchronized with the daily life schedule |
| Model binding relationships | The five model categories—language, indexing, reranking, speech synthesis, and speech recognition—correspond to the steps in which they are used | Check the type labels in the model configuration, compare the model identifiers against the model names returned by the channel, check the configuration items maxContext, maxTokens, quoteMaxToken, and toolChoice, and confirm that the channel and key source are consistent |
Three common errors
- Symptom: The count or date for the same child's name does not match between the morning and afternoon health check records and the health observation records. Cause: The two materials were drafted separately, and names, counts, and dates were not compared item by item during handover.
- Symptom: The daily life schedule has been updated to a new version, but the morning and afternoon health check records still reference the old time slots. Cause: The version was not synchronized, and the version number and issue date were not checked during handover.
- Symptom: The health observation records lack parent notification or handover receipt signatures. Cause: The signature fields and receipt were not checked during handover, and missing items were not blocked.
How to verify the setup
Acceptance for this feature: run one conversation and one retrieval, check the model identifiers in the responses, confirm that the language model and indexing model are bound to the corresponding steps, and check the configuration items maxContext, maxTokens, quoteMaxToken, and toolChoice.
Business test: draft one copy according to the template and complete one handover, and see whether missing items are blocked.
- Check the type labels of the five model categories in the model configuration, compare the model identifiers against the model names returned by the channel, and confirm that the channel and key source are consistent.
- Draft the daily life schedule, morning and afternoon health check records, and health observation records according to the template, compare names, counts, dates, and signatures item by item, complete one handover, and check missing-item blocking.