What the documents look like
A brand-run livestream carries its own scripting, inventory and after-sales obligations, and does not depend primarily on creator commission. Copy drafting for products and marketing draws on four document types: the livestream script, the product explanation card, the shift schedule and the livestream review. Data sources named in the brief include the Douyin Shop compass, Juliang Qianchuan, livestream comments and transaction details. Whether a promotional sentence can stand depends on whether the explanation card, script or review actually states the corresponding fact. Brand livestream teams, floor controllers, hosts and ad buyers each supply different materials, and the drafting step needs to place source wording and proposed sentences into the same form interaction for comparison. Update frequency does not affect the form behavior described on this page, so it is left aside here.
Constraints at the interactive forms 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 the flow waits for the user to complete the required information and submit it. The submitted values are then passed to subsequent nodes. The User Selection node is also a user interaction node. When it triggers, the conversation likewise enters an interaction state, records the workflow state, and waits for the user to make a choice; on that choice it executes the "yes" branch.
Neither node carries a business database. Field validation, business approval, write-back and batch operations need to be implemented in an external system or in later nodes. The User Selection node is not a personnel directory or a business data selector; it only routes on the user's choice. The Form Input node is not a business database; it collects submitted values and passes them onward.
Hypothetical paper exercise: the source wording is "This session's explanation card states: Model A thermos, capacity 500 ml, inner liner material 304 stainless steel, orders placed between 1 March 2025 and 31 March 2025 receive a cup brush." The proposed sentence to be judged is "Model A thermos has a 316 stainless steel inner liner, and orders placed this month receive a cup brush." The object under comparison is Model A thermos, the field is inner liner material, and the period is March 2025. The source states 304 stainless steel while the proposed sentence states 316 stainless steel, so the same field carries mutually exclusive values. The cup brush is stated in the source. The material sentence is not supported by the source. This exercise is paper only and was not submitted or deployed.
Configuration and implementation checks
| Configuration item | Type | Relation to this page |
|---|---|---|
| Form Input node | Documented node | Enters the interaction state on trigger, collects required information and passes it to later nodes |
| User Selection node | Documented node | Enters the interaction state on trigger and executes the "yes" branch on the user's choice |
| Required information list | Implementation check | Lists the fields this task cannot omit and tests the missing-item and completed-item behaviors separately |
| Material field comparison | Implementation check | Compares the proposed sentence's material value against the explanation card wording |
| Period field comparison | Implementation check | Compares the proposed sentence's period against the validity range stated in the explanation card |
| Downstream handling split | Implementation check | Field validation, approval, write-back and batch operations are implemented in an external system or later nodes |
Hypothetical starting point for this exercise: the required fields are set to product name, promotional field and material source, chosen because these three correspond to the comparison object, the field and the source in this sample. Completeness is judged by comparing each item against the explanation card wording. This starting point is a paper setting, not an official default.
Three common errors
- Treating the User Selection node as a personnel directory or business data selector. The node only executes a branch on the user's choice and does not provide business data retrieval.
- Treating the Form Input node as a business database. The node collects submitted information and passes it to later nodes, and does not carry database functions.
- Treating a field the source does not state as a denial or a conflict. A field that is not stated, or for which only related-stage evidence exists, is unsupported or pending verification; a conflict requires mutually exclusive values in the same field.
How to verify the setup
- Enter the hypothetical source wording and the proposed sentence above, and compare the inner liner material field. The source states 304 stainless steel and the proposed sentence states 316 stainless steel; the two are mutually exclusive, so the result is a conflict. The expected observation is that the comparison record marks this field as conflicting.
- Enter the same source wording and proposed sentence, and compare the cup brush field. The source states a cup brush for orders placed between 1 March 2025 and 31 March 2025, and the proposed sentence says orders placed this month receive a cup brush; the periods agree, so the result is supported. The expected observation is that the comparison record marks this field as consistent.
- Enter a proposed sentence whose material is not stated in the source, and compare the material field. The source has no corresponding statement, so the result is unsupported. The expected observation is that the comparison record marks it as pending verification and does not mark it as a denial. All three are paper walkthroughs and were not run.