What the documents look like
Fresh-food weighing and sorting sits inside warehouse fulfilment, where weight and specification are the working facts. The main materials for copy drafting are the sorting task sheet, the weighing label, the short-weight compensation form and the quality inspection record. These materials come from a WMS, electronic scales, an order system and inspection photographs, with updates per order and per day. Draft sentences need to cite fields such as specification, weight range and inspection conclusion. Whether a material is complete and in a confirmed state decides whether a proposed sentence can be supported.
Constraints at the workflow routing step
The Form Input node belongs to the user-interaction nodes. When it triggers, the conversation enters an interaction state, the workflow state is recorded, and execution continues after the user completes the interaction. The User Selection node also enters an interaction state when triggered and records the workflow state. When the user makes a choice, the node evaluates that choice and runs the corresponding branch. Both nodes collect information the user fills in or selects. Order writes, document backfill and external status synchronisation need a separate business interface or a later process.
Hypothetical paper exercise sample. Material text one: "Sorting task sheet A-01 states: 10 March 2026, order number A-01, item is loose spinach, specification range 300 g to 350 g, the sorter has weighed and labelled it." Material text two: "Quality inspection record Q-07 states: same date, same order number, inspection conclusion is acceptable appearance, no re-weigh result recorded." Draft sentence under assessment: "Every portion of spinach in this order is 300 g to 350 g, and quality inspection has confirmed the weight is correct." The draft sentence touches two fields, weight re-weighing and inspection conclusion. The inspection record does not record a re-weigh result, so the weight-confirmation part of the draft sentence is not supported.
Configuration and implementation checks
| Configuration item | Type | Description |
|---|---|---|
| Form Input node | Documented setting | Enters the interaction state when triggered, collects required information, and passes it to later nodes after submission. |
| User Selection node | Documented setting | Runs the "yes" branch after the user makes a choice; check each branch connection one by one. |
| Interaction state check | Implementation check | State recording is behaviour of the interaction nodes; do not add or claim a global state-recording switch. |
| Output handover check | Implementation check | Pass collected information explicitly to later retrieval, judgement or interface nodes, and compare each output against its input. |
| External action split | Implementation check | Order writes, document backfill and external status synchronisation require a separate business interface or later process. |
Three common errors
- Treating the "yes" branch of the User Selection node as an automatic judgement. The node runs a branch based on user feedback. Whether a draft sentence is supported by materials still requires a manual comparison of material fields. Branch execution does not produce a conclusion about copy correctness.
- Treating information collected by the Form Input node as already verified fact. The node collects information the user fills in and passes it to later nodes. Whether that information matches the sorting task sheet and inspection record requires a separate check.
- Treating interaction state recording as business status synchronisation. Interaction state recording is node behaviour. Order writes and external status synchronisation need a separate business interface and cannot be completed by an interaction node.
How to verify the setup
- Enter the hypothetical sample material text and the draft sentence. Compare the draft sentence "quality inspection has confirmed the weight is correct" with quality inspection record Q-07, which records no re-weigh result. Observe whether the result is recorded as not supported. The expected result is not supported, with the evidence gap retained.
- Enter the hypothetical sample material text and the draft sentence. Compare the draft sentence "every portion is 300 g to 350 g" with sorting task sheet A-01, which gives a specification range of 300 g to 350 g. Observe whether the range wording is consistent. The expected result is consistent range wording, while the weight-confirmation part remains to be verified.
- Enter the hypothetical sample material text and the handover request "please push this order's copy to the order system and backfill the inspection record". Compare the order-write and document-backfill actions in the request with the capabilities of the configured nodes. Observe whether an interface or later process exists that can carry out those actions. The expected result is that the actions need a separate business interface, and the current nodes do not perform them.