What the documents look like
Inbound receiving and put-away is the first book-to-physical confirmation when goods enter the warehouse. The working records are the purchase arrival note, the inbound acceptance sheet, the put-away task, and the discrepancy report. Operational reporting and exception review depend on tracing a reported figure back to a specific document, and the citation tracing step determines whether a review conclusion can rest on checkable source text.
The material set is narrow and concrete. A purchase arrival note states what was expected. An inbound acceptance sheet records what was counted and who signed. A put-away task states a location and a task status. A discrepancy report states a variance. Each of these carries a different subject, a different field, and a different stage, so a traced citation must match the same subject, the same period, and the same field before any conclusion is drawn. When tracing is loose, inventory records diverge from physical stock, later picking draws on wrong quantities, and supplier disputes lack a defensible paper trail.
Constraints at the citation tracing step
The knowledge base search node outputs cited content as an array, and the length may be zero. The output path still runs even when nothing is retrieved. A knowledge base selection may combine one or more knowledge bases that share the same vector model; knowledge bases built on different vector models cannot be associated together, so the identifier is checked and non-matching libraries are excluded first. The minimum relevance setting takes effect only under semantic retrieval or when result reranking is used. It is a filter threshold and does not act as a permission or entity isolation control; retrieval itself is not authorization. Hybrid retrieval merges multiple result paths through RRF, reranking requires a rerank model enabled by configuration, and image retrieval requires image input plus model capability. These optional paths are not executed on every request.
Assumed drill sample: an inbound acceptance sheet reads "purchase arrival note PO-2024-0517, supplier delivery note DN-8891, expected quantity 200 pieces, received quantity 196 pieces, variance 4 pieces, acceptance signature: signed, date 17 May 2024." A put-away task reads "task number SH-0517-03, linked to PO-2024-0517, assigned location A-12-03, put-away quantity 196 pieces, status is pending execution." A draft sentence awaiting judgment reads "the supplier has confirmed replenishment for this batch variance, and inventory has been adjusted." The sample is used only to check citation and tracing, and does not indicate that any business action occurred.
Configuration and implementation checks
| Configuration item | Assumed trial starting point | Reason and comparison method |
|---|---|---|
| Associated knowledge bases | Select the knowledge bases holding the purchase arrival note, inbound acceptance sheet, put-away task, and discrepancy report | Check whether the vector model identifier is the same across libraries; exclude those that differ |
| Search mode | Hybrid retrieval | The sample contains the identifier PO-2024-0517, so keyword and semantic recall are both needed; compare against semantic retrieval alone |
| Citation limit | Set for this trial to cover the body text of the four sample documents | Compare against the sample text length and confirm all four documents can be contained |
| Minimum relevance | Set for this trial to 0.5 | Compare against the retrieval score of the sample draft sentence and observe whether source text is filtered out |
| Result reranking | Enabled | The sample candidates span several documents; compare against ordering without reranking |
| Cited content output | Accept the array, allowing length zero | Use the paper input [] to check the downstream branch design |
Three common errors
- Treating a retrieval hit as authorized execution. In the sample, the put-away task status is "pending execution." Retrieving that task does not mean put-away was approved or that inventory was adjusted. The node's existing behavior, the configurable fields, and the business actions that require a separate system implementation must be kept distinct.
- Treating a draft sentence as a verified conclusion. The draft sentence states supplier-confirmed replenishment and adjusted inventory. The sample source text records only a 4-piece acceptance variance and an acceptance signature; it records no supplier confirmation and no inventory adjustment. This is unsupported, and it is not a contradiction or a negation.
- Forcing association across knowledge bases with different vector models. Where the sample knowledge bases carry different vector model identifiers, the identifier is checked, non-matching libraries are excluded, and the actual observation is recorded. A cross-model retrieval is not executed to compare missed recall.
How to verify the setup
- Input the sample inbound acceptance sheet text and the draft sentence, then compare whether "supplier confirmed replenishment" appears in the source text. When the source text does not carry that content, the finding is unsupported and the evidence gap is preserved.
- Input the sample put-away task text, then compare whether "status is pending execution" and "inventory has been adjusted" share the same subject, the same period, and the same field. The two belong to different fields, so they do not form a contradiction, and a pending status does not indicate a missing operating permission.
- Input the paper citation array [], then compare whether the downstream answer step still runs. Observe whether the empty array interrupts the chain; the expected behavior is that it runs, without claiming that a fictional rule retrieval necessarily returns [].