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 (Beta)
A guided process design layer above the runtime.
Use it when you want to:
- describe a process in business language
- review assumptions before publish
- simulate the structure of a process before deployment
- publish governed workflow bundles into an org
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 compiled runtime artifact
Start here:
Which path should you choose?
| If you need... | Start with... |
|---|---|
| guided authoring and publishing | Process Studio (Beta) |
| 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
- AI generation is a compiler-style drafting path
- 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.