What the documents look like
Creator-exclusive livestream sales collaboration centers on external creator fulfillment and commission settlement. Brand commercial staff, MCN agencies and creator managers reconcile four document types: the creator cooperation agreement, the commission setup sheet, the sample shipment sheet and the livestream performance report. After each livestream, the commission rate stated in the agreement is compared with the actual value on the commission setup sheet, and sample shipment records are checked against the products that appeared in the livestream report. Subject, period and field values across these materials must align item by item before any difference can be identified. The primary data sources for this category are the selected alliance, the creator marketplace, creator historical data and store transaction details. Errors in this reconciliation surface as commission settlement disputes, inflated traffic and damage to brand reputation.
Constraints at the workflow routing step
Workflow routing breaks document comparison into an executable node sequence. 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 required fields and submits, the collected form information is passed to subsequent nodes. The user selection node is also a user interaction node: it triggers the same interaction state, and when the user makes a choice, the node evaluates that choice and executes the corresponding "yes" branch. Interaction state recording is behavior of the interaction nodes; no separate global state recording switch is documented. Information collected must be explicitly passed to subsequent retrieval, judgment or interface nodes, and outputs compared against inputs item by item. Order writes, document backfill and external status synchronization require a separate business interface or downstream flow; the nodes themselves do not perform these business actions. Retrieval is not authorization: material needed for a check must sit inside an accessible target retrieval scope or be supplied as explicit manual input.
Hypothetical paper exercise sample. A brand commercial staff member submits the original text of a creator cooperation agreement reading: "Party A commissions Party B to conduct an exclusive livestream sales campaign from June 1, 2025 to June 30, 2025, with a commission rate of 20% of sales, and sample shipment subject to the shipment sheet confirmed by Party A." A commission setup sheet is submitted alongside it reading: "The commission rate for this livestream is set at 18% of sales, effective June 1, 2025." The draft sentence to be assessed is: "The commission rate agreed in the cooperation agreement matches the commission setup sheet." Comparison shows the two materials carry different values in the commission rate field, so the draft sentence does not match the source text. This sample only illustrates the comparison method; it does not claim that any execution has taken place.
Configuration and implementation checks
| Configuration item | Setting or check for this page | Relation to the sample |
|---|---|---|
| Form input node | Collects agreement, commission setup sheet and other material text; passes to later nodes after submission | Both materials in the sample are submitted through form input |
| User selection node | After the comparison result is output, the user chooses whether to enter a manual review branch | A mismatch finding on the draft sentence can trigger a review choice |
| Output handoff check | Compare form output against the input fields of the later judgment node item by item | The commission rate field in the sample must reach the comparison node |
| Interaction state check | Records interaction node behavior; no separate global state recording switch | The sample enters the interaction state after submission |
| External action division | Order writes, document backfill and external status synchronization connect to a separate business interface | The sample involves no order write or external synchronization |
| Retrieval scope check | Material needed for the check must be in an accessible target retrieval scope or explicit manual input | The sample materials are provided as manual input |
Three common errors
- Treating information collected by the form input node as already authorized for execution. The form input node only collects user-entered information and passes it to later nodes; business verification, approval, database writes and external synchronization need a separate downstream implementation. Submitting two materials in the sample does not mean the comparison has been authorized or completed.
- Treating the "yes" branch of the user selection node as an automatic judgment result. The user selection node executes the corresponding branch after the user makes a choice; the node itself does not automatically decide whether materials match. In the sample, the draft sentence must be judged by the comparison node before the user chooses whether to enter review.
- Treating interaction state recording as a global state snapshot guarantee. Interaction state recording is behavior of the interaction nodes, and no separate global state recording switch is documented. Entering the interaction state after submission in the sample does not mean the system automatically saved a complete snapshot or guarantees the number of submissions.
How to verify the setup
- Input the agreement original text and the commission setup sheet original text from the sample, and compare the values of the two materials in the commission rate field. The agreement states 20% and the commission setup sheet states 18%; the same field carries different values, so the result is a mismatch. The draft sentence "The commission rate agreed in the cooperation agreement matches the commission setup sheet" does not match the source text, and this finding satisfies the condition.
- Input the draft sentence from the sample and compare its wording against the corresponding fields in the two source texts. The draft sentence claims the two materials match, while the source texts show commission rates of 20% and 18%, so the draft sentence is not supported by the source text. When this is observed, the draft sentence should be marked as pending verification or requiring correction.
- Input the agreement period field "June 1, 2025 to June 30, 2025" and the commission setup sheet effective date "June 1, 2025", and compare the coverage relation of the two materials in the period field. The commission setup sheet states only an effective date and no expiry date, so the period coverage relation cannot be determined from the available source text. This field comparison result is pending verification, and the evidence gap is preserved.