Authoring
Hyphen supports more than one authoring level.
You can start with a guided process-design surface, generate a draft from business language, or work directly with the workflow DSL when you want explicit control.
The authoring stack
Process Studio
A catalog of governed cases above the runtime, and a plain-words path for work no case covers.
Use it when you want to:
- pick a case that already runs and make it your own
- change content, connections, and people, never the steps
- run it, or hand it to a developer or an assistant
- describe work no case covers and get a checked case listed for your organization
Start here:
AI workflow generation
An advanced authoring path that turns a natural-language description into a draft Hyphen workflow specification.
Use it when you want to:
- bootstrap a draft quickly
- generate a workflow definition and supporting artifacts
- work closer to the compiler and runtime layer
Start here:
Workflow DSL
The direct execution contract for Hyphen workflows.
Use it when you want to:
- define exact branching and step structure
- work directly with primitives and actions
- review or hand-edit the definition the runtime executes
Start here:
Which path should you choose?
| If you need... | Start with... |
|---|---|
| a governed case you can run today, or a case built from your own words | Process Studio |
| a generated first draft from a business description | AI workflow generation |
| maximum low-level control | Workflow DSL |
Important distinction
All three authoring paths target the same runtime.
- Process Studio sits above the runtime; its cases are published workflows and agents
- AI generation is a drafting path for engineers
- the DSL remains the execution-facing source of truth
That means teams can start at the level that suits them and still publish into the same governed Hyphen system.