What this category's data looks like
This page addresses the compulsory education dropout prevention and school retention scenario. Materials include dropout risk ledgers, return-to-school persuasion records, home visit records, as well as signable draft materials and handover records generated by summarizing these records. Ledger fields include student name, class, risk level, identification date, and responsible person's signature; persuasion records include persuasion time, participants, persuasion result, and receipt; home visit records include home visit date, home visit teacher, and parent signature. The three types of materials are updated weekly, and changes in risk level, persuasion results, and home visit receipts must be synchronized. When materials enter this function, the ledger provides the base numbers, the persuasion and home visit records provide process evidence, and the model drafts signable drafts and generates handover records based on these, for the next stage to sign for receipt.
Configuration and implementation checks
This step is executed by the memory turns and prompt configuration in the application settings, which output the reference historical message range and answer constraints. The signable draft materials and handover records are then completed by the model. The memory turns control how many previous dialogue turns can be referenced at most when answering. If the value is too small, the preceding context cannot be used; if the value is too large, irrelevant content is brought in and consumption increases.
| Object | Check | Verification action |
|---|---|---|
| Dropout risk ledger | Fields complete, responsible person clear, version and date consistent | In the application settings, check the current memory turns value, run a trial with two consecutive questions, confirm that the second question can carry on the reference from the first question, and check whether the ledger fields in messages are complete |
| Persuasion record | Persuasion time, participants, persuasion result, receipt consistent with the ledger name, quantity, and date | Draft a persuasion record according to the template, complete one handover, see whether missing items are blocked, and check whether the name, quantity, and date of the same record under chatId match across the two materials |
| Home visit record | Home visit date, home visit teacher, parent signature synchronized with version | Compare the usage records of two runs, check whether the home visit fields in variables are synchronized with the version, and whether missing signatures or receipts are blocked |
| Handover record | Responsible person clear, version and date consistent, receipt complete | Draft a handover record according to the template and complete one handover, see whether missing items are blocked, and confirm that the sign-for-receipt information for the next stage is complete |
Three common errors
- Phenomenon: The name, quantity, and date of the same record do not match between the ledger and the persuasion record. Cause: When drafting, the field source under the same
chatIdwas not locked, and the version was not synchronized. - Phenomenon: The home visit record lacks a parent signature or receipt, but the handover is still allowed through. Cause: The prompt did not list signature and receipt as required constraints, and the handover check did not block it.
- Phenomenon: When the second question uses a reference, the answer is off-topic, the response becomes slower, and consumption rises. Cause: The memory turns value does not match the preceding context range required by the question, bringing in irrelevant content.
How to verify the setup
This function's acceptance: Ask two consecutive follow-up questions, see whether the second question carries on the reference from the first question, and check the values of the three identifiers messages, chatId, and variables in the historical message range.
Business test: Draft one according to the template and complete one handover, and see whether missing items are blocked.
- In the application settings, check the current memory turns value, run a trial with two consecutive questions, and confirm that the second question can carry on the reference from the first question.
- Compare the usage records of two runs, confirm that usage changes accordingly after adjusting the turns, and check whether the fields in
variablesare synchronized with the version.