What the documents look like
Livestream product selection and sample quality inspection happen before a broadcast. The work decides whether a product can be sold on air and whether it suits live presentation. Source material includes supplier files, testing-agency reports, platform negative catalogs, and historical return rates. Daily documents include sample evaluation forms, quality inspection reports, supplier qualifications, and prohibited-sale lists. These materials together define the retrieval scope for purchasing and stocking. Retrieval returns reference content only; it does not constitute qualification verification, authorization, or purchasing approval.
Constraints at the retrieval step
The knowledge base search node can associate one or more knowledge bases that use the same vector model. Bases built on different vector models cannot be associated together. Check the model identifier first, exclude any base that does not match, and record what was observed. Search output is an array, and its length can be 0; the empty-result path still completes. The reference limit is measured in tokens. The minimum relevance score takes effect only under semantic search or when result reranking is used. Question optimization performs coreference resolution and question expansion and adds an extra model call. RRF is the fusion process for hybrid retrieval results and is not described as a standalone switch. Image retrieval requires image input and the corresponding model capability. Reranking requires a model and is enabled according to settings. Retrieval and similarity scores do not perform permission or entity isolation.
Hypothetical drill sample: a supplier file states, "Sample evaluation form number SP-0417 for this batch, corresponding to inspection report QR-2291; the report concludes the batch meets the platform's current listing requirements, valid until June 30, 2025." A separate handover request states, "Based on the above materials, confirm this supplier has passed qualification review and purchasing can be arranged." What the materials establish is the sample, the report, and the validity period recorded in the text. Qualification review and purchasing authorization are not stated in the source text and remain to be verified.
Configuration and implementation checks
| Configuration item | Hypothetical trial starting point | Verification method |
|---|---|---|
| Associated knowledge bases | Associate only the quality inspection base and supplier base whose vector model identifiers match | Check model identifiers, exclude non-matching bases, and record the observation |
| Search mode | Test the same question separately with semantic search and full-text search | Compare recall differences between number-type and natural-language questions |
| Reference limit | Set to the token volume needed to cover one complete inspection report | Compare content completeness against actual materials of differing lengths |
| Minimum relevance score | Annotate relevant and irrelevant samples first, then adjust | Observe whether relevant samples survive filtering |
| Question optimization | Enable in multi-turn follow-up scenarios | Compare whether the subject in the original question and the optimized question stays consistent |
| Result reranking | Enable according to settings when candidates are numerous | Compare ordering changes of relevant content before and after reranking |
These values are hypothetical trial starting points, not official defaults.
Three common errors
- Treating a retrieval hit as a passed qualification review or a completed purchasing authorization. Input is the supplier material returned by retrieval; compare whether it states a review conclusion and an authorization scope; observe whether the result contains only material content with no authorization fact.
- Associating knowledge bases that use different vector models. Input is the model identifiers of the two bases; compare whether they match; observe whether exclusion and recording happen before association.
- Treating the minimum relevance score as a permission or entity filter. Input is the similarity score and the access scope; compare whether changing the score setting alters authorization records; observe whether unrelated or unauthorized records can still be recalled.
How to verify the setup
- Using the hypothetical sample text "Sample evaluation form number SP-0417 for this batch, corresponding to inspection report QR-2291; the report concludes the batch meets the platform's current listing requirements, valid until June 30, 2025," enter the retrieval question "What is the inspection conclusion for SP-0417?" Compare whether the returned reference contains that report conclusion and validity period. The condition is satisfied when the reference content matches the source text.
- Using the draft sentence "Based on the above materials, confirm this supplier has passed qualification review and purchasing can be arranged," enter it into retrieval or handover checking. Compare whether the materials state review and authorization. The condition is satisfied when the result presents only material content and the review and purchasing authorization remain marked as pending verification.
- Using the paper input of an empty array
[]to check the downstream design, compare whether the empty-result path completes. The condition is satisfied when the downstream does not interpret the empty result as no risk or as approved. All of the above are paper expectations and were not actually executed.