What the documents look like
A brand-run livestream carries its own script, inventory and after-sales work; creator commission is not the main arrangement. That difference shapes copy drafting, because promotional sentences in the product talking card and the livestream script must correspond line by line with product material, and complaint exposure sits with the brand. Main data sources are Douyin Store Compass, Juliang Qianchuan, livestream comments and transaction details. Everyday documents include the livestream script, product talking card, shift schedule and livestream review.
This page covers only workflow routing inside product and marketing copy drafting: using interaction nodes to collect required information, following branches by selection, and passing collected values to later nodes. Whether a promotional sentence is supported by material belongs to copy checking and is not expanded into an enterprise identity certification tutorial.
Constraints at the workflow routing step
The Form Input node is a user interaction node. When it triggers, the conversation enters an interactive 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 later nodes. The User Selection node is also a user interaction node: when the user makes a choice, the node judges that choice and executes the "yes" branch. Both can be added repeatedly and trigger execution.
Neither node writes orders, backfills documents or synchronizes external status. Those actions require a separate business interface or later process. Retrieval recalls content and does not carry permission or entity isolation; a similarity score is not a category, entity or permission filter. Knowledge base reference limits use the unit recorded in the documentation and are not converted into an item count. An empty-result handoff can be checked against a clearly stated paper input for downstream design, without claiming that a particular retrieval necessarily returns empty.
Hypothetical drill sample: the source material reads, "The product covered by this session's talking card is Model A thermos cup, material marked as 304 stainless steel, quality inspection report number QC-2024-0311 for this batch, report date 11 March 2024, applicable sales period 1 March 2024 to 31 March 2024." The proposed draft sentence reads, "The Model A thermos cup uses a 304 stainless steel inner liner and this batch has passed quality inspection." To be judged: the subject and material field of the draft sentence match the material; the inspection conclusion appears in the material only as a report number and date, with no conclusion text recorded, so that part is unsupported and the evidence gap must be recorded.
Configuration and implementation checks
| Configuration item | Hypothetical starting point for this drill | Reason and comparison method |
|---|---|---|
| Form Input node | Enabled, with fields for product name, batch and sales period | Collects the subject and period needed for drafting; compare field by field against the draft sentence |
| User Selection node | Enabled, with branches "adopt draft sentence" and "return for revision" | Executes the matching branch after selection; check whether branch connections are verified one by one |
| Interactive state check | Enters interactive state and records state after trigger | Compare with the documented description; no separate global state switch is set |
| Output handoff | Passes collected values to a later retrieval or judgment node | Compare each output item against the corresponding input item |
| External action split | Order writing, document backfill and external synchronization connect to separate interfaces | This page configures none of these actions and only marks ownership |
| Reference limit | Set in the unit recorded in the documentation | Compare against the documented unit; do not convert into an item count |
Three common errors
- Treating a similarity score as a category or permission filter, so that a low score is read as excluding unrelated business or unauthorized records. Retrieval does not carry authorization; the permission source must be checked separately.
- Treating the "yes" branch of the User Selection node as an automatic judgment without verifying branch connections one by one, so that a selection leads to the wrong node.
- Treating a pending or submitted form as approved or already written, or treating an interactive state record as completed external synchronization. Submission, approval and writing are distinct facts.
How to verify the setup
- Enter the hypothetical sample's source material and draft sentence, and compare whether the subject, material and batch fields agree. When conclusion text is absent, record the item as unsupported rather than as a negation or conflict.
- Trigger the Form Input node and check whether the conversation enters the interactive state and whether collected values reach later nodes after required fields are submitted. The condition is met when output and input correspond item by item.
- Trigger the User Selection node and check whether the chosen option executes the matching branch and whether branch connections are verified one by one. If execution goes to a branch other than the selected one, the condition is not met; record the actual observation.
Knowledge bases built on different vector models cannot be associated together. Check identifiers first and exclude those that do not match; do not run cross-model retrieval to compare missed recall. Image retrieval requires a corresponding image input and model capability, and reranking requires a model enabled according to settings; the optional paths listed in the documentation do not mean every request executes all of them.