What this category's data looks like
This page addresses acceptance records and supplementary questions in primary and secondary school admissions organizations, involving three types of materials: admission plans, application material checklists, and admission lists. Admission plans come from education authorities and school admissions leadership groups, updated by academic year or batch, with fields including admission scope, time nodes, application conditions, review process, publicity arrangements, and signature fields; application material checklists come from admissions working groups, updated by application stage, with fields including material name, number of copies, original/copy requirements, submission method, and receipt; admission lists come from the review and admission stage, updated according to batch publicity rhythm, with fields including student name, application number, admission status, publicity date, and signature. When materials enter Q&A acceptance, admission plans provide the rule basis, application material checklists provide the basis for determining missing items, and admission lists provide the basis for result verification; multi-turn dialogue and prompts are responsible for fixing the historical message scope and answer constraints, so that follow-up questions and supplementary questions can be stably handled by the model.
Configuration and implementation checks
This part is executed by the memory turns and prompt configuration in application settings, outputting the referenced historical message scope and answer constraints. "Acceptance records and supplementary questions" are then completed by the model. Memory turns control how many previous dialogue turns can be 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.
| Object | Check | Verification action |
|---|---|---|
| Admission plan | Whether admission scope, time nodes, application conditions, review process, publicity arrangements, and signature fields are complete, and whether the name, quantity, and date of the same record match across the two materials | Check the current memory turns value in application settings, run a trial with two consecutive questions, check whether the second question inherits the reference from the first question, and record the inclusion scope of messages and variables |
| Application material checklist | Whether material name, number of copies, original/copy requirements, submission method, and receipt are complete, whether versions are synchronized, and whether missing signatures or receipts are identified | Ask a question missing key information and see whether it first asks a follow-up question before answering; compare the usage records of two runs to confirm that consumption changes with the turns adjustment |
| Admission list | Whether student name, application number, admission status, publicity date, and signature are complete, and whether the name, quantity, and date of the same record match across the two materials | Use chatId to locate the same conversation, check whether the answer cites the admission plan and application material checklist as the basis, and check whether missing items are followed up |
Three common errors
- Phenomenon: the second question answers off-topic when using references. Cause: the memory turns value is too small, the prior context scope is insufficient, and the model cannot inherit the references and missing items from the previous turn.
- Phenomenon: the name, quantity, and date of the same record do not match between the admission plan and the admission list. Cause: versions are not synchronized, the two materials are updated separately, and fields are not checked by batch.
- Phenomenon: an application material checklist missing a signature or receipt is still treated as accepted. Cause: missing-item identification does not reach the material fields, and follow-up questions are not triggered before answering.
How to verify the setup
This feature acceptance: ask two consecutive follow-up questions and see whether the second question inherits the reference from the first question; check the referenced historical message scope and answer constraints, and use messages, variables, and chatId to record the inclusion scope.
Business test: ask a question missing key information and see whether it first asks a follow-up question before answering.
- Check the current memory turns value in application settings and match it with the prior context scope required by the question; run a trial with two consecutive questions to confirm that the second round correctly inherits the reference from the first round.
- Compare the usage records of two runs to confirm that runtime consumption changes with the turns adjustment; check whether the opening message is treated as prior context, avoiding irrelevant content entering the reference scope.