What the documents look like
Price and display auditing in a chain store happens during ordinary trading periods, so the material record builds around sustained execution rather than a single launch event. Supervision systems hold store visit results. POS price lists supply the comparison baseline for shelf labels. Store cameras and visit photographs carry the evidence. Head office promotion calendars set the price and display requirements in force for a given period. Regional supervisors and store managers exchange visit photographs, price label lists, display standards and rectification notices during order fulfilment and after-sales question handling. These materials update weekly or monthly, and a single request should only cover the period and store scope it explicitly names.
Constraints at the workflow routing step
The form input node and the user selection node both belong to the user interaction node family. When either is triggered, the conversation enters an interaction state and the workflow state is recorded; execution continues after the user completes the interaction. Form input collects required information and passes it to later nodes once submitted. User selection evaluates the user's choice and executes the corresponding branch. Neither a retrieval hit nor a completed form counts as authorization: order writes, document backfill and external status synchronisation require a separate business interface or a later process. Visit photographs, price label lists and promotion calendars needed for label comparison must sit inside an accessible retrieval scope or an explicit manual input; when they are absent, the gap is recorded.
Hypothetical drill sample: a chain brand operations department receives a store after-sales request. The source text reads: "Store A submitted its price label list in week 3 of the promotion period, and the list states a shelf price of 19.9 yuan for a certain product. The head office promotion calendar for the same period states that this product runs at 16.9 yuan during that period. The visit photograph shows the shelf label still at 19.9 yuan." The draft sentence to be assessed is: "The store has completed rectification at the promotion price and issued a refund." The request sits in a pending review state, with no signature or approval record.
Configuration and implementation checks
| Configuration item | Type | Relation to this page's sample |
|---|---|---|
| Form input node | User interaction | Collects required information such as store, promotion period, product and request type, then passes it to later nodes after submission |
| User selection node | User interaction | Presents a choice between "check the price label difference" and "escalate to manual review", then executes the corresponding branch |
| Interaction state record | Node behaviour | Triggering an interaction node records workflow state and waits for the interaction to complete before continuing |
| Output hand-off | Implementation check | Passes form and selection results explicitly to later retrieval or decision nodes, comparing each input against its output |
| Retrieval scope check | Manual check | Confirms visit photographs, price label lists and promotion calendars sit inside an accessible target scope |
| External action split | Separate implementation required | Order writes, rectification backfill, refunds and external synchronisation are carried by a business interface or a later process |
Hypothetical trial starting point for this page: treat the price label list value and the promotion calendar value as two fields to compare. This starting point is chosen because the sample supplies both numbers. The comparison method is a field-by-field check for the same store, the same promotion period and the same product. No default value or threshold is set.
Three common errors
- Treating a retrieval hit or a form submission as completed authorization. In the sample the request sits in a pending review state. Finding the promotion calendar file only shows the material exists; it does not show that rectification or a refund has been approved.
- Treating the draft sentence "has completed rectification at the promotion price and issued a refund" as an established fact. The source text only shows the shelf label still at 19.9 yuan, with no rectification record and no refund evidence. That sentence is unsupported.
- Using a similarity score to exclude unrelated stores or unauthorized records. Relevance does not perform entity isolation or permission filtering. Libraries built on different vector models cannot be associated together; identifiers must be checked and non-matching records excluded.
How to verify the setup
- Input the sample source text and the draft sentence. Compare whether the draft sentence contains rectification completion and refund facts not carried in the source text. The observable result is that the sentence should be marked unsupported.
- Input the sample source text. Compare whether the price label list value of 19.9 yuan and the promotion calendar value of 16.9 yuan belong to the same store, the same promotion period and the same product. The observable result is that the two field values are mutually exclusive, forming a difference pending verification.
- Input an explicit paper empty result []. Check whether downstream nodes are designed to accept an empty result. The observable result is that downstream produces no order write and no external synchronisation action. Whether retrieval actually returns an empty result still requires an observed record.