What this category's data looks like
This category's data typically includes registration forms, academic qualification certificates, and work experience certificates. The sources are submissions by applicants and stamped returns from their employers, and the update cadence rolls with batches and correction notices. The registration form carries identity, examination level, specialty, and employer opinion; the academic qualification certificate carries the graduating institution, specialty, certificate number, and date of award; the work experience certificate carries start and end dates, position, and employer seal. When these three types of materials enter multiple rounds of dialogue and prompt features, their respective roles are: the registration form provides the subject and the registration criteria, the academic qualification certificate provides the date and specialty comparison basis for the qualification threshold, and the work experience certificate provides the start, end, and cumulative criteria for calculating years of experience. Field characteristics are concentrated in four categories: names, quantities, dates, and signature receipts. It is common for the names, quantities, and dates of the same record to fail to match across two materials, or for versions to be out of sync, or for signatures or receipts to be missing.
Configuration and implementation checks
This part is executed by the memory rounds and prompt configuration in the application settings, and outputs the historical message range and answer constraints for reference. "Externally available entry points and authorization scope" are determined by the publishing service and file permissions, and the model only processes filtered materials. Memory rounds control how many previous rounds of dialogue can be referenced at most when answering. If the value is too small, prior context cannot be used; if the value is too large, irrelevant content is brought in and consumption increases.
| Object | Check | Verification action |
|---|---|---|
| Registration form | Whether names, quantities, dates, and signatures correspond item by item with the academic qualification certificate and work experience certificate | Check the memory rounds value in the application settings, run a trial with two consecutive follow-up questions, and check whether messages and chatId are carried over within the same session |
| Academic qualification certificate | Whether the graduating institution, specialty, certificate number, and date of award are consistent with the registration form's criteria | Compare field by field against the registration form and record inconsistencies; check whether the session variables in variables are correctly carried in with each round |
| Work experience certificate | Whether the start and end dates, position, and employer seal match the date chain of the registration form and academic qualification certificate | Check whether signatures and receipts are complete and whether versions are in sync; compare the usage records of two runs to confirm that consumption changes with the round adjustment |
| Consecutive follow-up questions | Whether the second round correctly carries over the references from the first round | Run a trial with two consecutive question sentences, use a reference in the second question, and check whether the answer is off-topic |
Three common errors
- Symptom: the names, quantities, and dates of the same record fail to match between the registration form and the work experience certificate. Cause: the two materials are filled in separately, without field-by-field comparison and receipt verification.
- Symptom: the academic qualification certificate has been updated to a new version, but the registration form still references the old version, resulting in inconsistent criteria. Cause: versions are out of sync, lacking a unified version marker and return confirmation.
- Symptom: the work experience certificate lacks a signature or receipt, so the review step cannot confirm the employer's opinion. Cause: seals and receipts were not archived together with the materials, and the correction notice was not closed-loop.
How to verify the setup
Feature acceptance: with two consecutive follow-up questions, see whether the second question carries over the reference from the first question; check whether the value ranges and answer constraints of messages, chatId, and variables in the session are consistent.
Business test: access once with a restricted identity and see whether the visible range matches the setting; unauthorized content is not visible, and the range opened to parents or superiors is consistent with the authorization.
- Check the current memory rounds value in the application settings and match it with the prior context range required by the question; run a trial with two consecutive question sentences and record the results.
- Compare the usage records of two runs to confirm that consumption changes with the round adjustment; check whether the opening message is treated as prior context.