What this category's data looks like
This page addresses the scenario of exam question setting and marking in primary and secondary schools. The materials come from three types: the question-setting two-way specification table, the exam paper, and the marking rubric. The question-setting two-way specification table lists question numbers, question types, scores, and difficulty by knowledge point and ability level, and is updated as the syllabus and teaching progress are adjusted; the exam paper carries the question text, answers, and page numbers, and updates are based on the finalized version; the marking rubric gives scoring points, deduction points, and marking explanations for each question, and is updated as marking feedback is revised. When these three types of materials enter the multi-turn dialogue and prompt stage, their roles differ: the specification table serves as the basis for question setting and the checklist draft, the exam paper serves as the text to be issued, and the marking rubric serves as the attachment for scoring criteria. Field characteristics center on names, quantities, dates, signatures, and version numbers. The handover record must be aligned item by item with the three types of materials; any missing item is intercepted.
Configuration and implementation checks
This link is executed by the memory turns and prompt configuration in the application settings, and outputs the referenced historical message range and answer constraints. The signable material drafts and handover records are then completed by the model, and the external entry point and authorization are handled by the publishing service and file permissions.
| Object | Check | Verification action |
|---|---|---|
| Question-setting two-way specification table | Question numbers, question types, scores, difficulty, and knowledge point names are consistent between the specification table and the exam paper, and dates and signatures are complete | Check the memory turns value in the application settings, and use two consecutive follow-up questions to verify whether the specification table fields are correctly carried forward from the preceding context |
| Exam paper | The exam paper name, number of questions, total score, and marking rubric correspond item by item, and the version number and date are synchronized | Draft an exam paper draft according to the template and complete one handover, then check whether the names, quantities, and dates in messages are consistent with the rubric |
| Marking rubric | Scoring points, deduction points, and marking explanations cover all questions, and signatures and receipts are complete | Check the historical message range associated with chatId, confirm that the rubric fields have not been overwritten by irrelevant preceding context, and intercept if a signature is missing |
| Handover record | Responsible person, version number, date, and receipt are consistent between the record and the materials, and missing items are intercepted | Use variables to record the handover fields and run a trial handover to see whether missing items are intercepted |
Three common errors
- Phenomenon: The names and quantities of the same record do not match between the specification table and the exam paper. Cause: During drafting, fields were not aligned item by item according to the template, and the preceding context range was too narrow, causing references to be lost.
- Phenomenon: The marking rubric version is not synchronized; the exam paper has been finalized while the rubric is still the old version. Cause: The memory turns are too large and bring in irrelevant history, or the turns are too small and the preceding context cannot be used.
- Phenomenon: The handover record lacks a signature or receipt, and the responsible person column is empty. Cause: Drafting and handover were not checked against the same template, and missing items were not intercepted before entering the next stage.
How to verify the setup
Acceptance for this feature: use two consecutive follow-up questions to see whether the second question carries forward the reference from the first question, and check whether the historical message range corresponding to messages and chatId matches.
Business test: draft one according to the template and complete one handover to see whether missing items are intercepted.
- Check the current memory turns value in the application settings and match it with the preceding context range required by the question.
- Run a trial with two consecutive question sentences, confirm that the second round correctly carries forward the reference from the first round, and compare the usage records of the two runs.