WorkflowsDashboardsModule — the Workflows app: the saved-workflow list, the Create Workflow front
door, and the run history.
A separate app rather than a tab inside AI, per D18/D19: the vocabulary rule puts Workflow in
front of end users, and filing the surface under "AI" would contradict that at the navigation
level. See mockups/workflow-ux/front-door-v1.html for the locked design.
The app owns runs, not editing. There is exactly one workflow editor — the AI Agents form —
and the front door hands off to it after Workflow.Save rather than opening a second canvas. What
this app adds that exists nowhere else is the Runs surface: a task graph outlives the run that
submitted it, so a scheduled or MCP-triggered workflow has no owning conversation to be found
from. Runs are listed here by what a person remembers — what ran, when, and how it ended.
WorkflowsDashboardsModule — the Workflows app: the saved-workflow list, the Create Workflow front door, and the run history.
A separate app rather than a tab inside AI, per D18/D19: the vocabulary rule puts Workflow in front of end users, and filing the surface under "AI" would contradict that at the navigation level. See
mockups/workflow-ux/front-door-v1.htmlfor the locked design.The app owns runs, not editing. There is exactly one workflow editor — the AI Agents form — and the front door hands off to it after
Workflow.Saverather than opening a second canvas. What this app adds that exists nowhere else is the Runs surface: a task graph outlives the run that submitted it, so a scheduled or MCP-triggered workflow has no owning conversation to be found from. Runs are listed here by what a person remembers — what ran, when, and how it ended.