Chain-store site selection: model connections for product questions

Review model connections for product questions in Chain-store site selection. Check sources, input boundaries, error handling and repeatable test evidence.

What the documents look like

Site selection and store opening work happens before a store begins trading, and the paperwork centres on leasing and engineering handover rather than on trading operations. The four document families are the site assessment form, the letter of intent to lease, the renovation budget, and the opening schedule. Each is produced per store and updated irregularly, so a question-answering flow over this material cannot rely on a steady refresh rhythm.

Two properties of these documents shape model connection work. First, the same commercial situation is spread across fields that carry different legal weight: a quoted price validity window and a deposit clause sit in different fields of the same letter of intent, and the letter itself does not mean a lease has taken effect. Second, the documents describe stages, not outcomes. A signed letter of intent, a concluded lease contract, and a completed handover are three separate facts. A model connection that reads these fields correctly still has to keep its answers inside what the material states.

Constraints at the model connections step

This page covers only model connection and configuration for product-material and selection question answering in the site-selection and store-opening category.

AI Proxy is a required dependency from V4.17.0. The App service and any Admin service that reuses App/Service configuration must both set AIPROXY_API_ENDPOINT and a non-empty AIPROXY_API_TOKEN; missing either one causes startup validation to fail. Legacy OpenAI environment variables and per-model custom request addresses do not substitute for these two settings. AIPROXY_API_ENDPOINT holds the service root address and does not carry a /v1 suffix.

Model channels, model ID mapping, and enablement are configured on the administrator model provider page. Model capability is checked against the input the application actually needs. Retrieval and relevance scoring carry no permission or entity isolation: a retrieval hit is not an authorization, and a similarity setting does not exclude unrelated businesses or unauthorized records.

Assume a paper exercise sample. The material text reads: "A letter of intent states that the tenant is chain headquarters A, the subject is a third-floor unit in mall B, the signing date is 10 March 2026, the quoted price is valid until 30 April 2026, and the deposit clause remains subject to confirmation by both parties." The sentence under review reads: "Chain headquarters A has completed lease signing for this unit and can arrange renovation access." The point under review is that signing a letter of intent and a lease taking effect are two facts; the material does not state that a contract has taken effect, so the sentence under review goes beyond the source and is unsupported.

Configuration and implementation checks

The table lists only settings that the official material describes, or implementation checks tied to this page's main task. The values in the middle column are starting points for this paper exercise, not official defaults.

Configuration itemStarting point for this exerciseHow to check
AIPROXY_API_ENDPOINTService root address, no /v1 suffixCompare character by character against the actual address in the deployment template
AIPROXY_API_TOKENNon-empty administrator tokenCompare against the server-side configuration and confirm it is non-empty
Model ID mappingRequested model ID matches the channel model nameCompare against the mapping record in the channel configuration
Model enablementOnly models needed for question answering are enabledReview the enabled list on the system model page
Model capabilityChecked against the input the question-answering flow needsCompare against the capability fields in the model configuration
Model probingEnabled as needed, interval set to an integer from 5 to 60Review the configured value on the model probe page

Three common errors

  1. Treating a signed letter of intent as a lease that has taken effect. Input: the sample material text above together with the sentence under review. Comparison: whether the source states that a lease contract has taken effect. Result: when the source does not state this, the sentence is unsupported.
  2. Using an application API key in place of the AI Proxy administrator token. Input: the two credentials. Comparison: the source of the value assigned to AIPROXY_API_TOKEN. Result: when the value comes from the application side, the configuration does not match.
  3. Treating a retrieval hit as a basis for permission. Input: one set of retrieval results. Comparison: whether that result carries an authorization record. Result: with no authorization record, no business action follows from the hit.

How to verify the setup

  1. Input the sample material text and the sentence under review. Compare whether the source states that a lease contract has taken effect. The sentence under review is satisfied only when the source explicitly states both the effective condition and the effective status.
  2. Input AIPROXY_API_ENDPOINT and AIPROXY_API_TOKEN. Compare whether the address is a root address and whether the token is non-empty and consistent with the server side. Startup validation passes only when both hold.
  3. Input one question-answering request. Compare whether the answer cites only fields stated in the material. When a signing or access conclusion appears that the material does not state, record it as unsupported and preserve the evidence gap.

A retrieval check observes results rather than guaranteeing them. With a paper input of an empty result set, verify the downstream design that handles an empty result; this page does not claim that any particular query returns an empty set. Where libraries use different vector models, check the identifiers first and exclude the ones that do not match; this page does not describe what a combined lookup would return.

An approval request is not an approval, an offered option is not execution, and an unsigned termination is not a completed termination. Where a field is not provided in the documents, it remains unknown.