feat: Prototype workflow authoring and run inspection #312

New issue

Closed

opened 2026-07-13 19:46:08 +02:00 by dries · 0 comments

dries commented

2026-07-13 19:46:08 +02:00

Owner

Parent

#311

What to build

Create a throwaway frontend prototype that resolves how users author workflow definitions and inspect very large workflow runs before production UI implementation begins. Use realistic fixtures containing parallel branches, nested mapped items, retries, blocked nodes, resource waits, and artifacts.

Acceptance criteria

Users can switch between YAML/JSON source and a read-only graph representation.
The prototype demonstrates navigation and node inspection on a large synthetic DAG.
Dynamic map branches can be collapsed and expanded without losing context.
Node details cover attempts, logs, artifacts, resources, and workspace ownership.
Pending, ready, running, waiting, successful, failed, skipped, blocked, unknown, paused, and canceled states are visually distinguishable and accessible.
Desktop and narrow viewport behavior is demonstrated.
The prototype records decisions that the production tracer must preserve.
The prototype is explicitly disposable and introduces no production dependency.

Blocked by

None — can start immediately.

## Parent #311 ## What to build Create a throwaway frontend prototype that resolves how users author workflow definitions and inspect very large workflow runs before production UI implementation begins. Use realistic fixtures containing parallel branches, nested mapped items, retries, blocked nodes, resource waits, and artifacts. ## Acceptance criteria - [ ] Users can switch between YAML/JSON source and a read-only graph representation. - [ ] The prototype demonstrates navigation and node inspection on a large synthetic DAG. - [ ] Dynamic map branches can be collapsed and expanded without losing context. - [ ] Node details cover attempts, logs, artifacts, resources, and workspace ownership. - [ ] Pending, ready, running, waiting, successful, failed, skipped, blocked, unknown, paused, and canceled states are visually distinguishable and accessible. - [ ] Desktop and narrow viewport behavior is demonstrated. - [ ] The prototype records decisions that the production tracer must preserve. - [ ] The prototype is explicitly disposable and introduces no production dependency. ## Blocked by - None — can start immediately.