What this category's data looks like
This page addresses the school safety hazard inspection and campus incident reporting scenario. The materials include three categories: safety inspection checklists, hazard rectification ledgers, and emergency incident reports. Safety inspection checklists are filled in item by item at each point by the inspector, recording the inspection date, hazard description, and signature; the hazard rectification ledger carries forward the conclusions of the checklists, registering the rectification responsible person, deadline, re-inspection results, and receipt; emergency incident reports are formed after the incident, stating the time, location, personnel involved, handling process, and reporting signature. After these three categories of materials enter the knowledge base retrieval node, each plays a different role: the checklist provides the points and the basis for determination, the ledger provides the rectification closed loop and the chain of responsibility, and the incident report provides the factual draft for external statements. In terms of update cadence, checklists are updated weekly or per inspection, ledgers are updated on a rolling basis along with rectification progress, and incident reports are archived once per incident. Field characteristics center on names, quantities, dates, signatures, and receipts. Differences in how the same hazard is expressed across different materials are the focus of subsequent comparison. For external services, the scope visible to parents or superiors is determined by authorization; the materials themselves do not carry permission information.
Configuration and implementation checks
This step is executed by the citation output of the knowledge base retrieval node, which outputs an array of citation content, each entry containing the original text fragment and a source identifier, and the length can be 0. "Externally available entry points and authorization scope" are completed subsequently by AI nodes, code nodes, or manual work. The citation content is output as an array; even if no content is found, the output chain still runs through.
| Object | Check | Verification action |
|---|---|---|
| Safety inspection checklist | Whether the inspection date, hazard name and quantity, and inspector signature are consistent with the first row of the ledger | Locate the fragment of this checklist in the citation array, and compare it against the name, quantity, date, and signature field of the same point in the ledger |
| Hazard rectification ledger | Whether the rectification deadline, re-inspection results, and receipt signature are complete and correspond to the checklist conclusions | Open the citation superscript to point back to the original ledger text, check the rectification status and signature field in quoteList, and record missing items separately |
| Emergency incident report | Whether the incident time, personnel involved, reporting signature, and external statement wording are consistent | Access once with a restricted identity, and check whether the visible scope covers only authorized materials; unauthorized entries must not be visible |
| Citation content output | Whether the number of returned entries matches the materials hit; being empty is also normal | Run a test with a question that matches no materials, and see whether the output is empty while the chain continues; when the citation limit is involved, check the tokens of the citation text, and record the number of array entries separately |
Three common errors
- Symptom: the name and quantity of the same hazard do not match between the checklist and the ledger. Cause: the two entries use different wording, or the ledger does not backfill the checklist conclusions, causing field conflicts in external statements.
- Symptom: the rectification ledger version is not synchronized, and re-inspection results and receipts are missing. Cause: the ledger was not updated after rectification was completed, or an old version is still participating in retrieval in the knowledge base, so citations point to outdated paragraphs.
- Symptom: there is an answer but the citation array is empty, or the citation fragments do not match the original text. Cause: no materials were hit in this round, or a different material was hit; an empty array is a normal output and is not directly attributed to length truncation. First check the hit situation, then look at truncation.
How to verify the setup
This feature's acceptance: ask a question with original-text support, check whether the citation array and superscripts can point back to the original text, and check whether the number of citations in responseData (non-streaming module results returned with detailed output enabled) matches the materials hit; then ask a question with no matching materials, and confirm that the array is empty while the chain runs through.
Business test: access once with a restricted identity, and see whether the visible scope matches the setting, with unauthorized entries not visible; when the citation limit is involved, check the tokens of the citation text, record the number of array entries separately, and treat quoteMaxToken only as a content budget.
- In the node, check whether the selected knowledge base collections and their vector models are consistent, and open the search parameter panel to check the values item by item.
- In the conversation, open the citation superscripts, compare each citation against the source document to check whether it can point back to the original paragraph, and list separately the entries missing signatures or receipts.