What the documents look like
Creator commission settlement and deduction materials centre on commission setting records, settlement statements, refund deduction details and invoices. These materials are produced by the Selected Alliance backend, order after-sales data, the finance system and creator contracts. The typical roles involved are finance settlement, Selected Alliance operations and creator business affairs. Errors here lead to creator disputes, incorrect finance entries and stalled cooperation.
Procurement and supplier materials sit in the same knowledge base as a separate class of records, covering purchase batches, supplier entities, supply scope and price validity periods. When retrieving this class of material, supplier entity, purchase object, batch scope and authorization status serve as the fields to check, so that settlement definitions are not applied to procurement records.
Constraints at the retrieval step
The knowledge base search node can associate one or more knowledge bases that use the same vector model. Knowledge bases using different vector models cannot be associated together; verify the vector model identifier first, exclude those that do not match, and record the actual observation. Search modes are semantic retrieval, full-text retrieval and hybrid retrieval; hybrid retrieval merges multiple result paths through RRF, and RRF is a fusion process rather than a standalone switch. Minimum relevance takes effect only under semantic retrieval or when result reranking is used; it is a filter threshold and does not perform permission or entity isolation. Retrieval output is an array whose length can be 0, so the output path still runs even when no content is found.
Hypothetical paper test sample. Source text one: "Supplier A, purchase object disposable paper cups, batch 2026-03, supply scope limited to the East China warehouse, price valid until 2026-03-31." Source text two: "Supplier A, purchase object disposable paper cups, batch 2026-04, supply scope limited to the South China warehouse, price valid until 2026-04-30." Draft sentence: "Supplier A's paper cup supply scope for 2026-03 covers both the East China warehouse and the South China warehouse." The check compares the entity, object, period and supply scope fields. Both source texts point to the same supplier and the same purchase object, while the batch and supply scope differ. The draft sentence merges the scopes of two batches, so it is unsupported.
Configuration and implementation checks
| Configuration item | Hypothetical starting point for this test | Reason and comparison method |
|---|---|---|
| Associated knowledge bases | Associate only the procurement and supplier knowledge bases that use the same vector model | Verify the vector model identifier first, exclude knowledge bases with a different model, and do not run cross-model retrieval |
| Search mode | Test the same question separately under semantic retrieval and full-text retrieval | Purchase batch numbers and supplier names contain numbers and proper nouns; compare the content hit under each mode |
| Reference limit | Hypothetical starting point of 2000 tokens | This value is the starting point for this paper test; compare whether reference content stays complete across long and short batch materials, then adjust |
| Minimum relevance | Hypothetical starting point of 0.5 | This value takes effect only under semantic retrieval or result reranking; label relevant and irrelevant samples first, then compare the filtering result |
| Question optimization | Enable for follow-up questions that contain references | Compare the original question with the optimized question, and check whether the supplier entity and batch were altered |
| Result reranking | Enable according to settings when a rerank model is available | Rerank scores are used for filtering; compare candidate ordering before and after reranking |
Three common errors
- Treating minimum relevance as a permission or entity filter. Relevance is a similarity threshold and does not exclude records outside the access scope. The access scope must be confirmed separately before retrieval.
- Describing RRF as a standalone switch that can be turned on. RRF is the fusion process of hybrid retrieval, so configuration items should describe the search mode and rerank settings.
- Treating a pending review as already authorized. When a handover request is in pending review status, record only that status and do not infer that operational permission is already in place.
How to verify the setup
- Check one: Enter the two source texts and the draft sentence from the hypothetical sample, and compare the entity, object, period and supply scope fields. The draft sentence merges the scopes of two batches, so it is judged unsupported and the evidence gap must be kept.
- Check two: Enter the same supplier name and observe the returned content under semantic retrieval and full-text retrieval respectively. Compare how the two modes hit the batch number, record the actual observation, and do not guarantee a first-position hit.
- Check three: Enter an empty array [] and check the downstream design, observing whether the output path runs through. Handle the empty-result path as the documentation describes, and do not claim that a fabricated rule retrieval necessarily returns [].
All three checks must run within a target retrieval scope that the operator is authorized to access, or through an explicit manual input. When that is missing, record the gap.
This page addresses only creator commission settlement and deduction / procurement and supplier materials / knowledge base retrieval and recall. Whether materials, operations or requests are in a given authorization state during an operations handover is a separate matter; retrieval and forms are not authorization to execute.