What this category's data looks like
This page addresses the category materials for school safety hazard inspections and campus incident reporting, covering three types: safety inspection checklists, hazard rectification ledgers, and emergency incident reports. Safety inspection checklists are updated by inspection cycle, with fields including inspection item, hazard description, responsible person, rectification deadline, and signature; hazard rectification ledgers are updated by rectification closure, with fields including hazard name, quantity, rectification status, review date, and receipt; emergency incident reports are updated by the pace of incident occurrence, with fields including incident name, quantity involved, occurrence date, reporter, and acknowledgment record. When these three types of materials enter this feature, their roles differ: safety inspection checklists and emergency incident reports serve as source materials pending drafting and pending reporting, while hazard rectification ledgers serve as the basis for handover records. Field characteristics concentrate in four places: name, quantity, date, and signature. The same record must be consistent across the two materials, versions and dates must be synchronized, and a missing signature or receipt is blocked.
Configuration and implementation checks
This step is executed by the server-side model channel configuration, which outputs the model binding relationships and channel responses. The material drafts and handover records that can be issued are then completed by dialogue and retrieval using this model. Models fall into five categories: language, indexing, reranking, speech synthesis, and speech recognition, and different steps bind different model types.
| Object | Check | Verification action |
|---|---|---|
| Model type | Corresponds to the step to be used, and the type label is checked in the model configuration | Check whether the type label is consistent with the dialogue or retrieval step |
| Channel and key | Consistent with the connected service, and the channel configuration and key source are checked | Check the channel configuration and key source, and confirm whether the call can succeed |
| Model identifier | Consistent with the name listed in the documentation, and compared against the model name returned by the channel | Compare against the model name returned by the channel, and check the configuration items maxContext, maxTokens, toolChoice, and quoteMaxToken |
| Safety inspection checklists and hazard rectification ledgers | Name, quantity, date, and signature are consistent between the two types of materials | Compare item by item the name, quantity, date, and signature of the same record; a missing item is blocked |
Three common errors
- Symptom: The name, quantity, and date of the same record do not match between the safety inspection checklist and the hazard rectification ledger. Cause: During drafting, the same source field was not used as the basis, and the two materials were entered separately.
- Symptom: The material version is not synchronized, and the handover record references an old version. Cause: After the model binding relationship was updated, it was not synchronized to the dialogue and retrieval sides.
- Symptom: The emergency incident report lacks a signature or receipt, and the next step cannot acknowledge it. Cause: Field completeness was not verified before handover, and the responsible person was not clarified.
How to verify the setup
Feature acceptance: Run one dialogue and one retrieval, check the model identifier in the response, and confirm that the binding relationships of the language model and the indexing model are consistent with the model name returned by the channel.
Business test: Draft one copy according to the template and complete one handover, and see whether missing items are blocked.
- In the model configuration, check that the type label corresponds to the step to be used, and confirm that the channel and key source are consistent.
- Compare against the model name returned by the channel to check the model identifier, and check the configuration items
maxContext,maxTokens,quoteMaxToken, andtoolChoice.