What this category's data looks like
This category's data covers three types of materials in vocational school student internship management: internship agreements, internship plans, and internship logs, which are respectively signed and acknowledged by multiple parties including schools, enterprises, and parents. Internship agreements contain position, duration, insurance, and signature; internship plans contain batch, date, and supervising teacher; internship logs contain daily records, week number, and enterprise mentor signature. When the materials enter this feature, agreements and plans serve as background constraints, while logs serve as the object of continuous follow-up questions, each playing a different role. In terms of update cadence, agreements are signed once per batch, plans are adjusted weekly, and logs are submitted daily. Field characteristics require that the four types of information—name, quantity, date, and signature—be consistent across the three materials. Common inconsistencies include the name, quantity, or date of the same record not matching between two materials, versions not being synchronized, and missing signatures or acknowledgements.
Configuration and implementation checks
This part is executed by the memory turn count and prompt configuration in the application settings, which output 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, and the model only processes filtered materials. The publishing service and file permissions handle identity and file authentication, and the model answers accordingly.
| Object | Check | Verification action |
|---|---|---|
| Internship agreement | Name, quantity, date, and signature are consistent between the agreement and the plan | Check the memory turn count value in the application settings, run a trial with two consecutive questions, and check whether the second turn carries over the references from the first turn |
| Internship plan | Batch, date, and supervising teacher match the agreement records | Compare the usage records of two runs to confirm that consumption changes with the turn count adjustment, and check the historical range in messages |
| Internship log | Daily records, week number, and enterprise mentor signature match the plan dates | Access once with a restricted identity, see whether the visible range matches the settings, and check whether chatId and variables are correctly carried in with the session |
| External entry point | Visitor identity matches the visible range, and unauthorized content is not visible | Open it once to parents or superiors, access with a restricted identity, and confirm that unauthorized content is not visible |
Three common errors
- Symptom: the name, quantity, or date of the same record does not match between the agreement and the plan. Cause: the two materials were revised separately without cross-checking.
- Symptom: the log version is not synchronized, and an old acknowledgement is treated as a valid signature. Cause: file permissions and the publishing service were not refreshed to the latest version.
- Symptom: the second question answers off-topic when using references. Cause: the memory turn count is too small to use the preceding text, or the opening message is treated as preceding text.
How to verify the setup
Feature acceptance: ask two consecutive follow-up questions and see whether the second question carries over the references from the first question; if it answers off-topic, check the memory turn count value in the application settings and check the historical range in messages.
Business test: access once with a restricted identity, see whether the visible range matches the settings, and confirm that unauthorized content is not visible.
- Check the current memory turn count value in the application settings and match it with the preceding text range required by the question.
- Compare the usage records of two runs to confirm that consumption changes with the turn count adjustment; if the quote limit is involved, check the tokens of the quoted text, and record the array length separately.