What this category's data looks like
This page focuses on drafting materials and handover of responsibilities in kindergarten childcare daily life management, covering three types of materials: 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 period, activity name, childcare key points, responsible person, date, and signature; morning and afternoon health check records are filled in twice, in the morning and at noon, with fields including child's name, body temperature, throat and hand observation, handling of abnormalities, inspector, and date; child health observation records are updated as needed or daily, with fields including observation time, description of performance, water and meal intake, nap status, handling opinions, observer, and signature. When these three types of materials enter the multi-turn dialogue and prompt function, they respectively serve as the timeline basis, health screening evidence, and individual status supplement, based on which drafts and handover records are generated, and then handed to the next step for receipt.
Configuration and implementation checks
This step is executed by the memory turn count and prompt configuration in the application settings, outputting the historical message range and answer constraints for reference. The material drafts and handover records that can be issued are then completed by the model, while the external entry point and authorization are handled by the publishing service and file permissions.
| Object | Check | Verification action |
|---|---|---|
| Daily life schedule | Time period, activity name, childcare key points, responsible person, date, and signature are complete, and consistent with the date and class name in the morning and afternoon health check records | Check the memory turn count value in the application settings, run a trial with two consecutive rounds of questions, check whether the second round can carry forward the references from the first round, and verify the fields brought in by messages and variables |
| Morning and afternoon health check records | Child's name, body temperature, throat and hand observation, handling of abnormalities, inspector, and date are complete, and the name, quantity, and date of the same record are consistent between the draft and the handover record | Draft one according to the template and complete one handover, check whether missing items are blocked, and verify whether the historical message range corresponding to chatId covers the previous round of materials |
| Child health observation records | Observation time, description of performance, water and meal intake, nap status, handling opinions, observer, and signature are complete, and the version and date are synchronized | Compare the usage records of two runs, confirm the consumption changes after adjusting the turn count, and verify whether the handover record receipt is attached with a signature |
| Handover record | Responsible person is clear, version and date are consistent, and receipt is complete | Hand to the next step for receipt, and check whether missing signatures and receipt items are blocked |
Three common errors
- Symptom: The name, quantity, or date of the same record does not match between the draft and the handover record. Cause: Insufficient previous turns or the prompt does not constrain the field source, and the model rewrites on its own.
- Symptom: The schedule has been updated, but the handover record still references the old version. Cause: The memory turn count is too large and brings in irrelevant old content, and the version is not synchronized.
- Symptom: The handover record lacks a signature or receipt. Cause: The prompt does not list signature and receipt as required constraints, and the model only generates the body text.
How to verify the setup
Acceptance of this feature: Use two consecutive rounds of follow-up questions. In the first question, provide the material name and date. In the second question, use a reference to ask about the same record. See whether the second question carries forward the reference from the first question, and verify the historical message range corresponding to messages, variables, and chatId.
Business test: Draft one according to the template and complete one handover, and see whether missing items are blocked.
- Check the current value of the memory turn count in the application settings, and match it with the previous context range required by the question.
- Run a trial with two consecutive rounds of questions, compare the usage records of the two runs, and confirm the consumption changes after adjusting the turn count.