What the documents look like
Wholesale stall trading is more fragmented than regional distributor replenishment. It relies on on-site price negotiation and consignment shipping, so purchase sheets, handwritten sales slips, stall lease contracts and payment receipts are often produced on the same day and updated with each order. Operating reports and exception reviews must reconcile materials spread across market quotations, stall inventory, WeChat payments and logistics consignment notes. The retrieval step has one job: recall these materials by subject, period and field as citable source text for human comparison. A retrieval result does not decide authorization.
A stall lease contract may state a lessor, a lessee, a lease term and a monthly rent due date. A payment receipt may state a date, an amount received, the sales slip it corresponds to, and an outstanding balance. These are the fields a reviewer compares when checking whether a drafted sentence about settlement matches the source records.
Constraints at the retrieval step
The knowledge base search node can associate one or more knowledge bases that use the same vector model. Its output is an array of cited content, and the length can be zero; the output path still runs when nothing is found. Hybrid search merges multiple result paths through RRF. Reranking requires a model and must be enabled by configuration. Image retrieval requires image input and matching model capability. These paths do not all execute on every request. The minimum relevance value takes effect only under semantic search or result reranking. The citation limit is measured in tokens. Semantic similarity does not establish permission or entity isolation; retrieving a material does not mean that material is authorized for a particular settlement.
Hypothetical drill sample. Source material for comparison: (1) "Stall lease contract (Sample A): the lessor is a market management office, the lessee is a stall operator, the lease term runs from 1 March 2025 to 28 February 2026, and monthly rent is payable by the 5th of each month." (2) "Payment receipt (Sample B): on 12 April 2025, a purchaser's payment of 8,000 yuan was received, corresponding to the goods listed on the handwritten sales slip of 10 April; the remaining 2,000 yuan is unsettled." Draft sentence to be assessed: "The lessee under Sample A settled all payments listed in Sample B in April 2025." The subject is the stall operator, the object is the Sample B payment, and the stated status is fully settled. Sample B records a remaining 2,000 yuan unsettled, with the same subject, same period and same field, so the values are mutually exclusive.
Configuration and implementation checks
| Configuration item | Hypothetical starting point for this drill | Reason and comparison method |
|---|---|---|
| Associated knowledge bases | Associate only stall-trading bases sharing one vector model | Check each base's vector model identifier first; exclude those that differ; do not associate across models |
| Search mode | Use semantic search and full-text search together | Compare the two recall paths on the same test question; observe differences for coded and natural-language questions |
| Citation limit | Hypothetical starting value 3,000 tokens | Because sample materials vary in length, compare whether cited content is truncated for long and short materials, then adjust |
| Minimum relevance | Hypothetical starting value 0.4 | Mark relevant and irrelevant samples by hand first; compare results on each side of the threshold; confirm it applies only under semantic search or reranking |
| Question optimization | Enable for multi-turn follow-ups | Compare the original question with the optimized question; check whether subject, object and period were altered |
| Result reranking | Enable when a rerank model is available | Compare candidate order before and after reranking; observe how the 0-1 score interacts with citation-limit trimming |
Three common errors
- Treating a retrieval hit as authorization. Input: a retrieval result for the Sample B payment receipt. If this is used to decide that the payment can be settled, recall has been confused with authorization. Check by comparing the retrieval output against authorization materials and observing whether approval or signature records exist.
- Forcing association across vector models. Input: two knowledge bases with different vector model identifiers. Merging them directly is a configuration error. Check by verifying each base's vector model identifier, excluding those that do not match, and recording the observation without asserting a runtime result.
- Using a similarity threshold as an entity filter. Input: a mixed base containing multiple stall subjects. Assuming that raising minimum relevance excludes unrelated stalls is a misuse. Check by comparing the recalled subject composition before and after the threshold change and observing whether unrelated subjects are still recalled.
How to verify the setup
- For the draft sentence "The lessee under Sample A settled all payments listed in Sample B in April 2025," input the Sample B source text and the draft sentence. Compare the values for the same subject, same period and same field. Sample B records a remaining 2,000 yuan unsettled, and the draft sentence's value is mutually exclusive with the source. The draft sentence is not supported.
- For the citation limit, input long and short materials with the same test question. Compare whether the cited content is complete. Observe whether short materials remain complete and long materials are truncated, and record the item for adjustment.
- For empty-result handling, input a paper retrieval result of []. Compare whether the downstream design handles a citation array whose length can be zero, and observe whether the path runs. Do not claim that a fictional rule search necessarily returns [].
This page addresses only wholesale stall trading, operating reports and exception reviews, and knowledge base retrieval and recall. At operational handover, which materials, operations and requests are in what authorization state cannot be treated as authorized execution by retrieval or a form.