What this category's data looks like
This page focuses on the scenario of foreign teacher appointment and course scheduling, and organizes three types of materials: appointment contracts, work permit materials, and course scheduling tables. Appointment contracts are generated by the HR department at the signing node, and contain name, position, appointment period, number of class hours, and signature field; work permit materials are updated by the foreign affairs specialist at the declaration node, and contain name, ID number, permit period, and receipt; course scheduling tables are maintained by academic affairs at the scheduling node, and contain teacher name, course name, weekly class hours, and date. When the three types of materials enter this function, the contract and permit materials serve as the verification baseline, and the course scheduling table serves as the comparison object, jointly supporting discrepancy localization for consistency of the same object's name, quantity, and date across the two materials. The material update rhythm is driven by the three nodes of signing, declaration, and scheduling. Field characteristics are mainly name, quantity, date, and signature, and version differences often appear in the cross-department write-back stage.
Configuration and implementation checks
This part is executed by application settings (reply limit, etc.), outputting the length of a single answer and the context range it can accommodate. The discrepancy list is then completed by the model. The reply limit uses a slider to control the length of a single answer. If set too low, the answer will be truncated; if set too high, consumption will increase.
| Object | Check | Verification action |
|---|---|---|
| Appointment contract | The same teacher name, appointment period dates, number of class hours, and signature field are consistent across the two materials | Check whether the contract name and the name in the work permit materials are identical character by character, check whether the appointment start and end dates and the dates in the course scheduling table fall within the same interval, check whether the number of class hours corresponds to the weekly class hours in the schedule, and check whether the signature field and receipt are complete; when context range is involved, record maxContext |
| Work permit materials | ID number, permit period, and receipt date do not conflict with the contract appointment period | Check whether the ID number and the contract name point to the same object, check whether the permit period covers the contract appointment period, check whether the receipt date is later than the declaration date, and check and mark entries missing a signature or receipt; the number of quoted items is recorded by array length, and quoteMaxToken only checks the tokens of the quoted text |
| Course scheduling table | Teacher name, course name, weekly class hours, and date match the contract and permit materials | Check whether the teacher name is consistent with the contract name, check whether the weekly class hours match the contract class hours, check whether the course dates overlap with the appointment period dates, and check whether the version number is consistent with the latest write-back; the length of a single answer is controlled by maxResponse, and longer discrepancy lists need confirmation that the ending is complete |
| Discrepancy list | When the same object's name, quantity, and date do not match across the two materials, list them item by item | List inconsistent items by field, mark the source material and version, submit to the reviewer for confirmation and write-back; check whether the list covers the date and signature discrepancies among the contract, permit materials, and course scheduling table |
Three common errors
- Phenomenon: The same teacher name is written differently in the contract and the course scheduling table, and the quantity and date do not match. Cause: Cross-department entry did not unify field conventions, and versions were not synchronized, causing old values to remain.
- Phenomenon: The receipt date in the work permit materials is missing, and the contract signature field is empty. Cause: Write-back at the declaration node and signing node is not synchronized, and missing signatures or receipts were not intercepted.
- Phenomenon: The weekly class hours in the course scheduling table are inconsistent with the contract class hours, and the discrepancy list omits items. Cause: The scheduling version was not aligned with the contract version, and name, quantity, and date were not compared field by field during verification.
How to verify the setup
This function's acceptance: ask a question that requires a long answer, see whether the ending is complete, and confirm that the reply limit matches the answer length required by the page. If it breaks off in the middle of a sentence, increase the slider and retry.
Business test: use a real record to find fields inconsistent with the ledger, verify the name, quantity, date, and signature across the contract, work permit materials, and course scheduling table, record discrepancies, and submit them to the reviewer for confirmation and write-back.
- In application settings, check the reply limit switch and slider position, compare usage from two runs, and confirm the change in single-run usage after adjusting the limit.
- For each real record, verify field by field the name, quantity, date, and signature in the contract, work permit materials, and course scheduling table, write inconsistent items into the discrepancy list, and mark the version.