What this category's data looks like
This category involves three types of materials: registration records, course qualification certificates, and graduation application forms. Registration records are updated by the provincial examination office after each registration, and their fields include admission ticket number, name, ID number, major code, course name, score, and date obtained; course qualification certificates are generated one by one per course, and include course code, qualification date, and the seal of the examining institution; graduation application forms are filled out by the candidate, preliminarily reviewed by the study assistance center, and re-reviewed by the examining institution, and include the major plan version number, number of courses, signature, and receipt. When these three types of materials enter the model access and configuration stage, registration records and course qualification certificates serve as retrieval corpus for the indexing model to chunk, and graduation application forms serve as review evidence for the language model to compare fields; the reranking model reranks entries hit across materials so that the name, quantity, and date of the same course in the two materials can be aligned to the original text. Material versions are synchronized with adjustments to the major plan, old versions are retained for reference, and only the current version may serve as the basis for a reply.
Configuration and implementation checks
This step is executed by the server-side model channel configuration, which outputs the model binding relationships and channel responses. "Evidence entries that can be traced back to the original text" are completed subsequently by AI nodes, code nodes, or manual work. Dialogue and retrieval use this model to map hit entries to their original locations in registration records, course qualification certificates, and graduation application forms.
| Object | Check | Verification action |
|---|---|---|
| Registration records | Fields must include admission ticket number, name, major code, course name, score, and date obtained, and must be consistent with the current major plan version | Check field by field against the original text, confirm that course names and quantities are consistent with the course qualification certificates, that dates do not conflict, and that signatures or electronic receipts are complete |
| Course qualification certificates | Course code, qualification date, and seal of the examining institution must correspond item by item with the same course records in the registration records | Extract the name, quantity, and date of the same course from both materials for comparison, and mark entries missing a seal or receipt as pending supplementation |
| Graduation application forms | The major plan version number, number of courses, signature, and receipt must be aligned across all three parties: registration records, course qualification certificates, and the form itself | Check whether the version number is the current version, whether the number of courses equals the number of qualification certificates, and whether the preliminary and re-review signatures are complete |
| Model binding relationships | The three types of models—language, indexing, and reranking—are bound respectively to the dialogue, retrieval, and reranking stages, and the type labels correspond to the stages | Check the type labels in the model configuration, confirm that the identifiers are consistent with the model names returned by the channel, and check the indexing model binding when retrieval errors occur |
Three common errors
- Symptom: The name or quantity of the same course does not match between the registration records and the course qualification certificate, and citing either document in a reply is incomplete. Cause: The two materials are updated on different schedules, and the old version was not synchronized.
- Symptom: The number of courses in the graduation application form is not equal to the number of qualification certificates, and the review conclusion cannot be written. Cause: The major plan version was not synchronized, and the old form was not refilled after the version change.
- Symptom: Retrieved hit entries lack a signature or receipt, and validity cannot be confirmed when tracing back to the original text. Cause: Items were omitted during material scanning or data entry, and no completeness check was performed.
How to verify the setup
Acceptance for this feature: run one dialogue and one retrieval, check that the model identifier in the response is consistent with the model name returned by the channel, and check that the values of the three parameters maxContext, maxTokens, and quoteMaxToken in the configuration are consistent with the documentation.
Business test: ask an evidence question that spans materials, see whether the answer provides a traceable source, and record the number of cited entries and the tokens of the cited text; record the two separately and do not compare them for equality.
- In the model configuration, check item by item the type labels and binding stages of the three types of models—language, indexing, and reranking—and confirm that they correspond to the stages to be used.
- Check the model identifier against the model name returned by the channel, and check whether the channel and key are consistent with the service being accessed.