What this category's data looks like
This page addresses kindergarten safety protection and emergency drill scenarios. Material sources include hazard ledgers, drill plans and sign-in sheets, access control and school bus inspection records, and responsibility handover forms. The update cadence is weekly inspections, per-drill execution, and per-class handover. Field characteristics center on hazard items and rectification deadlines, drill headcount and sign-in, access control and school bus inspection items, and responsible person signatures. When materials enter this function, hazard ledgers and inspection records serve as context to provide pending and completed details, drill plans and sign-in sheets serve as the comparison baseline, and responsibility handover forms serve as receipt evidence; based on this, the model drafts issuable material drafts and handover records, with entry and authorization handled by the publishing service and file permissions.
Configuration and implementation checks
This step 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. Issuable material drafts and handover records are then completed by the model. The response limit is controlled by a slider for the length of a single answer; if set too low, answers will be truncated, and if set too high, consumption will increase.
| Object | Check | Verification action |
|---|---|---|
| Hazard ledger | Whether hazard items and rectification deadlines are closed loop item by item, and whether responsible person signatures are complete | Check rectification deadlines and signatures item by item against the ledger, and use maxResponse to observe whether the end of long table output is complete |
| Drill plan and sign-in sheet | Whether drill headcount and sign-in are consistent with the plan, and whether records match the plan | Compare the planned headcount with the sign-in headcount, check whether missing items are blocked, and use quoteMaxToken to check the tokens of quoted text |
| Access control and school bus inspection records | Whether access control and school bus inspection items are missing, and whether the responsible person is clear | Check the inspection item list and signatures item by item, and use maxContext to observe the range of context that can be accommodated |
| Responsibility handover form | Whether version and date are consistent, and whether the responsible person is clear | Check the version number and date, confirm the handover record fields are complete, then pass to the next step for receipt |
Three common errors
- Phenomenon: Some hazards in the hazard ledger are not closed loop, and the rectification deadline has passed without a review record. Cause: During material drafting, hazard items and rectification deadlines were not compared item by item, and the handover form only wrote the total number without details.
- Phenomenon: Drill records do not match the plan, and the sign-in headcount does not match the planned headcount. Cause: During drafting, the drill plan and sign-in sheet were not used as the comparison baseline, and missing items entered handover without being blocked.
- Phenomenon: Access control and school bus inspection items are missing, and the responsible person signature field is blank. Cause: Inspection records were not checked item by item, and during handover only the version and date were checked, not whether inspection items were complete.
How to verify the setup
This function's acceptance: ask a question that requires a long answer and see whether the ending is complete; if it breaks off mid-sentence, check whether the maxResponse slider position matches the answer length required by the page.
Business test: draft one according to the template and complete one handover, and see whether missing items are blocked.
- In application settings, check the response limit switch and slider position, compare usage from two runs, and confirm that the change in single-run usage matches the limit adjustment.
- Record the tokens of quoted text and the number of array entries separately;
quoteMaxTokenis the budget for quoted content, andmaxContextis the range of context that can be accommodated. Do not compare the two for equality.