What the documents look like
Near-expiry markdown handling follows the shelf-life of stock rather than the weighing of individual orders. The working papers are near-expiry lists, markdown approvals, damage reports and promotional price tags. Store inspections and POS stock-age data update by day or by shift, and the same batch may carry different names across store records written in different languages. Cross-border material and multilingual retrieval requires these papers to enter a knowledge base and then be found by batch, date and status. A retrieval result presents document content only; it does not change an approval state or a sales state.
Two facts shape this page. First, model access runs through AI Proxy, and both the App service and an Admin service that reuses App/Service configuration must set AIPROXY_API_ENDPOINT and a non-empty AIPROXY_API_TOKEN; a missing item fails startup validation. Second, at least one language model and one index model are required for normal operation, and the index model determines whether text blocks can be retrieved. A model mapping in a channel changes only the model value sent upstream; it does not change the authorization state of a document.
Constraints at the model connections step
Retrieval associations are built per vector model, and libraries built on different vector models cannot be associated together. The documented condition concerns the vector model identity of the library, not the business category of the records and not any external registry.
Hypothetical paper exercise sample. Material one: "Shift of 10 March 2026, batch A-0310 near-expiry markdown approval form has been signed by the store manager; the markdown rate awaits confirmation by financial audit; the promotional price tag for this batch has not been printed." Material two: "10 March 2026, batch A-0310 damage report has been submitted, status pending review." Draft sentence to be judged: "Batch A-0310 has completed markdown approval and markdown sales may proceed." The comparison scope is limited to these two materials.
The draft sentence is not supported by the supplied wording. The signature and the audit confirmation are separate fields, and the material records the markdown rate as awaiting financial audit confirmation. The damage report carries the status pending review, and no review outcome appears. Retrieval of a near-expiry list returns document content; it does not execute an approval, write to a database or synchronize an external system.
Configuration and implementation checks
| Check item | Hypothetical starting value for this exercise | Reason and comparison method |
|---|---|---|
AIPROXY_API_ENDPOINT | http://aiproxy:3000 | The document requires the service root address without /v1; compare character by character against the documented example format |
AIPROXY_API_TOKEN | A non-empty administrator token | The document requires a non-empty value consistent with the server; compare against the AI Proxy server configuration |
AGENT_ENGINE | fastAgent | The document lists fastAgent and piAgent as the two values; compare against the actual deployment choice |
| Index model activation | One index model enabled | The document states that at least one language model and one index model are needed; inspect the enabled list |
| Channel model mapping | Request model mapped to an upstream model | The documented example maps gpt-4o-test to gpt-4o; compare the names before and after mapping |
| Vector library identity | One library for the batch materials | The document states that libraries on different vector models cannot be associated; compare library identifiers for equality |
Three common errors
- Reading the signature in the draft sentence as a completed markdown approval. The material states that the markdown rate awaits financial audit confirmation. The check is whether the same field holds mutually exclusive values; on this material it does not.
- Reading pending review on the damage report as a completed damage write-off. Pending review is a submitted status, and no review result is recorded, so this field remains unsupported.
- Treating a retrieved near-expiry list as a markdown authorization. Retrieval returns document content and performs no approval, database write or external synchronization.
How to verify the setup
- Input the two materials and the draft sentence. Compare "the markdown rate awaits confirmation by financial audit" against "has completed markdown approval." When the materials contain no record of completed audit, the draft sentence is not supported.
- Input the damage report wording "status pending review." Compare whether a passed or rejected review record exists. When only the pending review field is present, the completion state remains to be verified.
- Input the near-expiry list and the promotional price tag materials for the same batch. Compare the vector library identifiers. When the identifiers differ, record that the libraries cannot be associated, retain the gap and do not run a cross-library comparison.
These checks describe expected observations. They do not report a completed test, an approval, a refund or any other executed business action.