What this category's data looks like
In the kindergarten home-school co-education communication category, materials come from class notices, child observation records, parent request registrations, and commitment response ledgers, with an update cadence that advances daily or weekly along with class activities. When entering the authorized access and external services feature, class notices and observation records serve as content sources that can be published externally, parent request registrations serve as the basis for classification, and the commitment response ledger serves as the verification surface for response deadlines and status. The field characteristics are: commitment items and response times appear in pairs, child performance descriptions must correspond to observation records, parent request classification determines the visibility scope, and notification delivery status distinguishes sent from pending. Multi-turn dialogue and prompts are responsible for fixing the preceding scope and answer constraints, so that the external entry point only presents content matching the visitor's identity, and unauthorized content does not enter the visible set.
Configuration and implementation checks
This part is executed by the memory turn count and prompt configuration in the application settings, outputting the reference historical message scope and answer constraints. The externally available entry points and authorization scope are determined by the publishing service and file permissions; the model only processes filtered materials, while the publishing service and file permissions are responsible for applying the entry points and permissions to the external services.
| Object | Check | Verification action |
|---|---|---|
| Commitment items and response times | Whether the commitment receives a response within the agreed deadline, and whether the response content corresponds one-to-one with the commitment | Check the memory turn count value in the application settings, and run a trial with two consecutive follow-up questions to confirm that the second question can still carry forward the commitment reference from the first question |
| Child performance descriptions | Whether the description is consistent with the observation records, without behaviors or degrees that do not appear in the records | Retrieve the observation records and compare them item by item with the dialogue output, checking whether the statements exceed the scope of the records |
| Parent request classification | Whether the request is classified into the correct category, and whether the visibility scope is determined accordingly | Access once with a restricted identity, and check whether the visible content corresponding to the request classification matches the settings |
| Notification delivery | Whether the notification is marked as delivered, and whether undelivered items are invisible to parents | Check the notification delivery status and the display scope of the external entry point, confirming that undelivered items do not appear |
Three common errors
- Phenomenon: After a parent raises a request, there is no response for a long time. Cause: Commitment items and response times are not registered in pairs, and the response step lacks a verifiable deadline basis.
- Phenomenon: The external description is inconsistent with the observation records. Cause: The statements were not checked back against the observation records, and speculative content was written into the answer as established fact.
- Phenomenon: Feedback is not classified, and the visibility scope is misaligned. Cause: Parent request classification is missing, the external entry point displays according to the default scope, and unauthorized content may be seen.
How to verify the setup
Acceptance for this feature: Ask two consecutive follow-up questions and see whether the second question carries forward the reference from the first question; check whether the reference historical message scope matches the memory turn count value, and record the correspondence between messages and chatId.
Business test: Access once with a restricted identity and see whether the visible scope matches the settings.
- Check the current memory turn count value in the application settings, and confirm that it matches the preceding scope required by the question.
- Compare the usage records of two runs, confirm that the run consumption changes accordingly after adjusting the turn count, and check whether
variablesare correctly brought in.