What this category's data looks like
This category's data covers three types of materials: internship agreements, internship plans, and internship logs. Internship agreements contain the unit and school names, position, term, and signatures and seals; internship plans contain the batch, dates, supervising teacher, and signature; internship logs contain daily records, week numbers, and student and mentor signatures. Materials enter by batch; agreements and plans are updated before the internship, while logs are added daily as the internship progresses. When querying the business basis, the three types of materials respectively play the roles of authorization and agreement, arrangement and progress, and process and confirmation: agreements and plans provide the source of clauses, and logs provide the source of process records. The name, quantity, and date of the same record must align across the three types of materials, the version must match the current batch, and signatures and receipts must be complete, so that basis entries that can be traced back to the original text can be formed.
Configuration and implementation checks
This part is executed by application settings (response limit, etc.), which determine the length of a single answer and the range of context that can be accommodated. "Basis entries that can be traced back to the original text" are then completed by the model. The response limit is controlled by a slider that sets the length of a single answer; if set too low, the answer will be truncated, and if set too high, consumption will increase.
| Object | Check | Verification action |
|---|---|---|
| Response limit | Matches the answer length required by the page | Check the switch and slider position in application settings, and check the maxResponse value |
| Internship agreement and internship plan | Names, quantities, dates, and signatures and seals match between the two types of materials | Compare unit names, internship terms, position quantities, and signature dates one by one |
| Internship log | Log dates and week numbers match the plan batch, and mentor and student signatures are complete | Spot-check log entries against plan dates, and verify signatures and receipts |
| Quoted content | The tokens of the quoted text are within budget, and the number of array items is recorded separately | Check quoteMaxToken and maxContext, and record the array length |
Three common errors
- Symptom: The name, quantity, and date of the same internship record do not match between the agreement and the log. Cause: The two materials are filled in by different stages, and no cross-check was performed.
- Symptom: The plan has been updated to the current batch, but the log still uses the old version's dates and week numbers. Cause: The version was not synchronized, and the old material was not replaced.
- Symptom: The agreement lacks the unit's signature or the log lacks the mentor's receipt, so the basis entry cannot be traced back to the original text. Cause: Signatures and receipts were not fully collected before entering the query.
How to verify the setup
This feature's acceptance: ask a question that requires a long answer, see whether the ending is complete, and check maxResponse and the truncation behavior.
Business test: ask a basis question that spans materials, and see whether the answer gives a traceable source.
- Check the response limit switch and slider position in application settings, and compare the usage changes between two runs.
- Compare the names, quantities, dates, and signatures of the agreement, plan, and log by batch, and record any inconsistencies.