What the documents look like
Brand after-sales repair work runs on warranty responsibility and physical service points. Store service staff, repair outlets and the brand after-sales center jointly handle warranty cards, repair work orders, inspection reports and replacement approvals. These materials record purchase information, fault symptoms, inspection conclusions and approval status respectively. A missing field in any one material leaves source verification at pending. Data updates per order and per day. During store handover, staff must distinguish whether a material currently sits at intake, inspection, awaiting approval or approved. A retrieval match does not substitute for an authorization judgment.
For citation tracing, this category matters because the training audience reads draft statements that mix work order facts, inspection conclusions and approval status. Each of those facts lives in a different document, and the status field is the one most easily overstated. The following hypothetical sample uses only invented identifiers and is labelled as a paper exercise.
Hypothetical drill sample: a store service staff member submits a draft sentence for internal training citation: "Work order WX-2024-0517 has passed replacement approval and the customer can be notified for pickup." The three source sentences supplied for comparison are: first, "Work order WX-2024-0517, intake date 17 May 2024, fault symptom is screen flicker." Second, "Inspection report number JC-0517, inspection conclusion is screen ribbon cable fault, within warranty scope." Third, "Replacement approval form HP-0517, approval status is pending review, approver field blank." The draft sentence states that approval has passed, which conflicts with the third sentence on the same field. The pickup notification concerns an authorization action, and the materials do not record it.
Constraints at the citation tracing step
The knowledge base search node can associate one or more knowledge bases that share the same vector model, and it outputs citation content as an array whose length may be zero. When the array is empty, the output chain still runs through. The minimum relevance value takes effect only under semantic retrieval or result reranking, and it acts as a filter threshold; it does not perform permission or entity isolation. The citation limit is controlled by tokens and is unrelated to the thinking budget. Hybrid retrieval merges multiple result paths through RRF, and reranking requires a configured model enabled by setting. Image retrieval requires image input and model capability. Knowledge bases with different vector models cannot be associated together; verify the vector model identifier and exclude non-matching bases rather than running cross-model retrieval to compare missed recalls.
For the drill sample, the draft sentence and the approval form share the same subject and the same approval status field, and their values are mutually exclusive. That makes the draft unsupported by the supplied materials. The pickup notification is a business action the materials do not record, so it remains an evidence gap. Pending review does not by itself prove the absence of operating authority.
Configuration and implementation checks
| Configuration or check item | Hypothetical starting point for this drill | Reason and comparison object |
|---|---|---|
| Associated knowledge bases | Store after-sales material base only | Verify the vector model identifier of the selected base matches; exclude bases with a different model |
| Search mode | Hybrid retrieval | Work order numbers and report numbers are exact queries, compared with pure semantic retrieval |
| Minimum relevance | Starting value 0.5 | A hypothetical value for this drill, to observe how the number of citations changes after filtering |
| Citation limit | Starting value 2000 tokens | A hypothetical value for this drill, compared with the combined length of the work order and report text |
| Result reranking | Enabled | Requires a configured rerank model; compared with the ordering when not enabled |
| Citation output handoff | Citation array passed to the answering step | Compare each answer statement against the cited source text; treat an empty array as zero length |
Three common errors
- Treating a retrieval match as approval. Input is the draft sentence and the approval form text; compare the approval status field values; the observable result is that "pending review" and "has passed" are mutually exclusive, so the draft sentence is unsupported.
- Treating minimum relevance as a permission filter. Input is a cross-store work order query; compare the returned citations against the requester's authorization scope; the observable result is that the relevance score does not distinguish store ownership, so authorization must be checked separately.
- Treating an empty citation array as a process error. Input is a paper citation array []; compare the downstream node design; the observable result is that the chain continues to run, and whether an error is raised depends on the downstream implementation, which the documents do not state.
How to verify the setup
- Input the three source sentences and the draft sentence from the drill sample, compare the approval status field, and if the citations present only "pending review" and the answer does not contain "has passed approval," source verification passes; if "has passed" appears, it fails.
- Input work order number WX-2024-0517 as a full-text query, compare the returned citation against the source number, and if the citation contains that work order without mixing in other work orders, number tracing passes; when there is no match, record it as pending and do not infer a cause.
- Input a paper citation array [], compare whether the downstream node continues execution, and if the chain runs through without producing a pickup notification action, empty-result handoff passes; any automatic notification is a business action the documents do not record.
These checks compare the same subject over the same period on the same field. Only mutually exclusive values on one field constitute a contradiction. Unrecorded facts and stage-only evidence remain unsupported or pending.