What the documents look like
Creator sales campaigns turn on external creator fulfillment and commission settlement. Brand business staff, MCN agencies and creator managers handle the same four document types across every campaign: creator cooperation agreements, commission setting sheets, sample shipment sheets and livestream performance reports. The state of these materials determines which operations may continue at handover and which requests remain pending verification.
A cooperation agreement may sit at pending review, signed or effective. A sample shipment sheet records dispatch and receipt. A commission setting sheet states the rate and the settlement basis. A livestream performance report aggregates session transaction and after-sales data. The supplied brief gives update frequency as per session and weekly. This page does not derive batch synchronization, full synchronization or real-time triggers from that frequency.
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 execution continues after the user completes the interaction. The node collects required information and passes what the user submits to later nodes. The user selection node behaves the same way at trigger, then evaluates the user's choice and executes the "yes" branch. Branch connections require item-by-item verification. The interaction state is behavior of the interaction nodes; no separate global state-recording switch is documented.
Collected information must be passed explicitly to later retrieval, judgment or interface nodes, and outputs are compared against inputs item by item. Order writes, document backfill and external status synchronization require a separate business interface or a later process. Retrieval and form submission do not by themselves constitute authorized execution.
Hypothetical paper exercise: a brand business staff member submits a handover request for a creator campaign. The attached material text reads: "Cooperation agreement number H-001, signature status is pending review; commission setting sheet states a commission rate of 20% and a settlement cycle of 7 days after the session ends; sample shipment sheet shows the sample dispatched, receipt column blank." The proposed determination sentence is: "This cooperation is signed and effective, and commission settlement may be executed." This exercise is used only for checking on this page and points to no real entity.
Configuration and implementation checks
| Configuration item | Setting or check on this page | Relation to the exercise |
|---|---|---|
| Form input node | Enters interaction state on trigger, collects required information | Collects material fields in the handover request |
| User selection node | Executes the "yes" branch after the user chooses | Confirms whether the handover request continues |
| Interaction state check | Recorded state is behavior of the interaction node | Checks whether the exercise request waits in interaction |
| Output handoff check | Collected information passed to later retrieval or judgment nodes | Compares exercise fields against downstream input |
| External operation split | Order writes and status synchronization use a separate business interface | Commission settlement does not run from form submission |
| Retrieval scope check | Materials checked within the target range the operator may access | Records an evidence gap when absent |
Three common errors
- Treating pending review as signed. In the exercise, cooperation agreement number H-001 has signature status "pending review," while the proposed sentence says "signed and effective." Input is the exercise source text and the drafted sentence; the compared field is signature status. Pending review is not completed signing and is not contract effectiveness, so the determination is not supported.
- Treating form submission as authorized execution. After the exercise request is submitted, only information collection is complete; commission settlement requires a separate business interface. Input is the handover request and the node output; the comparison is whether a downstream business interface call record exists. With no such record, settlement remains unexecuted.
- Treating a retrieval hit as permission confirmation. A material entering the retrieval range only means it can be recalled; it does not mean the current operator is authorized to execute settlement. Input is the retrieval result and the operator authorization record; the comparison is whether both refer to the same subject and the same period. When the authorization record is absent, the matter stays pending verification.
How to verify the setup
- For the exercise source text and proposed sentence, input "Cooperation agreement number H-001, signature status is pending review" and "This cooperation is signed and effective." Compare the value of the signature status field. The expected observation is that pending review and signed are mutually exclusive, so the sentence does not meet the condition and is recorded as unsupported.
- For the exercise handover request, input the form input node output and the downstream node connections. Compare whether the submitted information is passed explicitly to a retrieval or judgment node. The expected observation is complete field handoff. If no downstream business interface call record exists, commission settlement remains unexecuted.
- For retrieval over the exercise materials, input the explicit paper empty result [] and the downstream handoff design. Compare whether the downstream handles the empty result through its designated branch. The expected observation is that an empty result does not trigger a settlement action. Whether retrieval hits does not constitute a permission judgment; when there is no hit, record the gap and do not claim that a fictional rule must return empty.
This page addresses only creator sales campaigns, operations permission and handover management, and workflow routing. Which materials, operations and requests at handover sit at which authorization state cannot be resolved by treating retrieval or a form as authorized execution.