What the documents look like
Community group-buy presale orders are collected before purchasing and fulfilment are organised. The document set for this category centres on the presale product table, the order-collection result, the purchasing plan and the cut-off notice. Materials update daily or per session. For store service and internal training, the recurring question is whether a statement about a product, a cut-off point or a purchasing arrangement can be supported by the wording of the document as it stood at that time.
Two consequences follow. A citation must be traceable to a specific document and a specific version. Traceability review must separate what the document states from what was added verbally. Because materials update frequently, the same product may carry a different status in the presale product table of a different session, so review has to lock onto one session.
The knowledge-base search node can associate one or more knowledge bases that share the same vector model. Its output is an array of citations, and the length may be zero; an empty array still passes through the output path. Whether a retrieval result is adopted depends on whether the answering step carries that citation forward and whether a person compares it against the original text item by item. The minimum relevance value is a filter threshold that takes effect only in semantic retrieval or when result reranking is used. It does not perform permission filtering or entity isolation. Hybrid retrieval merges multiple result paths through RRF, which is a result-fusion process. Image retrieval requires corresponding image input and model capability, and reranking requires a model and must be enabled in settings; these paths do not run on every request.
A hypothetical drill sample: a platform operator keeps an excerpt of "Session 12 Presale Product Table", with the original text "Product A, cut-off time 8 March 20:00, presale status is awaiting group formation". The cut-off notice excerpt for the same session reads "after the Session 12 cut-off, purchasing plan drafting begins; the group-formation result is subject to the order-collection result". The sentence to be checked is "Product A has been confirmed as formed and has entered the purchasing plan". That sentence concerns the subject Product A, the object Session 12, and the states of formed and purchasing plan. The original text gives only awaiting group formation and the statement that purchasing plan drafting begins after cut-off. It does not state a group-formation conclusion. The judgement is unsupported, and the original order-collection result must be supplied.
Constraints at the citation tracing step
The search scope is the knowledge base, which is the smallest search unit; collections inside it only classify data and do not affect search results. Before any comparison, confirm the vector model identifier of each selected knowledge base and exclude any that differ. Do not run a cross-model retrieval to compare missed recalls.
The citation array output may be empty. A paper input of [] can be used to check whether the downstream design still carries the empty citation through; this does not mean a given retrieval rule necessarily returns an empty array.
Minimum relevance is a 0-1 value that filters low-relevance results and applies only in semantic retrieval or with result reranking. It is a filter threshold, not a final ordering rule. It must not be recorded as a permission or entity-isolation measure.
The citation limit is expressed as a maximum number of tokens cited per search. Record it in that documented unit and keep it separate from retrieval-term quality review. Do not treat a thinking budget as a citation token limit.
Hybrid retrieval merges paths through RRF. Reranking requires a model and must be enabled in settings. Image retrieval requires image input and model capability. Record the actual enabled state; when reranking is not enabled, do not describe the output as a reranked result.
Configuration and implementation checks
| Configuration or check item | Documented basis | Implementation point for this page |
|---|---|---|
| Associated knowledge bases | Only knowledge bases with the same vector model can be associated; the knowledge base is the smallest search unit | Check the vector model identifier of each selected knowledge base, exclude mismatches, and record the actual observation |
| Citation output | Output is an array whose length may be zero | Use the paper input [] to check whether the downstream design carries an empty citation |
| Citation hand-off | Citation content is passed to the answering step | Compare the answer against the cited original text item by item and confirm the citation source can be located |
| Search mode and reranking | Hybrid retrieval merges through RRF; reranking requires a model and must be enabled | Record the actual enabled state; when not enabled, do not describe the result as reranked |
| Minimum relevance | A 0-1 value effective only in semantic retrieval or with result reranking | Record it as a filter threshold, not as a permission or entity-isolation measure |
| Citation limit | Each search cites at most n tokens of content | Record in the documented unit and check separately from retrieval-term quality |
Three common errors
- Reading "awaiting group formation" as "confirmed as formed". Input: the Product A original text above and the sentence to be checked. Comparison: the presale status field. The original value and the drafted value differ in the same field, so the sentence is unsupported.
- Treating a retrieval hit as authorisation or as an executed action. Input: the citation array returned by one retrieval. Comparison: the authorisation status field. The retrieval output carries no authorisation meaning, and whether the purchasing plan was drafted must be checked in the corresponding document.
- Associating knowledge bases that use different vector models. Input: the vector model identifiers of two knowledge bases. Comparison: whether the identifiers match. Different identifiers mean exclusion; do not proceed to a cross-model retrieval to compare missed recalls.
How to verify the setup
- Input: the two hypothetical original sentences and the sentence to be checked. Comparison: the same-field values "awaiting group formation" and "confirmed as formed". The check condition is met when the sentence to be checked is unsupported by the original text.
- Input: the paper empty citation array
[]. Comparison: whether the downstream answering step still passes through and the gap is recorded. The condition is met when the output path is not interrupted. Do not claim that a given rule-based retrieval necessarily returns an empty array. - Input: the list of vector model identifiers for the knowledge bases to be checked. Comparison: whether the identifiers match, excluding mismatches. The condition is met when the actual observation is recorded. Do not infer runtime behaviour after joint association.
Situations that are not stated, or that have only related-stage evidence, are recorded as pending verification. A pending review does not indicate a lack of operating permission. Signing, reaching cooperation and contract effectiveness are three distinct facts. A quotation validity period does not indicate a supply period.