What the documents look like
Franchisee onboarding is a transfer of operating capability. It differs from franchise registration disclosure, which is a legal filing matter. The working materials for this page are training sign-in sheets, opening inspection checklists, SOP manuals and assessment scores. These come from a training system, a supervisor app, store photographs and the headquarters SOP library. The brief states that these materials update per store and per month, and that formats and fields are decided by each source system. That update frequency does not change what this page covers. The retrieval scope remains the selected knowledge base and the document version held in it.
For citation tracing, the practical question is whether a retrieved item can be tied to a specific store, a specific onboarding stage and a specific version, and what authorization state a handover request is in. A search hit is a retrieval event. It is not an approval, not a completed review and not a permission grant.
Constraints at the citation tracing step
The knowledge base search node can be linked to one or more knowledge bases that share the same vector model. It outputs citations as an array, and the length may be zero, which means the output path still runs even when nothing is found. Retrieval does not perform authorization checks, and a similarity score is not a category, entity or permission filter. The minimum relevance setting is a filter threshold that applies only under semantic retrieval or result reranking. It does not exclude unrelated businesses or unauthorized records. Hybrid retrieval merges multiple result paths through RRF; RRF is a fusion process and is not documented as a standalone switch. Image retrieval requires corresponding image input and model capability, and reranking requires a model that is enabled in settings. These optional paths do not all run on every request. Knowledge bases with different vector models cannot be linked together; the identifiers must be checked first and non-matching bases excluded.
Hypothetical paper exercise sample: a franchisee training file holds the following two sentences of source text from an "Opening coaching handover record": "On 10 March 2025, regional supervisor Li handed franchisee owner Wang one cashier training sign-in sheet, with 12 signatories, sheet number PX-20250310-01. The sheet is an opening coaching stage material and has not yet been reviewed by the head of the training department." A draft sentence is put forward for assessment: "This sign-in sheet has been reviewed and approved by the head of the training department and can serve as evidence that opening coaching is complete." The source text records only the handover and the not-yet-reviewed state. The draft sentence's approval and completion evidence have no support in the source text.
Configuration and implementation checks
The table below lists documented settings or implementation checks tied to this sample. The values are starting points for this exercise and name what they are compared against. They are not official defaults.
| Configuration item | Starting point for this exercise and reason | Comparison and recording method |
|---|---|---|
| Linked knowledge base | Select only the one training file base whose vector model identifier matches the sample | Check the base identifier against the vector model identifier and exclude any that do not match |
| Search mode | Choose hybrid retrieval to cover both the sign-in sheet number and natural language description | Compare with pure semantic retrieval to see whether the citation content includes the number field |
| Minimum relevance | Set to 0.5 for this exercise to observe whether low-relevance fragments are filtered | Compare with 0.3 and 0.7, and record changes in citation content |
| Citation limit | Set to 500 tokens for this exercise to bound single-request citation length | Compare with 200 and 1000 tokens, and record citation count and truncation |
| Question optimization | Enable, to complete the reference of "this sign-in sheet" | Compare with the disabled state to see whether the search terms include the sheet number |
| Citation content output | The downstream node checks each array entry against the source text | Record the array length and the correspondence of each entry to the source text |
Three common errors
- Treating a retrieval hit as a completed authorization. The observable error is reading a retrieved sign-in sheet as a training department approval. Check: input the sample source text and the draft sentence, compare whether the source text states a reviewing body and a review state, observe that the draft sentence's "reviewed and approved" has no corresponding field in the source text, and record it as unsupported.
- Treating a similarity score as an entity or permission filter. The observable error is expecting that raising the minimum relevance will exclude other stores' records. Check: input the same question and adjust the minimum relevance, compare whether citations from other store materials still appear, observe whether the score setting changes the entity scope, and record the actual observation.
- Inferring runtime behaviour from linking knowledge bases with different vector models. The observable error is linking bases with different vector models and expecting a specific recall outcome. Check: input each base identifier and vector model identifier, compare whether the identifiers match, observe that non-matching bases are excluded, and record that they cannot be linked. Do not run a cross-model retrieval comparison.
How to verify the setup
- Citation handover check. Input the two source sentences and the draft sentence. Compare whether the draft sentence's "reviewed and approved" and "completion evidence" share the same subject, the same period and the same field as the source text's "not yet reviewed." When the source text does not state a review outcome, record it as unsupported rather than as a conflict.
- Empty-result handover check. Input a paper citation array of []. Compare whether the downstream node continues to execute with a length of zero. Observe that the output path runs and that no error assertion is produced, and record this as a downstream design item to be confirmed.
- Material version check. Input the sample sign-in sheet number PX-20250310-01 and the marked date 10 March 2025. Compare the record for that number in the current version and the historical version. Observe whether the citation content points to the same version, record any version difference, and do not infer a review or effective state.
This page covers only franchisee training and opening coaching, operations permission and handover management, and citation tracing. Which materials, operations and requests are in what authorization state during an operations handover cannot be decided by retrieval or by a form.