Reported by: codex
Requested by: jmr.pineda
Priority: P3
Affected surfaces: workflow authoring UX, runtime-compatible editing, design tooling
Constraints: the editor must stay aligned with the YAML runtime instead of inventing a separate execution model
Summary
Build a visual workflow editor that sits on top of the existing YAML runtime so users can author and inspect workflows through a graphical surface without breaking runtime compatibility.
Problem / opportunity
The current authoring surface is powerful but text-centric. A visual editor could broaden usability, reduce onboarding friction, and make complex orchestration easier to inspect.
Requested behavior
Users should be able to create and edit runtime-valid workflows through a visual interface that preserves or generates the canonical YAML representation.
Scope
- In scope: visual authoring, graph or flow editing, YAML alignment, round-trip compatibility expectations.
- Out of scope: replacing the YAML runtime or introducing a separate workflow engine.
Acceptance criteria
- Users can create or edit workflows visually while preserving runtime-valid YAML output.
- The editor reflects key orchestration concepts already present in the runtime.
- The resulting artifacts remain reviewable and usable in GitOps workflows.
Notes
- Source: local roadmap at
.doc/positioning-and-roadmap.md.
- This issue was created while migrating local backlog ownership to GitHub.
Reported by: codex
Requested by: jmr.pineda
Priority: P3
Affected surfaces: workflow authoring UX, runtime-compatible editing, design tooling
Constraints: the editor must stay aligned with the YAML runtime instead of inventing a separate execution model
Summary
Build a visual workflow editor that sits on top of the existing YAML runtime so users can author and inspect workflows through a graphical surface without breaking runtime compatibility.
Problem / opportunity
The current authoring surface is powerful but text-centric. A visual editor could broaden usability, reduce onboarding friction, and make complex orchestration easier to inspect.
Requested behavior
Users should be able to create and edit runtime-valid workflows through a visual interface that preserves or generates the canonical YAML representation.
Scope
Acceptance criteria
Notes
.doc/positioning-and-roadmap.md.