What the documents look like
Creator sales campaigns depend on external creator fulfilment and commission settlement. The working materials are creator cooperation agreements, commission setup sheets, sample dispatch notes and livestream performance reports. In store service and internal training, these materials are entered into a knowledge base so frontline staff can retrieve them.
The material set updates per campaign and weekly. Retrieval configuration needs to fit that rhythm without assuming batch, full or real-time synchronisation.
A hypothetical drill sample is used throughout this page. The source text is a creator cooperation agreement: "Party A commissions Party B to conduct a dedicated sales session in a designated livestream room from 1 June 2025 to 30 June 2025. Party B's signature on this agreement indicates acceptance of the commission; the specific commission ratio is set out in Annex 1."
A draft sentence to be checked reads: "The creator has confirmed the June dedicated campaign and agreed to the commission ratio."
The retrieval request is: recall content related to "creator June dedicated campaign commission confirmation" from a knowledge base containing the agreement text above.
Constraints at the retrieval step
A knowledge base search node can associate one or more knowledge bases that use the same vector model. When two knowledge bases use different vector models, they cannot be associated together. The check is to compare vector model identifiers and exclude any knowledge base whose identifier does not match.
Semantic retrieval relies on vector distance. Full-text retrieval relies on keyword hits. Hybrid retrieval combines both paths through RRF. ReRank performs a second ordering of candidate text and returns a score between 0 and 1. The minimum relevance value applies only under semantic retrieval or when result reranking is used. It is a filter threshold, not a final ordering rule. The reference cap controls the amount of returned content in tokens.
Question optimisation runs before retrieval to resolve references and expand the question, adding one model call. Image retrieval depends on whether a vision model or an image-capable vector model is configured, and on whether image indexes were built at ingestion. Rerank requires a model and must be enabled by configuration. These optional paths do not run on every request.
Retrieval is not authorisation. A retrieved passage does not confirm that a signature was completed, that cooperation was reached, or that a contract took effect. Forms collect values; business verification, approval, database writes and external synchronisation need their own downstream implementation.
Configuration and implementation checks
| Configuration item | Hypothetical starting point for this drill | Reason and comparison method |
|---|---|---|
| Associated knowledge bases | Select the creator agreement base and the commission setup base, both using the same vector model | Compare vector model identifiers across the two bases; exclude any base whose identifier differs |
| Search mode | Hybrid retrieval | Compare semantic-path and full-text-path candidates, then observe the RRF-fused candidate set |
| Reference cap | Hypothetical starting value 2000 tokens | Test with agreement and performance-report fragments of different lengths; compare content completeness against a shorter cap |
| Minimum relevance | Hypothetical starting value 0.5 | Label relevant and irrelevant samples; compare the number of recalled items before and after filtering |
| Question optimisation | Enabled | Compare the original question with the optimised question; check whether the subject was altered |
| Result reranking | Enabled | Compare ordering before and after reranking; observe whether the score is used for filtering |
Three common errors
- Treating a retrieval hit as confirmation of authorisation. Input: the agreement text above and the draft sentence. Compare the draft phrase "has confirmed the campaign and agreed to the commission ratio" against the source wording "Party B's signature on this agreement indicates acceptance of the commission." The source states what a signature means; it does not state that a signature occurred. Observable result: the draft sentence exceeds what the source supports and is recorded as unsupported.
- Associating knowledge bases that use different vector models. Input: the vector model identifiers of the two knowledge bases. Compare whether the identifiers match. Observable result: when identifiers differ, exclude that base and do not perform cross-model retrieval. Do not assert leakage, redundancy or unpredictable behaviour as a consequence.
- Treating minimum relevance as a permission or entity filter. Input: the minimum relevance setting and the recalled results. Compare whether filtering changes which unrelated business records appear. Observable result: the score filters by relevance only; it does not exclude unauthorised records.
How to verify the setup
- Input the hypothetical agreement text and the draft sentence. Compare whether the draft sentence matches the source on the same subject, the same period and the same field. The source does not state that the signature was completed, so the draft sentence is judged unsupported. It is not judged as a denial or a contradiction. A contradiction requires the same field with mutually exclusive stated values.
- Input the retrieval request "creator June dedicated campaign commission confirmation" together with the associated knowledge base identifiers. Compare whether the vector model identifiers are consistent. If an identifier differs, exclude that base and record the gap. Do not run cross-model retrieval to compare missed recall.
- Input an empty reference array [] together with the downstream chain design. Compare whether the downstream chain still proceeds when the reference length is 0. Observe whether the downstream stage can accept an empty reference. Do not claim that a rule-based retrieval will necessarily return an empty array.
Across all three checks, a pending review does not demonstrate a lack of operating permission. Signing, reaching cooperation and contract effectiveness are three separate facts. The agreement text above does not include an authorisation or effectiveness clause, so that evidence gap remains open and is recorded as such.