YOU

Dynamic Workflows

A dynamic workflow is a JavaScript orchestrator-backed factory whose live run is a Factory Session—not a separate runtime type.

What It Is

A dynamic workflow is a JavaScript orchestrator-backed (`JAVASCRIPT`) factory. Instead of Petri graph fields, the factory carries JavaScript orchestrator configuration—source identity, metadata, argsSchema, and related knobs. The live run is still a Factory Session: the same durable runtime object used for every live orchestration. Dynamic workflow is shorthand for that JavaScript-backed session shape, not a separate DynamicWorkflowRun type.

When To Use

Use Dynamic Workflows when you need to author or validate JavaScript orchestrator source, start a durable JavaScript Factory Session, or inspect status and results through the shared session surface. Reach for them when Petri factory.json topology is not the right fit and a live JavaScript orchestrator should drive the run.

How It Fits

Dynamic workflows use the shared Factory Session API surface across CLI, Model Context Protocol (MCP), and related hosts. Validate source, start a session, and read status or results through that same session identity. Configuration resolves JavaScript orchestrator source from a project root and chooses how an MCP host launches the serve path. Packaged factories and Petri configuration remain sibling factory shapes; sessions stay the live handle for every run.

Limits And Assumptions

Dynamic Workflows covers JavaScript orchestrator-backed factories and when they matter. It is not a schema embed, not an OpenAPI or operation catalog, not the Cursor first-loop guide, and not Petri factory.json topology. Orchestrator fragments, invocation signatures, CLI knobs, and API relationship depth live on the Dynamic Workflows reference page.

Tags

On this page

What It IsWhen To UseHow It FitsLimits And AssumptionsTags