What the documents look like
Community group-buy presale order collection runs in a fixed business order: orders are gathered before a stated cut-off time, and procurement and fulfilment are then organised from the collected order result. The daily materials are the presale product table, the collection result, the procurement plan, and the cut-off notice. These materials update daily or per session. The comparison task on this page checks contract and transaction materials against each other: contract clauses and quotation materials supplied by the supplier or purchasing side are compared item by item with the platform-side transaction records, confirming whether the counterparty, object, quantity, price, and validity period agree.
This comparison depends on two interaction node types to collect material information, and on later nodes to carry the judgement. The form input node and the user selection node are the documented mechanisms for that collection. The comparison itself is a downstream activity: retrieval, form collection, and user selection gather and pass values, and they do not constitute an authorisation to execute a business action.
Constraints at the workflow routing step
When the form input node is triggered, the conversation enters an interaction state, the workflow state is recorded, and the workflow continues after the user completes the interaction. The node collects the form information the user fills in and passes it to later nodes. The user selection node also enters an interaction state, records the workflow state, and continues after the user completes the interaction; when the user makes a choice, the node judges that choice and executes the "yes" branch.
The waiting and state recording are behaviours of the interaction nodes themselves. The documentation describes no global state-recording switch, no guaranteed submission count, and no automatic judgement. Collected material information must be passed explicitly to the later retrieval, judgement, or interface node. Order writes, document backfill, and external status synchronisation require a separate business interface or a later process. Retrieval and forms collect and pass values only; they do not authorise execution. A pending review is not evidence that an operating permission is absent. Signing, reaching cooperation, and contract effectiveness are three distinct facts. A quotation validity period does not express a supply period.
Configuration and implementation checks
The table below uses one hypothetical paper exercise sample for this page and lists documented settings or implementation check items relevant to this feature and the primary task.
| Configuration item | Hypothetical starting point for this exercise | Reason and comparison method |
|---|---|---|
| Form input node fields | Supplier name, contract number, quotation validity period | Fields must cover the same counterparty, same period, and same field needed for the sample judgement |
| User selection node branches | Two branches, "materials complete" and "materials pending" | Verify branch connections one by one; compare the user choice with the downstream node direction |
| Interaction state carry-over | Submitted information passed to the comparison node | Compare the submitted value with the value read downstream |
| Output carry-over node | Comparison result passed to the judgement node | Compare the correspondence between output fields and input fields |
| External write division | Order writes and document backfill use a separate interface | Check whether an independent business interface or later process exists |
| Retrieval scope identifier | Distinguish vector models by library identifier | Check the identifier only and exclude non-matching libraries; do not run cross-model retrieval comparisons |
Three common errors
- Treating the interaction state record of a form input or user selection node as an authorisation credential. The node recording state is an interaction behaviour. Signing, reaching cooperation, and contract effectiveness are three distinct facts. A pending review does not demonstrate that an operating permission is absent.
- Treating a retrieval or similarity result as a permission or entity filter. A relevance score does not carry out category, entity, or permission filtering. A retrieval result cannot replace a business authorisation judgement.
- Substituting related-stage evidence for a same-field determination. A contradiction exists only when the same counterparty, the same period, and the same field carry clearly mutually exclusive values. A field that is not stated, or evidence from a related stage only, is unsupported or pending verification.
How to verify the setup
Hypothetical exercise sample: the contract text provided by Supplier A reads "This contract number is HT-2024-031, the supplier is Supplier A, and the quotation validity period ends on 30 June 2024." The platform-side collection result records "Supplier A, Product A, quantity 200 pieces, cut-off date 20 June 2024." The proposed judgement sentence is "Supplier A's quotation remains valid on the cut-off date."
- Verification one: Input the contract text and the proposed judgement sentence, and compare the contract number, supplier name, and quotation validity period fields. The judgement sentence is supported only when the contract text states a quotation validity period that covers the cut-off date. In this sample the validity period ends on 30 June 2024, later than the cut-off date of 20 June 2024, so the judgement sentence is supported.
- Verification two: Input the collection result and the contract text, and compare the supplier name and product object. The same counterparty and same object are recognised only when the names and the product object agree in both places. If the names do not agree, record the item as pending verification and do not record it as a contradiction.
- Verification three: Input one quotation material that does not state a validity period, and compare whether it contains the period field needed for the judgement. Whether the period covers the cut-off date can be judged only when the material clearly states a validity period. When the field is missing, record the evidence gap and do not supply an authorisation or effectiveness clause.