What this category's data looks like
This category's data mainly includes registration records, course qualification certificates, and graduation application forms. Registration records are archived by the provincial examination office after each exam, with an update cadence synchronized with the exam session; fields include admission ticket number, name, ID number, major code, course code, score, signature field, and archive date. Course qualification certificates are generated by the main examining institution after scores are released; fields include course name, qualification certificate number, issue date, and handler's signature and seal. Graduation application forms are filled out by candidates when applying for graduation; fields include name, ID number, major name, number of courses, review opinion, and responsible person's signature. When the materials enter the multi-turn dialogue and prompt feature, registration records serve as the historical factual draft, course qualification certificates serve as the basis for course-dimension verification, and graduation application forms serve as the application and approval carrier for the graduation conclusion. The three must mutually corroborate on fields, dates, and signatures to support exception tracing.
Configuration and implementation checks
This part is executed by the memory turns and prompt configuration in the application settings, and the output references the historical message range and answer constraints. The "exception list and review conclusion" is then completed by the model. Memory turns control how many previous dialogue turns can be referenced at most when answering; too small a value makes prior context unusable, while too large a value brings in irrelevant content and increases consumption.
| Object | Check | Verification action |
|---|---|---|
| Registration records | Whether the name, course name, and date in the same record are consistent between the registration records and the course qualification certificate | Check the fields and dates of the two materials, use chatId to locate the session, and use messages to trace prior records |
| Course qualification certificate | Whether the qualification certificate number, issue date, and handler's signature correspond to the archived record | Check the qualification certificate number and signature field, and confirm whether the receipt is complete |
| Graduation application form | Whether the number of courses and major name on the application form match the registration records, and whether the responsible person's signature is in place | Check the application form fields and signature, and use variables to mark exception items |
| Exception list and review conclusion | Exceptions are supported by original records, and the reviewer has signed | Create an exception record and see whether the source material can be traced and a review conclusion can be formed |
Three common errors
- Phenomenon: The name, course name, and date in the same record do not match between the registration records and the course qualification certificate. Cause: The two materials are archived separately, and no field-level comparison was performed.
- Phenomenon: The graduation application form version is not synchronized, and the number of courses is inconsistent with the registration records. Cause: After the application form was updated, it was not written back to the archived record.
- Phenomenon: The qualification certificate lacks the handler's signature or the receipt is missing, so the review conclusion cannot be signed and confirmed. Cause: The signature field was not verified during the material circulation process.
How to verify the setup
Feature acceptance: Use two consecutive follow-up questions. The first question gives the course record in the registration records, and the second question uses anaphora to ask for the qualification certificate number of that course. See whether the second question inherits the anaphora from the first question, and check whether chatId, messages, and variables are correctly referenced.
Business test: Create an exception record and see whether the source material can be traced and a review conclusion supported by original records and signed by the reviewer can be formed.
- In the application settings, check the current value of memory turns, match it with the prior context range required by the question, and run a trial with two consecutive questions to confirm that the second round correctly inherits the anaphora from the first round.
- Compare the usage records of two runs before and after adjusting the number of turns, confirm that run consumption changes with the number of turns, and check that the opening message is not treated as prior context.