What the documents look like
Wholesale market stall trading runs on on-site bargaining and consignment shipping. The daily document set covers purchase receipts, handwritten sales slips, stall lease contracts and payment receipts. Related records include market price quotations, stall inventory, WeChat payment records and logistics consignment notes. Compared with regional distributor replenishment, stall trading is more fragmented and depends on face-to-face negotiation and shipping arrangements. Documents update daily and per order.
For the inventory procurement and supplier records task, workflow inputs are often unstructured text or images. Missing fields and handwritten ambiguity are common. Workflow routing has to carry collected information into later retrieval, judgment or interface nodes without treating collection as business confirmation.
Constraints at the workflow routing step
The form input node enters an interaction state when triggered, collects required information, and passes the submitted information to later nodes after submission. The user selection node evaluates the user's choice and executes the "yes" branch. Recording interaction state is behavior of the interaction nodes; no separate global state-recording switch is documented.
Three constraints apply. Interaction nodes collect and branch; they do not perform business verification. Output handoff must compare input and output item by item. Order writes, document backfill and external status synchronization require a separate business interface or later process. The same-vector-model requirement for retrieval libraries applies only to knowledge base association. It does not extend to business registration sites or other external systems. Semantic recall and relevance scores do not handle permission or entity isolation. Libraries across different vector models cannot be associated together; check identifiers first and exclude those that do not match.
Hypothetical paper exercise sample: a stall owner submits a photo of a handwritten sales slip. The source text has three sentences: "Received from Wangji Vegetable Trading today payment of three thousand yuan in full, goods shipped by consignment, waybill number left blank. Stall lease contract number A-07, term runs to December of this year. Supplier record sheet telephone field is blank." A draft sentence is also submitted: "Payment for this order is settled, supplier records are complete, next procurement can be arranged." The source text contains the subject (Wangji Vegetable Trading), the object (three thousand yuan payment, waybill number blank), the state (supplier telephone blank) and the valid scope (lease term to December). The draft claims the payment is settled and the supplier records are complete. The source only records receipt of three thousand yuan and does not state settlement. The supplier telephone field is blank, so completeness is not supported.
Configuration and implementation checks
| Configuration item | Type | Description |
|---|---|---|
| Form input node | Documented | Enters interaction state when triggered, collects required information, passes it to later nodes after submission |
| User selection node | Documented | Executes the "yes" branch after the user makes a choice; verify branch connections one by one |
| Interaction state check | Implementation check | Recording state is behavior of the interaction nodes; no separate global state-recording switch is documented |
| Output handoff check | Implementation check | Pass collected information explicitly to later retrieval, judgment or interface nodes; compare output and input item by item |
| External operation separation | Implementation check | Order writes, document backfill and external status synchronization require a separate business interface or later process |
| Hypothetical exercise starting point | Hypothetical for this page | Draft-sentence consistency check uses the three source sentences as the comparison baseline; this starting point is chosen because the sample contains subject, object, state and scope |
The hypothetical exercise starting point applies only to this paper check against the source sentences. It does not claim any default value or tested result.
Three common errors
- Treating form submission as business authorization. The form input node collects required information and passes it to later nodes; submission does not confirm payment settlement or record completeness. The check compares the draft claim "payment is settled" with the source "Received from Wangji Vegetable Trading today payment of three thousand yuan in full." The source does not state settlement, so the claim is unsupported.
- Treating a user selection branch as automatic judgment. The user selection node executes the "yes" branch after the user makes a choice, and branch connections need verification one by one. If the draft claims "next procurement can be arranged," the source does not state any procurement arrangement, so the claim remains pending verification.
- Treating retrieval or similarity as permission or entity isolation. Semantic recall and relevance scores do not handle permission or entity isolation; retrieval is not authorization. When checking supplier record completeness, compare the source "telephone field is blank" with the draft "supplier records are complete." The source explicitly shows the telephone field blank, so completeness is unsupported.
How to verify the setup
- Input the hypothetical sample source sentences and the draft sentence. Compare "payment is settled" with "Received from Wangji Vegetable Trading today payment of three thousand yuan in full." The source records receipt of payment only and does not state settlement. If the check result shows the claim unsupported, output handoff is correct. If the output equates "payment received" with "settled," correct it.
- Input the same source and draft. Compare "supplier records are complete" with "telephone field is blank." The source explicitly shows the telephone field blank, so completeness is unsupported. If the check result preserves this gap and marks it pending verification, the behavior matches expectations. If the output declares the records complete, correct it.
- Input the same source and draft. Compare "next procurement can be arranged" with the source. The source does not state any procurement arrangement, so the claim is pending verification. If the check result marks it pending and executes no procurement action, the behavior matches expectations. If the output triggers procurement or writes an order, a separate business interface is required and the check must be redone.
Empty-result handoff can be checked with an explicit paper input of [] to verify downstream design; this does not claim that a fictional rule retrieval necessarily returns []. Retrieval checks describe observations and failure branches, without guaranteeing a first hit, full recall or an empty result for unrelated queries. Optional paths shown in the overall document flow diagram do not mean every request executes all of them: image retrieval requires a corresponding image input and model capability, and reranking requires a model enabled by settings. Missing evidence stays missing. A pending review does not show lack of operating permission, and a quotation validity period does not indicate a supply period.