Multi-Turn Conversation and Prompts for Kindergarten Operations and Quality Self-Assessment: Draft Materials and Hand Over Responsibilities

Kindergarten Quality: review conversation for material handover. 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 material sources are three types of text: self-assessment reports, issue lists, and rectification plans, with an update cadence that advances along with the kindergarten operation cycle and rectification milestones. After the three types of materials enter the application, they play different roles: the self-assessment report provides overall facts and conclusions, the issue list carries specific items and responsibility assignments, and the rectification plan arranges deadlines and handover milestones. Field characteristics center on names, quantities, dates, signatures, and receipts, with version numbers synchronized alongside revisions. In the material drafting stage, the model generates a signable draft based on the range of historical messages; in the handover stage, the model outputs a handover record. Both require complete fields, clearly identified responsible persons, and consistent versions and dates before they can be handed to the next stage for sign-off.

Configuration and implementation checks

This part is executed by the memory turn count and prompt configuration in the application settings, which output the range of historical messages referenced and the answer constraints. The signable material drafts and handover records are then completed by the model. The memory turn count controls how many preceding turns of dialogue are referenced at most when answering; too small a value fails to use prior context, while too large a value brings in irrelevant content and increases consumption.

ObjectCheckVerification action
Self-assessment reportFields are complete, responsible persons are clearly identified, versions and dates are consistent, and names, quantities, and dates align with those in the issue list and rectification planCheck the current memory turn count in the application settings, run a trial with two consecutive question turns, check whether the second turn carries forward the references from the first turn, and confirm the historical range in messages
Issue listItem names, quantities, and dates are consistent with the self-assessment report, signatures or receipts are complete, and when versions are not synchronized the latest version prevailsCompare the same record in the two materials, check whether names, quantities, and dates fail to match, check whether signatures and receipts are missing, and if necessary use chatId to locate the same session
Rectification planDeadlines, responsible persons, and handover milestones are clear, versions and dates are consistent with the self-assessment report and issue list, and sign-off records are completeDraft one according to the template and complete one handover, see whether missing items are blocked, and check whether the fields filled into variables are consistent with the materials

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 field definitions were not unified during drafting, and the historical message range brought in content from an old version.
  • Symptom: The rectification plan has been updated to a new version, but the self-assessment report still references the old date. Cause: The version was not synchronized, and the memory turn count was set too large, bringing in irrelevant prior context.
  • Symptom: The handover record lacks a signature or receipt, and the next stage cannot sign off. Cause: The prompt did not constrain the signature field, and the answer did not cover the receipt requirement.

How to verify the setup

This feature's acceptance check: ask two consecutive follow-up questions and see whether the second question carries forward the references from the first question.

Business test: draft one according to the template and complete one handover, and see whether missing items are blocked.

  • Check the current memory turn count in the application 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, confirm that usage changes accordingly after the turn count is adjusted, and check whether the use of messages, chatId, and variables meets expectations.