What this category's data looks like
This page addresses the scenario of vocational college skills competition organization, where the core materials are competition regulations, registration forms, and training plans. Competition regulations are issued by the organizer and contain the event name, group, date, signature field, and version number, and serve as the baseline for judgment; registration forms are filled in by participating teams and contain competitor names, quantities, identity information, and team leader signatures; training plans are submitted by instructors and contain training cycles, number of class hours, and phase objectives. When these three types of materials enter the knowledge base retrieval node, each is cited as an independent source, and cited snippets point back to the original paragraphs. In terms of update cadence, regulations are re-versioned as events are adjusted, registration forms undergo multiple rounds of revision before the deadline, and training plans roll over monthly. Field characteristics center on five items: name, quantity, date, signature, and receipt. If any material version is not synchronized or lacks a signature, discrepancies will be exposed during cross-material comparison.
Configuration and implementation checks
This step is executed by the citation output of the knowledge base retrieval node, which outputs an array of cited content, each entry containing the original snippet and source identifier, and the length may be 0. The discrepancy list is then completed by subsequent AI nodes, code nodes, or manual work. Even if no content is found, the output chain still runs through.
| Object | Check | Verification action |
|---|---|---|
| Competition regulations | The event name, group, date, and signature field must match the registration form and training plan item by item | Open the citation marker and verify the name, quantity, date, and signature against the source document; record the array length and the quoteMaxToken budget |
| Registration form | Competitor names, quantities, team leader signature, and receipt must align with the regulations and training plan | Use one real record to compare the ledger fields and check whether the cited snippets in responseData (non-streaming module results returned with detailed output enabled) point back to the original text |
| Training plan | The training cycle, number of class hours, and phase objectives must be consistent with the regulation dates | Check the version number and submission date, and inspect whether citations can still be traced when signatures or receipts are missing |
| Knowledge base retrieval node | Cited content is output as an array, the length may be 0, and an empty array is a normal output | Run a trial query with no matching materials to confirm the output is empty while the chain continues, and inspect the quoteList record |
Three common errors
- Symptom: the same competitor's name or quantity does not match across two materials. Cause: after multiple rounds of revision to the registration form, the version was not synchronized, the old version is still hit by retrieval, and the cited snippet comes from an outdated paragraph.
- Symptom: the regulation date conflicts with the training plan cycle. Cause: after the event was adjusted, the regulations were re-versioned, the training plan was not written back, and the two materials each entered retrieval independently without cross-material field comparison.
- Symptom: the cited snippet does not match the original text. Cause: the node only outputs the array of cited content and does not generate a discrepancy list; first check whether this round hit anything and which material was hit, then look at trimming.
How to verify the setup
Feature acceptance: ask a question with source-text support and check whether the citation array and markers point back to the original text; then ask a question with no matching materials and confirm the array is empty while the chain runs through.
Business testing: use one real record to find a field inconsistent with the ledger, have the reviewer confirm it, and write it back.
- In the node, check whether the selected knowledge base collections and their vector models are consistent, and open the search parameter panel to verify the values item by item.
- For each citation record, compare the array entry count with the
quoteMaxTokenbudget; record the count separately and do not compare it for equality with the budget.