Multi-Turn Conversation and Prompts for Kindergarten Operations and Quality Self-Assessment: Handle Questions and Collect Missing Information

Kindergarten Quality: review conversation for question intake. Check source versions, input mappings and the values received by downstream nodes.

What this category's data looks like

This page addresses the kindergarten operation behavior and quality self-assessment scenario; the materials include three types: self-assessment reports, issue lists, and rectification plans. Self-assessment reports are usually updated by semester or academic year, with fields covering operating conditions, safety and hygiene, care and education, faculty and staff, and internal management, accompanied by dates and signatures; issue lists are recorded item by item along with inspections or self-assessments, with fields covering issue description, responsible department, rectification deadline, and receipt; rectification plans correspond item by item to the issue list, with fields covering rectification measures, completion date, and responsible person's signature. When these three types of materials enter the Q&A intake and missing-item follow-up function, the self-assessment report serves as the primary basis for answering the overall situation, the issue list is used to locate specific missing items and the direction of follow-up questions, and the rectification plan is used to verify the rectification loop closure and signature receipts. The material sources are kindergarten self-assessment submissions, superior inspection feedback, and daily patrol records; the update rhythm is submission at the beginning of the semester, dynamic supplementation during the semester, and consolidation at the end of the semester. In terms of field characteristics, the name, quantity, and date of the same record must be consistent across the three materials, versions must be synchronized, and signatures and receipts must be complete.

Configuration and implementation checks

This part is executed by the memory turns and prompt configuration in the app settings, outputting the reference range of historical messages and the answer constraints. Memory turns control how many previous turns of dialogue can be referenced at most when answering; if the value is too small, the preceding text cannot be used, and if the value is too large, irrelevant content is brought in and consumption increases. The "intake records and completed question items" are then completed by the model, while the external entry point and authorization are handled by the publishing service and file permissions.

ObjectCheckVerification action
Self-assessment reportThe name, quantity, date, and signature must be consistent with the issue list and rectification planCheck the memory turns value in the app settings, run a trial with two consecutive question turns, and check whether the second turn can carry forward the references from the first turn; check the transmission of chatId, messages, and variables in the session
Issue listThe issue description, responsible department, rectification deadline, and receipt must correspond item by item to the rectification planCompare the usage records of two runs to confirm the consumption change after adjusting the turns; check whether the name, quantity, and date of the same record in the issue list and rectification plan match
Rectification planThe rectification measures, completion date, and responsible person's signature must close the loop with the issue listCheck whether the signatures and receipts are complete and whether the versions are synchronized; confirm that the opening message is not treated as preceding text and that the messages range matches the current question

Three common errors

  • Symptom: The name, quantity, and date of the same record do not match between the self-assessment report and the issue list. Cause: The two materials are submitted separately, are not checked against unified fields, and the versions are not synchronized.
  • Symptom: The rectification plan lacks a signature or receipt, and the issue list has been closed but there is no basis for loop closure. Cause: Signature receipts are not retained in the material circulation process, and the update rhythm is inconsistent.
  • Symptom: When the second question uses references, the answer does not address the question, and the response becomes slower with increased consumption. Cause: The memory turns value does not match the range of preceding text required by the question, bringing in irrelevant content.

How to verify the setup

This function's acceptance: ask two consecutive follow-up questions and see whether the second question carries forward the references from the first question; check the transmission of chatId, messages, and variables in the session, and confirm that the reference range of historical messages and the answer constraints meet expectations.

Business test: ask a question that lacks key information and see whether it first asks a follow-up before answering; the question items completed after the follow-up must have a material basis, then be forwarded to the responsible person for handling.

  • Check the current memory turns value in the app settings, run a trial with two consecutive question turns, and confirm that the second turn can correctly carry forward the references from the first turn.
  • Compare the usage records of two runs to confirm that usage changes accordingly after adjusting the turns; check whether the name, quantity, date, and signature of the self-assessment report, issue list, and rectification plan are consistent.