What this category's data looks like
Materials for the external services of social evaluation of vocational skill level certification mainly consist of evaluation implementation plans, candidate registration forms, and assessor dispatch forms. They come from certification bodies and evaluation implementation departments, are updated by batch, and roll forward with registration and dispatch milestones. The evaluation implementation plan states the occupation direction, level, assessment method, and authorization scope, and is the basis for the visible scope of the entry point; the candidate registration form records the candidate's identity, declared level, and contact information, and determines the information boundary visible to parents or superiors; the assessor dispatch form records the assessor, session, date, and signature, and is the verification working paper for the external service fields in authorized access. When these three types of materials enter the multi-turn dialogue and prompt features, they respectively play the roles of scope definition, identity matching, and process traceability. Their field characteristics center on name, quantity, date, and signature, and the same record must be consistent across materials.
Configuration and implementation checks
This part is executed by the memory turns and prompt configuration in the application settings, and outputs the referenced historical message range and answer constraints. The externally available entry point and authorization scope are determined by the publishing service and file permissions. The model only processes filtered materials, while the publishing service and file permissions handle identity and file authentication.
| Object | Check | Verification action |
|---|---|---|
| Evaluation implementation plan | The authorization scope and external service fields must be aligned item by item with the registration form and dispatch form | Check the occupation, level, assessment method, and authorization scope in the plan, compare them with the declared level in the registration form and the session dates in the dispatch form, and confirm that the name, quantity, and date are consistent |
| Candidate registration form | The candidate's identity matches the visible scope, and unauthorized content is not visible | Access once with a restricted identity, check whether the candidate name, declared level, and contact information in the registration form appear only within the authorized scope, and check the signature and receipt |
| Assessor dispatch form | The assessor, session, date, and signature must be consistent with the implementation plan | Check that the assessor name, session, and date in the dispatch form are consistent with the plan, check whether the signature or receipt is complete, and whether the version is synchronized |
| Multi-turn dialogue and prompts | The memory turns match the preceding context range required by the question | Check the current value in the application settings, run a trial with two consecutive follow-up questions, observe whether the second turn carries forward the reference from the first turn, and compare the usage of the two runs |
Three common errors
- Symptom: The quantity or date of the same candidate name or declared level does not match between the registration form and the implementation plan. Cause: The two materials were entered separately, and no item-by-item cross-material comparison was performed.
- Symptom: The dispatch form version is not synchronized, and the old session date still appears in the external service scope. Cause: After the materials were updated, the authorization scope and publishing status were not rechecked.
- Symptom: The registration form or dispatch form lacks a signature or receipt, but it is still visible in the external service. Cause: Signatures and receipts were not included in the prerequisite check for the authorized visible scope.
How to verify the setup
Acceptance of this feature: with two consecutive follow-up questions, see whether the second question carries forward the reference from the first question; combine chatId, messages, and variables to check the referenced historical message range and answer constraints.
Business test: access once with a restricted identity, see whether the visible scope matches the setting; unauthorized content is not visible, and check the registration form and dispatch form fields, dates, and signatures.
- Check the current value of memory turns in the application settings, and confirm that it matches the preceding context range required by the question.
- Run a trial with two consecutive follow-up questions, compare the usage records of the two runs, and check whether the opening message is treated as preceding context.