Workflow Creation

Purpose

Design one reliable video-production workflow on the PostPlus workflow platform for UGC-style multi-clip video generation. The user-facing deliverable is a named workflow on the user's account with a saved definition version, ready to quote and launch. Do not produce standalone definition files, exported JSON graphs, audit packets, or post-production notes unless the user explicitly asks.

Quality checks are internal; do not ask the user whether to run QA. Ask only when missing brand, product, reference, workflow-goal, naming, or claim-boundary facts would change the workflow.

Platform Tool Surface

Workflow authoring is ONE server-validated capability with two front doors. Use whichever the current session exposes — never mix them, and never bypass server validation:

• Workspace assistant typed tools: workflow_read (resolve by name via action=list, inspect nodes/slots/versions via get, read runs via runs_get), workflow_author (create a blank or template-seeded workflow; propose_edit structural edits - add_node / update_node / remove_node / connect_nodes - returning an honest validation verdict without persisting), apply_workflow_edit_to_canvas (same operations when the user's live canvas is attached), save_workflow_version (persist a proposal; always human-approved), then quote_workflow_run and launch_workflow_run.
• CLI agent postplus workflow commands - the same verbs, results as JSON, requiring a logged-in session (postplus auth login): postplus workflow list / show and runs / run-show (read), create, propose (= propose_edit: preview + validate, persists nothing), save (= save_workflow_version: persist a new immutable version), quote, and launch. Structural edits go in a --operations JSON array of the same add_node / update_node / remove_node / connect_nodes ops. Run postplus workflow help for exact flags.

The two surfaces map one-to-one onto the same hosted verbs and the same validation; propose mirrors propose_edit, save mirrors save_workflow_version, quote mirrors quote_workflow_run, launch mirrors launch_workflow_run.

Boundaries: