What the documents look like
Wholesale market stall trading runs on on-site price negotiation and consignment shipping, so the paperwork is scattered across several document types: purchase sheets, handwritten sales slips, stall lease contracts and payment receipts. Updates arrive daily or per order. A single transaction can produce more than one text, and handwritten and printed content sit side by side in the same file set.
The core work of contract and transaction material comparison is to trace each cited passage back to a specific field in a specific material, then confirm whether the subject, object, amount, date and status agree. Because materials are fragmented, a citation source must be locatable to a single document. When a source is missing, the gap is recorded rather than filled.
The knowledge base search node can select one or more knowledge bases that share the same vector model, and it outputs citations as an array whose length may be zero. When the array is empty, the output path still completes. Whether retrieved results reach the answer step, and whether the answer corresponds line by line to the cited original text, requires manual checking. The minimum relevance score takes effect only under semantic retrieval or result reranking; it is a filter threshold and does not perform permission or entity isolation. The citation limit controls the maximum content cited per search, measured in tokens. Hybrid retrieval merges multiple result paths through RRF, reranking requires a model and must be enabled by configuration, and image retrieval requires image input plus model capability.
Constraints at the citation tracing step
Hypothetical drill sample. A stall operator and a purchaser produce two materials for one batch of goods. Material one is a handwritten sales slip reading: "Received from purchaser A three thousand yuan in payment today; goods not shipped; shipping by consignment agreed within three days." Material two is a stall lease contract reading: "This contract runs from January 1, 2024 to December 31, 2024; rent payable quarterly." The draft sentence to be assessed is: "Purchaser A has paid and the goods were shipped on the agreed date."
Comparison requires the same subject, the same period and the same field. The sales slip states payment received and a not-shipped status, so the draft sentence's statement about shipping is not supported by that material. The lease contract has no bearing on shipping facts and does not constitute shipping evidence. The draft sentence is therefore partly supported and partly unsupported; the unsupported part remains a recorded gap.
Three constraints follow. First, a retrieval hit is not an authorization or a fact confirmation: the sales slip showing payment received supports the payment fact, while shipping status must be checked against the original wording. Second, knowledge bases with different vector models cannot be jointly associated; the model identifiers are checked first and non-matching bases are excluded and recorded. Third, a pending status cannot be written as completed. Signing, reaching cooperation and contract effectiveness are three distinct facts.
Configuration and implementation checks
| Configuration item | Hypothetical starting point for this drill | Reason and comparison method |
|---|---|---|
| Associated knowledge bases | Select the two bases holding the sales slip and the lease contract | Check the vector model identifier of both bases first; associate only if identical, otherwise exclude |
| Search mode | Hybrid retrieval | The handwritten slip contains exact items such as amount and date; compare whether citations cover both materials after merging with semantic recall |
| Citation limit | Set to a token amount covering the full text of both materials | Compare against the combined length of the two materials; confirm the limit is not below that total |
| Minimum relevance score | Leave at the current setting for this drill | Compare against the number of returned results and observe whether low-relevance fragments enter the citations |
| Question optimization | Off for this drill | The draft sentence has a clear subject; compare retrieval time against the enabled case |
| Citation handoff | Check whether the output array reaches the answer step | Compare the answer against the cited original text item by item and record non-matching entries |
Three common errors
- Treating a retrieval hit as authorization or fact confirmation. The sales slip shows payment received and retrieval returns that citation, so the payment fact holds; shipping status must still be checked against the original wording, and retrieval itself produces no shipping authorization.
- Forcing knowledge bases with different vector models into a joint association. When the two model identifiers differ, the association condition does not hold; the non-matching base is excluded and recorded, and no cross-model retrieval is run to compare missed recalls.
- Writing a pending status as completed. If the shipping referenced by the draft sentence is still awaiting arrangement, it can only be recorded as unsupported; signing, reaching cooperation and contract effectiveness are three separate facts.
How to verify the setup
- Enter the sales slip original text and the draft sentence from the hypothetical sample. Compare the draft sentence's phrase "the goods were shipped on the agreed date" against the original phrase "goods not shipped." When the original does not state shipping, the result is unsupported, not contradictory.
- Enter the lease contract original text and the same draft sentence. Compare the contract's lease period field against the shipping field. The two are not the same field, so the result is irrelevant evidence and the gap is recorded.
- Use a paper input of an empty array to check the downstream handoff design. Observe whether the answer step still receives input normally when citations are zero. Do not claim that a fictional rule search necessarily returns an empty array.
This page addresses only wholesale stall trading, contract and transaction material comparison, and citation tracing. Operational handover must not treat retrieval or a form as authorization to execute.