What this category's data looks like
This page addresses the school safety hazard inspection and campus incident reporting scenario. The source materials are daily safety inspection forms, hazard rectification ledgers, and emergency incident reports, updated on a rolling basis according to inspection cycles, rectification milestones, and incident occurrence times. Safety inspection forms record the inspection date, location, hazard description, and inspector signature; hazard rectification ledgers record the hazard name, quantity, rectification deadline, acceptance date, and responsible person's signature; emergency incident reports record the incident name, number of people involved, occurrence date, reporting time, and receipt signature. When these three types of materials enter this feature, each plays its own role: safety inspection forms provide clues for hazard discovery, hazard rectification ledgers provide closure status, and emergency incident reports provide the basis for reporting and receipts. Field characteristics are concentrated in four categories: name, quantity, date, and signature. These must correspond item by item with the authorization scope of the external entry point, ensuring that the entries seen by parents or superiors match their identity.
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 externally available entry point and authorization scope are determined by the publishing service and file permissions. The model only processes filtered materials; the publishing service and file permissions handle identity and file authentication.
| Object | Check | Verification action |
|---|---|---|
| Safety inspection form | The inspection date, location, hazard description, and inspector signature are complete, and match the hazard name, quantity, and date in the hazard rectification ledger | Check the memory turns value in the app settings, run a trial with two consecutive follow-up questions, check whether the second round can carry forward the first round's reference to the hazard name, and review the preceding context range in messages |
| Hazard rectification ledger | The rectification deadline, acceptance date, and responsible person's signature are complete, and the name, quantity, and date of the same record match across the safety inspection form and the emergency incident report | Retrieve the fields of the same hazard from the three materials and compare them item by item, confirm version synchronization, mark missing signatures or receipts as pending supplementation, and record the conversation scope corresponding to chatId |
| Emergency incident report | The incident name, number of people involved, occurrence date, reporting time, and receipt signature are complete, and are consistent with the date chain in the hazard rectification ledger | Access the external entry point once with a restricted identity, check whether the visible entries match the identity, ensure unauthorized entries are not visible, and check the authorization scope variables passed in variables |
Three common errors
- Symptom: The name, quantity, and date of the same hazard do not match between the safety inspection form and the hazard rectification ledger. Cause: The two materials are filled in separately, without cross-checking and version synchronization.
- Symptom: The emergency incident report lacks a signature or receipt, and the entries seen by parents or superiors cannot be traced. Cause: The reporting process did not collect all signatures, and the receipt was not returned before publishing.
- Symptom: When pronouns are used in the second question, the answer is off-topic, responses become slower, and consumption rises. Cause: The memory turns value is too large and brings in irrelevant preceding context, or too small and cannot use the preceding context, or the opening message is treated as preceding context.
How to verify the setup
Feature acceptance: Ask two consecutive follow-up questions, see whether the second question carries forward the first question's reference, and check the memory turns value and the messages reference range in the app settings.
Business test: Access once with a restricted identity, see whether the visible range matches the settings, and ensure unauthorized entries are not visible.
- Check the current memory turns value in the app settings, run a trial with two consecutive questions, and compare the usage records of the two runs.
- Retrieve the safety inspection form, hazard rectification ledger, and emergency incident report, check the name, quantity, date, and signature item by item, and confirm version synchronization.