What the documents look like
Creator-exclusive sales campaigns depend on external creator fulfillment and commission settlement. The procurement and supplier materials for these campaigns draw on selected alliance data, creator marketplace records, creator historical data and store transaction details. Day-to-day documents concentrate in four types: creator cooperation agreements, commission setting sheets, sample shipment forms and livestream performance reports. These materials update per session or per week, and they directly affect which fields a routing node collects, when it collects them, and which values it passes downstream. The cooperation agreement and the commission setting sheet carry commercial terms. The sample shipment form concerns physical goods movement. The livestream performance report concerns fulfillment results. The four document types serve different input roles inside one workflow.
Constraints at the workflow routing step
The form input node belongs to the user interaction node category. When it triggers, the conversation enters an interaction state, the workflow state is recorded, and after the user fills required information and submits, the node collects the submitted form information and passes it to subsequent nodes. The user selection node also belongs to the user interaction node category. When it triggers, the conversation enters an interaction state and the workflow state is recorded; when the user makes a choice, the node evaluates that choice and executes the "yes" branch. Both nodes can be added repeatedly and trigger execution. If the fields needed for procurement and supplier materials come from the four document types above, the nodes must explicitly collect them and compare each output against its input. Order writing, document backfill and external status synchronization require a separate business interface or a downstream process; the interaction nodes themselves do not complete those business actions.
Hypothetical paper exercise sample: a brand business contact hands over a creator-exclusive campaign to a creator agent. The material text reads: "The creator cooperation agreement states the cooperation period runs from June 1, 2024 to June 30, 2024, and the commission rate is 15% of sales. The commission setting sheet states the same period carries a commission rate of 15%. The sample shipment form states two samples were sent on June 3." The draft sentence to be assessed reads: "The cooperation has been signed and commission is executed at 15%." The draft sentence corresponds only to the period and rate fields in the materials. Signing status and execution status require separate verification.
Configuration and implementation checks
| Configuration item | Setting or check for this page | Relation to the sample |
|---|---|---|
| Form input node | Enters interaction state on trigger, collects required information, passes it downstream after submission | Collects agreement period, commission rate, sample shipment date |
| User selection node | Executes the corresponding "yes" branch after the user makes a choice | Selects continue or return based on the draft sentence assessment |
| Output handoff check | Passes collected information explicitly to downstream retrieval, judgment or interface nodes | Compares the period, rate and date fields |
| Interaction state check | State recording is interaction-node behavior; no separate global state recording switch is set | Checks whether workflow state is retained during interaction |
| External action division | Order writing, document backfill and external status synchronization require a separate business interface or downstream process | The draft sentence concerns signing and execution, not completed at these nodes |
| Retrieval scope check | Materials needed for verification must sit in an accessible target retrieval scope or explicit manual input | Records the gap when missing; no authorization clause is fabricated |
Three common errors
- Treating the commission rate collected by the form input node as an already-effective commission execution. The input is the 15% stated on the commission setting sheet; the comparison object is the 15% stated in the cooperation agreement. Matching values across the two fields support only that the rate figures are equal; they do not support that commission was actually settled at that rate. The observable result is whether the two rate fields hold the same value, while settlement status remains unknown.
- Treating the "yes" branch of the user selection node as signing confirmation. The input is the draft sentence "The cooperation has been signed and commission is executed at 15%"; the comparison object is the period and rate fields in the materials, which do not state signing status. The observable result is whether the draft sentence exceeds what the materials support; if it does, it must be returned for supplementary material.
- Treating a retrieval hit as authorized execution. The input is the cooperation agreement fragment returned by retrieval; the comparison object is the authorization boundary of the current handover request. A retrieval result does not constitute approval or execution permission. The observable result is whether the request carries an explicit authorization source; when missing, record the gap.
How to verify the setup
- Input the three material sentences and the draft sentence from the hypothetical sample, and compare whether the signing and execution status claimed by the draft sentence has a corresponding field in the source text. The condition is satisfied when the draft sentence restates only the period and rate and does not assert that signing or settlement is complete. If the assertion exceeds that scope, return for supplementary material.
- Input the 15% stated on the commission setting sheet and the 15% stated in the cooperation agreement, and compare the values of the two rate fields. The condition is satisfied when both fields hold the same value and the periods match. If the periods do not match, record as pending verification rather than declaring a conflict.
- Input the cooperation agreement fragment returned by retrieval and the current handover request, and compare whether the request carries an explicit authorization source. The condition is satisfied when the request notes the authorizing subject and scope. If only a retrieval hit exists without an authorization note, record an authorization gap and do not execute downstream business actions.