What this category's data looks like
This category's data covers three types of materials: school-enterprise cooperation agreements, order-class training plans, and master-apprentice mentoring records. A school-enterprise cooperation agreement contains the cooperation term, number of positions, responsible department, and signatures of both parties; an order-class training plan contains course modules, rotation cycles, assessment methods, and approval date; a master-apprentice mentoring record contains the mentoring master, apprentice list, week number, skill items, and receipt. The materials come from academic affairs, enterprise mentors, and department heads, and are updated on three rhythms: start of semester, monthly, and project closure. When entering this feature, the agreement serves as a constraint, the training plan serves as a field template, and the mentoring records serve as the objects to be filled in one by one; together the three support the generation of a signable draft and handover record.
Configuration and implementation checks
This part is executed by the memory turns and prompt configuration in the app settings, and outputs the referenced historical message range and answer constraints. The "signable material draft and handover record" is then completed by the model. Memory turns control how many previous dialogue turns can be referenced at most when answering; too small a value fails to use the preceding context, while too large a value brings in irrelevant content and increases consumption.
| Object | Check | Verification action |
|---|---|---|
| School-enterprise cooperation agreement | The cooperation term, number of positions, responsible department, and signature date must be consistent with the order-class training plan | Check the enterprise name, number of positions, and start and end dates in the agreement and the training plan, and check whether the signatures and receipts are complete |
| Order-class training plan | The course modules, rotation cycles, assessment methods, and approval date must correspond to the master-apprentice mentoring records | Compare item by item the week numbers and skill items in the plan with the week numbers and skill items in the mentoring records, and check whether the version number and date are in sync |
| Master-apprentice mentoring record | The mentoring master, apprentice list, week number, skill items, and receipt must be traceable item by item | Draft one mentoring record according to the template, go through one handover sign-off, and check whether missing items are blocked |
| Handover record | The responsible person, version, and date must be consistent with the materials handed over | Check the responsible person's name, material version number, and issuance date in the handover record, and confirm they are consistent with the source materials |
Three common errors
- Symptom: the same batch of apprentice lists does not match in quantity between the training plan and the mentoring records. Cause: the two materials are maintained separately and are not updated in sync under the same version.
- Symptom: the cooperation term in the agreement is inconsistent with the start and end dates of the training plan. Cause: the versions are not in sync, and after revision the change was not written back to the other material.
- Symptom: the mentoring record lacks the master's signature or the enterprise receipt. Cause: during the handover step, the signature field and receipt field were not checked item by item.
How to verify the setup
Feature acceptance: run a trial with two consecutive follow-up questions. In the first question, give the master's name and week number from the mentoring record; in the second question, use a reference to follow up on the same record, and see whether the second question carries forward the reference from the first question. At the same time, check whether the referenced historical message range in messages matches the memory turns value, whether the session corresponding to chatId is continuous, and whether the fields in variables are correctly brought in.
Business test: draft one according to the template and complete one handover, and see whether missing items are blocked.
- In the app settings, check the current memory turns value, run a trial with two consecutive questions, and confirm that the second question can correctly carry forward the reference from the first question.
- Compare the usage records of two runs, confirm that the run consumption changes accordingly after adjusting the turns, and check whether the opening message is treated as preceding context.