What the documents look like
Fresh-food supplier claims pursue incoming-quality liability. They sit on a different business line from in-store natural shrinkage handling. Quality inspection systems record batch quality exceptions. WMS receiving records incoming quantity and condition. Supplier contracts set deduction and replenishment terms. Finance reconciliation produces claim statements. The daily documents are quality exception forms, photo evidence, deduction notices, and claim reconciliation statements. Each incoming batch generates new exception records; monthly reconciliation produces summaries. Copy drafting in this setting cites specific facts from those materials, and the wording stays within what the materials record.
For this page the task is product and marketing copy drafting, and the workflow-routing step must collect material facts, judge whether proposed wording is supported, and output a handover-ready draft.
Constraints at the workflow routing step
The Form Input node is a user-interaction node. When it triggers, the conversation enters an interaction state, the workflow state is recorded, and after the user completes the interaction the workflow continues. It collects required information the user submits and passes that information to later nodes. The User Selection node is also a user-interaction node; when the user makes a selection, the node evaluates the choice and executes the corresponding "yes" branch. The interaction state is recorded by the interaction node. No separate global state-recording switch is documented. Collected information must be explicitly passed to later retrieval, judgment, or interface nodes, and output must be compared item by item against input. Order writing, document backfill, and external status synchronization require a separate business interface or a later process.
Hypothetical paper exercise sample. Material source text: "Batch SP-0310 arrived on 10 March 2025. Quality exception form QZ-0310-07 records a yellow-leaf ratio of approximately 12% for leafy vegetables. The WMS receiving record shows 200 boxes signed for in this batch. Supplier contract clause 4.2 provides that when the yellow-leaf ratio for leafy vegetables exceeds 10%, the value of the excess portion is deducted." Proposed draft sentence to be judged: "Because the yellow-leaf ratio in this batch exceeded the standard, the deduction under the contract has been completed." The sentence involves a subject (the supplier), an object (batch SP-0310), a state (12% yellow-leaf ratio), and a scope of validity (the deduction condition in clause 4.2). The materials do not record whether the deduction was executed. The phrase "has been completed" lacks material support.
Configuration and implementation checks
| Configuration item | Hypothetical trial starting point | Reason and comparison method |
|---|---|---|
| Form Input required fields | Batch number, exception form number, contract clause number | Compare each field value against the material source text to confirm traceability |
| User Selection branch condition | Whether the proposed sentence contains a state not recorded in the materials | Compare the proposed sentence with the source text on the same subject, same period, same field |
| Information passed downstream | Retrieval node receives batch number and exception form number | Check that passed fields match the downstream node input |
| Interaction state check | Record the state after form submission | Compare against the documented behavior of the interaction node |
| External action split | Deduction execution marked as pending integration | Confirm the workflow does not itself execute the deduction or backfill |
Three common errors
- Treating "the deduction has been completed" in the proposed sentence as a fact already recorded in the materials. The source text records only the contractual deduction condition, not the deduction execution status. The error is treating an agreed condition as an execution result.
- In the User Selection node, merging "12% yellow-leaf ratio" and the contract clause number into one judgment field. These belong to different fields; a contradiction exists only when the same field has clearly mutually exclusive values.
- Extending the retrieval node's vector-model association scope to an external system. Libraries on different vector models cannot be associated together; identify the model first and exclude those that do not match.
How to verify the setup
- Input the hypothetical sample source text and the proposed sentence, then compare "the deduction has been completed" against the recorded scope of the source text. When the materials do not record deduction execution status, that part of the proposed sentence should be marked as unsupported. If the proposed sentence is output directly as verified content, the condition is not met.
- Input the proposed phrase "the yellow-leaf ratio in this batch exceeded the standard" and compare "exceeded the standard" against the 12% recorded on quality exception form QZ-0310-07 and the 10% threshold in contract clause 4.2. When 12% exceeds the 10% threshold, the wording is consistent with the materials. If the materials do not provide a threshold or ratio, mark it as pending verification.
- Input an empty-result handover scenario, using the paper input [] to check the downstream design. When the downstream node receives an empty array, it should record the gap and wait for human input, without auto-filling or inferring. If the downstream node generates content on its own, the condition is not met.