What the documents look like
An MCN organization manages long-term account compliance for multiple creators, so its materials cover many people across continuing relationships rather than a single brand campaign. The documents relevant to contract and transaction material comparison include creator signing contracts, training records, violation handling forms, and account scheduling records. A contract ledger for one creator may carry fields such as signing entity, counterparty, settlement cycle, and authorization scope. Different creators use similar structures with different values, which means retrieval has to organize these materials by knowledge base so that the right clauses and records can be recalled during comparison.
The task on this page is contract and transaction material comparison. Retrieval supplies candidate clauses and records; it does not decide whether a contract took effect, whether a violation was approved, or whether a payment was completed. Those determinations depend on evidence that the retrieved text may not contain.
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 built on different vector models cannot be associated together. Verify the vector model identifier of each candidate base, exclude those that do not match, and record what was actually observed. Do not run cross-model retrieval to compare missed recalls.
Search results are output as an array of citations, and the length may be zero. When nothing is found, the output path still completes. Semantic recall and relevance scores do not perform permission or entity isolation; a similarity setting does not exclude unrelated businesses or unauthorized records. The same-vector-model requirement for associated knowledge bases does not extend to any external system.
The minimum relevance value takes effect only under semantic retrieval or when result reranking is used. It is a filter threshold, not a final ranking rule. RRF is a fusion process for mixed results, not a standalone switch. Image retrieval requires image input and the corresponding model capability. Reranking requires a rerank model and must be enabled in the settings.
Hypothetical drill sample: a contract ledger entry for one creator records: "Party A, XX Culture Media Co., Ltd., and Party B, creator XX, signed a livestream commerce cooperation contract on March 1, 2025, with a cooperation term from March 1, 2025 to August 31, 2025, and a settlement cycle of settling the previous month's commission on the 15th of each month." A scheduling record states: "Creator XX, March 2025 schedule is one livestream each on March 10 and March 20." A draft sentence under review reads: "The commission for creator XX's March 10, 2025 livestream was settled on April 15, 2025." The draft sentence asserts a settlement fact. The contract text states only the settlement cycle and does not record a specific settlement completion date, so whether the commission was settled is unsupported and remains to be verified.
Configuration and implementation checks
| Configuration item | Setting for this page | How to check |
|---|---|---|
| Associated knowledge bases | Bases holding creator signing contracts, training records, violation handling forms, and account scheduling records; confirm each base uses the same vector model | Verify the vector model identifier of each base and exclude those that do not match |
| Search mode | Compare semantic, full-text, and hybrid retrieval against test questions; do not assume one mode suits all materials | Test separately with contract clauses and violation identifiers |
| Citation limit | Unit is tokens; test with materials of different lengths to see whether content is complete | For this hypothetical trial, start at 2000 tokens because contract clauses are often long, and compare against shorter scheduling records |
| Minimum relevance | Takes effect only under semantic retrieval or when result reranking is used | Label relevant and irrelevant samples first, then adjust the threshold |
| Question optimization | Used for coreference resolution and question expansion | Compare the original question with the optimized question and check whether the subject was altered |
| Result reranking | Requires a rerank model and must be enabled in the settings | Observe the rerank score and the fused result |
Three common errors
- Treating retrieval recall as an authorization determination. When the input asks whether a creator's contract is effective, retrieving the contract text only shows that the clause exists. Signing, reaching cooperation, and contract effectiveness are three distinct facts, and recalled content does not establish that the contract took effect.
- Treating a pending-review status as missing operating permission. A violation handling form being under review only means that review is not complete; it does not establish that operating permission is absent.
- Treating an unstated field as a negation or a conflict. The contract text does not record a commission settlement date, and the draft sentence asserts settlement. This is unsupported rather than contradictory or negated, and the evidence gap must be preserved.
How to verify the setup
- Input the contract text and the draft sentence from the hypothetical sample. Compare the draft sentence "the commission was settled on April 15, 2025" with the contract text "settling the previous month's commission on the 15th of each month." The contract text does not record a specific settlement completion date, so the fact asserted in the draft sentence is unsupported and is marked as pending verification. No live test is claimed.
- Input the pending-review status of a violation handling form and a request to "approve this violation handling form." Compare the requested action with the form's status. Pending review does not constitute approval, the request has no authorization basis, and the result is recorded as pending verification.
- Input an empty citation array [] together with the downstream comparison flow. Compare how the empty result is carried with the downstream design. A citation length of zero still completes the output path, and the downstream flow must handle the empty result accordingly. Do not claim that a fictional rule query necessarily returns [].
This page addresses only MCN organization creator management, contract and transaction material comparison, and knowledge base retrieval and recall. At operations handover, the authorization status of materials, operations, and requests must be checked separately; retrieval and forms are not authorization to execute.