What the documents look like
Site selection and store opening work happens before a store begins trading. The core of the work is lease negotiation and engineering delivery, and the main data comes from trade-area footfall, map POI data, POS history by store type, and landlord materials. The document set for this page is the site evaluation form, the lease letter of intent, the renovation budget, and the opening schedule. Materials are updated on an irregular basis, once per store.
In the store service and internal training task, these materials are used to answer expansion staff questions. Each citation in an answer must trace back to a specific file and version. The answering step receives the citation array produced by the knowledge base search node, so the training question is whether that array can be traced to source text rather than whether an answer reads smoothly.
Two features of this category shape the tracing work. First, the materials carry different business states: an evaluation form records a calculation, a letter of intent records an intention and an expiry, and neither is a signed lease. Second, the same store can have a current version and an earlier version of the same form, so tracing must identify which version a citation came from.
Constraints at the citation tracing step
The knowledge base search node can associate one or more knowledge bases that use the same vector model. Its output is an array of citations, and the length may be zero, which means the output path still runs even when no content is retrieved. The minimum relevance value is a filter threshold that takes effect only in semantic search or when result re-ranking is used. It is not a permission filter and does not isolate entities; retrieval itself does not constitute authorization. Hybrid search merges multiple result paths through RRF, which is a step in the retrieval flow and not a separate switch. The citation limit is measured in tokens.
Version currency must be checked against the current version and the historical version separately. Whether a citation is adopted still depends on review of the effective version.
Hypothetical drill sample. A chain headquarters expansion department plans to evaluate a shop in City A in March 2026. Material one, the site evaluation form, reads: "This form evaluates the shop at No. 12 B Road, City A. Evaluation date: 2 March 2026. Rent-to-sales ratio calculation: 18%. Data source: fourth-quarter 2025 turnover provided by the landlord." Material two, the lease letter of intent, reads: "Intent deposit RMB 50,000. Valid for fifteen days from the date of signature. This letter of intent does not constitute a formal lease contract." The draft sentence to be judged: "The lease contract for this shop has taken effect, the 18% rent-to-sales ratio is confirmed, and renovation access can be scheduled."
Configuration and implementation checks
| Configuration or check item | Assumed starting point for this drill | Reason and comparison object |
|---|---|---|
| Associated knowledge bases | Associate only the same-vector-model base containing the site evaluation form and the lease letter of intent | Compare the vector model identifier against the base proposed for association; exclude those with a different identifier |
| Search mode | Hybrid search | Compare against semantic search alone; numbering and proper-noun lookups need full-text recall |
| Citation limit | Assumed starting point 3000 tokens | Compare against the total length of current candidate chunks, then adjust |
| Minimum relevance | Assumed starting point 0.3 | Compare against the re-rank score distribution; takes effect only in semantic search or re-ranking |
| Question optimization | Not enabled for this drill | Compare against a multi-turn follow-up scenario; a single clear question needs no extra model call |
| Citation handoff | Check whether the answering node receives the citation array | Compare item by item against the source text of the retrieval output |
Three common errors
- Treating a retrieval hit as business authorization. Error: because the lease letter of intent was retrieved, the lease contract is treated as effective. Check: input the two source materials above and the draft sentence, compare the letter's statement that it does not constitute a formal lease contract against the draft's claim that the contract has taken effect, and observe whether the same subject, same period, and same field carry mutually exclusive values.
- Treating minimum relevance as a permission or entity filter. Error: raising the relevance value is assumed to exclude unrelated shops or unauthorized records. Check: input a retrieval scope containing No. 12 B Road, City A, and a fragment about another shop, compare whether output items are removed only because the score changed, and observe whether removed items still fall within the same authorized scope.
- Treating an empty citation array as a flow error. Error: an output length of zero is read as node failure. Check: use a paper input of an empty array to check the downstream answering node design, compare whether the path still runs as documented, and observe whether any undefined termination behavior appears.
How to verify the setup
- Input: the site evaluation form text above and the draft sentence "the 18% rent-to-sales ratio is confirmed." Comparison: the form states the data source is fourth-quarter 2025 turnover provided by the landlord; check whether the draft presents that calculated value as a confirmed fact. Satisfied when citations point item by item to the form text and the calculated value is not written as a verified conclusion.
- Input: the lease letter of intent text above and the draft sentence "the lease contract has taken effect, and renovation access can be scheduled." Comparison: the letter states a fifteen-day validity from signature and that it does not constitute a formal lease contract; check whether the draft's contract-effectiveness claim and access arrangement are supported by the source text. Satisfied when the answer preserves the letter's nature and validity period, marks the access arrangement as pending verification, and does not infer authorization from the letter.
- Input: the same vector model base identifier, a different vector model base identifier, and a paper empty array. Comparison: check whether the two base identifiers match and whether the empty array still runs downstream. Satisfied when a mismatched identifier is excluded and no cross-model retrieval is performed, the empty array runs as documented with the actual observation recorded, and fields without support remain missing.