What this category's data looks like
The external entry points and authorization scope for vocational training subsidy applications revolve around three types of materials: training class filing, sign-in records, and completion assessment forms. Class filing includes the institution name, class number, start and end dates, teaching location, and the signature of the person in charge; sign-in records include the trainee's name, the last four digits of the ID number, the sign-in date, and the trainee's own signature; completion assessment forms include the assessment subject, score, assessment date, and the assessor's signature. The materials are collected by training institutions by class, submitted period by period, and the update cadence is synchronized with the class opening cycle. When entering the multi-turn dialogue and prompt functionality, class filing serves as the basis for determining identity and visible scope, sign-in records serve as the basis for verifying attendance facts, and completion assessment forms serve as the evidence for result confirmation. Together, the three determine the entry points and authorization scope that can be opened externally, for parents or superiors to view according to identity.
Configuration and implementation checks
This part is executed by the memory turn count and prompt configuration in the application settings, outputting the referenced historical message range and answer constraints. The externally available entry points 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 the actual authentication. The model answers accordingly; the configuration itself does not generate access entry points and does not perform identity or file authentication.
| Object | Check | Verification action |
|---|---|---|
| Training class filing | Institution name, class number, start and end dates, and signature of the person in charge are consistent between the filing and the sign-in records | Take the filing and sign-in records of the same class, compare the name, quantity, and dates item by item, check whether the signatures and receipts are complete, and record chatId and messages in the dialogue |
| Sign-in records | Trainee name, sign-in date, and personal signature match between the sign-in records and the completion assessment form | Initiate two consecutive follow-up questions with a restricted identity; the first question asks about the class, the second uses a reference to ask about attendance, and check whether the number of historical turns in messages is sufficient |
| Completion assessment form | Assessment subject, score, assessment date, and assessor signature are consistent between the assessment form and the filing | Compare the subject and date of the assessment form and the filing, check whether the signatures and versions are synchronized, and if necessary use variables to mark the class to limit the visible scope |
| External entry points and authorization scope | Visitor identity matches the visible scope; unauthorized content is not visible | Access once with a restricted identity, see whether the visible scope matches the settings, and check whether the memory turn count value matches the range of prior context required by the question |
Three common errors
- Symptom: The same trainee's name or date does not match between the sign-in records and the completion assessment form. Cause: The two materials are entered separately, no cross-check is performed, and versions are not synchronized.
- Symptom: The class number in the training class filing is inconsistent with the number in the sign-in records. Cause: After the filing is updated, it is not synchronized to the sign-in records, and receipts or signatures are missing.
- Symptom: When the second question uses a reference, the answer is off-topic, responses become slower, and consumption rises. Cause: The memory turn count is too large and brings in irrelevant content, or too small and cannot use the prior context.
How to verify the setup
Acceptance of this feature: two consecutive follow-up questions; the first asks about the class filing, the second uses a reference to ask about the sign-in for that class; see whether the second question picks up the reference from the first, and check the actual number of historical turns referenced in messages.
Business test: access once with a restricted identity, see whether the visible scope matches the settings, and unauthorized content is not visible.
- In the application settings, check the current value of the memory turn count and whether it matches the range of prior context required by the question.
- Compare the usage records of two runs to confirm the changes in consumption and response speed after adjusting the turn count.