What the documents look like
Wholesale market stall trading is fragmented and depends on on-site bargaining and consignment shipping. Compared with regional distributor replenishment, the paperwork is less standardized and more scattered. The documents this page concerns are purchase notes, handwritten sales slips, stall lease contracts and payment receipts. These materials typically cover a single transaction or a single day. The parties, the counterparty, the amount, the goods name and the shipping destination are spread across different sheets.
When a workflow supports product and marketing copy drafting, the orchestration step needs to collect those scattered fields into a form input node so the drafter fills them in item by item, and then pass the submitted values to the following nodes. The brief records the update frequency of this material as daily and per order. The orchestration design therefore needs to allow the same workflow to be triggered repeatedly, each run carrying the values actually entered in that run.
Two document statements are used as the hypothetical exercise sample throughout this page. Material statement one: "On 1 March 2024, stall A issued a handwritten sales slip to buyer B for 200 spring shirts; the amount is not settled." Material statement two: "The stall lease contract states that stall A's lease runs until 31 December 2024." The draft sentence to be judged is: "Stall A has fully settled the spring shirt payment and supplies steadily over the long term." The comparison scope is limited to those two statements.
Constraints at the workflow routing step
The form input node is a user interaction node. When it is triggered, the conversation enters an interaction state and the workflow state is recorded; after the user completes the required information and submits, the node collects the submitted form values and passes them to later nodes. The user selection node is also a user interaction node. When triggered, the conversation likewise enters an interaction state, and after the user makes a choice the node judges that choice and executes the "yes" branch. Both nodes can be added repeatedly and both trigger execution.
For copy drafting, the constraint is that whether a proposed sentence holds depends on whether the subject, counterparty, period and document status entered in the form agree with the source material. Retrieval returns candidate materials by semantics; it does not perform permission checks or entity isolation. The same vector model is a precondition for association within a library, and libraries built on different vector models cannot be associated together. Order writes, document backfill and external status synchronization must connect to a separate business interface; the orchestration itself does not complete those actions.
Configuration and implementation checks
The table below lists only settings already described in the official documentation, or implementation checks, that relate to this page's primary task. The values are hypothetical starting points for this exercise, not official default values.
| Configuration item | Hypothetical starting point | Reason and comparison object |
|---|---|---|
| Form input node required fields | Subject, counterparty, goods, period, document status | Aligns with fields checkable against the source statements; a missing item is recorded as a gap |
| User selection node branch | Yes branch connects to copy pass or return | Verify branch connections one by one and confirm the direction after the choice |
| Output handover | Form values passed to a retrieval or judgment node | Compare output against input item by item and confirm no field is lost |
| Retrieval library vector model identifier | Consistent with the target library | Check the identifier first and exclude libraries on different models |
| Empty-result handover | Paper input [] checked against downstream design | Observe whether downstream handles an empty value; do not presuppose a return |
| External write division of labor | Connect a separate business interface | Order writes, backfill and synchronization are not completed inside the orchestration |
Three common errors
- Treating a retrieval hit as authorization. Retrieval returns candidates by semantics and does not judge whether stall A is entitled to view buyer B's unsettled record. The error shows up as using a similarity score to exclude unrelated business. Check: input the two sample statements above, compare whether the returned materials contain the subject and counterparty fields, and observe whether records unrelated to A and B are treated as authorized.
- Treating a pending item as settled. Material statement one states "the amount is not settled," while the draft sentence says "has fully settled the payment." Same subject, same goods, same field, mutually exclusive values; this is a contradiction. The error shows up as adopting the draft sentence directly. Check: compare the status field in statement one with the status wording in the draft sentence, and observe whether a contradiction is marked and the item returned.
- Treating the lease term as a supply period. Material statement two records only that the lease runs until 31 December 2024 and does not state a supply period. The error shows up as deriving "supplies steadily over the long term" from the lease term. Check: compare the fields of statement two with the wording of the draft sentence, and observe whether it is marked as unsupported and the evidence gap retained.
How to verify the setup
- Form input and user selection check. Input the two sample source statements above, fill in subject, counterparty, goods, period and document status in the form input node, and after submission compare the fields received by later nodes with the entered values. Observe whether they match item by item and whether the yes branch of the user selection node is entered.
- Retrieval and empty-result check. Input the sample statements and observe whether the recalled materials contain the subject and counterparty fields; on the failure branch, record a miss or a missing field. Separately use a paper input of [] to check the downstream design and observe whether an empty value is handled. Do not claim that a fictional rule makes retrieval always return [].
- Draft sentence judgment check. Input the draft sentence to be judged together with the two source statements, compare values for the same subject, same period and same field, and observe whether "settled" and "not settled" are judged as a contradiction and whether "supplies steadily over the long term" is judged as unsupported. For libraries on different vector models, check the identifier first and exclude non-matching ones; do not run cross-model retrieval to compare missed recalls.