What the documents look like
Member private-domain operations revolve around customer identity, purchase records and outreach actions. The working materials come from a CRM system, WeCom, POS purchase records and mini-program behaviour data. Day-to-day documents include member tag tables, outreach plans, coupon rules and privacy authorization records.
In cross-border and multilingual retrieval, the same set of materials may exist in several language versions, and retrieval needs to locate corresponding records across languages. This page covers only the model connection and configuration step. It does not construct business functions that have no documented basis.
Two industry facts shape this step. First, member data carries authorization scope, so a retrieval result and an authorization record are different objects. Second, multilingual material means the same member may appear under several language versions, so identifier and scope checks matter more than surface wording. Update frequency does not change the configuration described here and is not repeated.
Constraints at the model connections step
Model connection depends on AI Proxy. From V4.17.0, both the App and any Admin service that reuses App/Service configuration must set AIPROXY_API_ENDPOINT and a non-empty AIPROXY_API_TOKEN. Missing either one causes startup validation to fail. AIPROXY_API_ENDPOINT holds the AI Proxy service root address and does not append /v1. Model channels and application configuration are checked separately. The system needs at least one language model and one index model to work normally. A retrieval relevance score does not carry permission or entity isolation duties, and retrieval itself does not constitute authorization.
Hypothetical paper exercise sample. A brand member operations team prepares a cross-border outreach item for review. The material text to be checked reads: "Member ID M-2041. Authorization scope: SMS outreach in mainland China. Authorization valid until 31 December 2026. Outreach plan: 2026 November Double Eleven coupon distribution." The draft sentence to be judged reads: "Send cross-border SMS outreach to M-2041 using coupon rule A." The draft sentence states the authorization as cross-border SMS, which differs from the material's "SMS outreach in mainland China". The draft sentence is judged unsupported.
Configuration and implementation checks
| Configuration item | Hypothetical starting value for this exercise | Explanation and comparison method |
|---|---|---|
AIPROXY_API_ENDPOINT | http://aiproxy:3000 | Hypothetical starting value, chosen because the documents show this address form. Compare against the documented requirement that the root address carries no /v1. |
AIPROXY_API_TOKEN | Hypothetical non-empty trial value | Hypothetical starting value, chosen because the documents require a non-empty value. Compare with the server-side configuration for consistency. |
| Language model | Selected for the input the application needs | Check whether it satisfies the text conversation needs of multilingual retrieval. |
| Index model | Selected for the knowledge base need | Check whether it satisfies the related-text retrieval need. |
| Model channel test | Test executed against a configured channel | Observe each model's test result and request duration. |
| Retrieval scope check | Manual check of the target retrieval scope | Confirm that the material needed for the check sits inside a scope the operator can access; record a gap when it does not. |
Three common errors
- Treating a retrieval result as an authorization basis. Input a retrieval request, compare the returned result against the privacy authorization record text, and observe whether a relevance score is misread as an authorization credential. Retrieval does not perform permission isolation; authorization needs a separately implemented system.
- Treating cross-border SMS in the draft sentence as equal to the material's authorization scope. Input the draft sentence and the hypothetical sample material, compare the authorization scope field, and observe whether "SMS outreach in mainland China" is misjudged as supporting cross-border SMS.
- Treating a successful model channel test as completed business authorization. Input the channel test result and the authorization record, compare the test scope against the authorization scope, and observe whether technical connectivity is misjudged as business authorization.
How to verify the setup
- Input the hypothetical sample material and the draft sentence. Compare the authorization scope field "SMS outreach in mainland China" against the draft sentence's "cross-border SMS outreach". Observe whether the two agree. The expected result is that they do not agree, and the draft sentence is unsupported.
- Input the
AIPROXY_API_ENDPOINTconfiguration value and the documented requirement. Compare whether/v1is appended, and observe whether the value is in root-address form. The expected result is that it is not appended. - Input the retrieval request and the target retrieval scope. Compare whether the material needed for the check falls inside that scope, and observe whether a missing gap is recorded. The expected result is that a gap is recorded explicitly when present, without inferring a negative or a conflict.