What this category's data looks like
Materials for kindergarten home-school co-education communication come from sources including kindergarten notices, class weekly plans, child observation records, parent feedback, and commitment items. After these materials enter the knowledge base retrieval node, each plays a different role: notices and weekly plans serve as the basis for the current version, observation records serve as the original source for descriptions of child performance, and parent feedback and commitment items serve as the comparison draft for request classification and response time limits. The update cadence is weekly, with same-day supplementary entry for temporary adjustments. Field characteristics are concentrated in four categories: commitment items and response times, descriptions of child performance, parent request classification, and notice delivery. The version ledger and change records are generated by subsequent nodes or manually by comparing fields accordingly; the cited content array is only responsible for providing original text snippets and source identifiers, and does not assume the responsibility of a difference list or ledger.
Configuration and implementation checks
This step is executed by the citation output of the knowledge base retrieval node, which outputs a cited content array, each entry containing an original text snippet and a source identifier, and the length may be 0. The "version ledger and change records" are then completed by subsequent AI nodes, code nodes, or manually.
| Object | Check | Verification action |
|---|---|---|
| Associated knowledge base | The selected knowledge base uses the same vector model and covers the two categories of materials: commitment items and response times, and descriptions of child performance | In the node, check the selected collections and their vector models, and confirm that both categories of materials are in the collections |
| Cited content output | The number of returned entries matches the materials hit; empty is also normal; when notice delivery materials are hit, the snippet should include the delivery time | Run a test with a question that has no matching materials, see that the output is empty while the chain continues, and record the array length and the quoteMaxToken budget |
| Citation-to-original correspondence | Each citation can point back to the original paragraph, and parent request classification and observation record wording should match | In the conversation, open the citation marker, compare against the source document, and check whether the snippets in responseData (non-streaming module results returned with detailed output enabled) and detail are consistent |
| Search parameters | Consistent with the values set in the knowledge base retrieval section; the citation limit only constrains the tokens of the cited text | Open the search parameters panel and check item by item; record the array entry count separately and do not compare it for equality with the citation limit |
Three common errors
- Symptom: A commitment item is mentioned in the answer, but the original text has no corresponding response time. Cause: The commitment and the response time belong to two separate materials, and the citation only hit the commitment one, not the response record.
- Symptom: The description of child performance does not match the wording in the observation record. Cause: A summary expression from an old weekly plan was cited, and the current observation record did not enter the materials hit in this round.
- Symptom: Parent requests are not classified and are mixed together in the answer. Cause: The feedback materials were not organized by the request classification field; the citation array only provides original text snippets and does not perform classification.
How to verify the setup
Acceptance for this feature: ask a question with an original-text basis and check whether the citation array and markers can point back to the original text; then ask a question with no matching materials, confirm that the array is empty while the chain runs through, and record the array length and the quoteMaxToken budget.
Business test: change one piece of content and see whether the version number and citations update synchronously, and whether the old version can still be traced.
- Open the citation markers, compare item by item against the source documents, and confirm that the snippets in
quoteListwithinresponseDatacan point back to the original paragraphs. - Run a test with a question that has no matching materials, confirm that the citation array is empty while the chain continues, and record the array length separately.