Web application

Interface capture from the visual workflow repository.

Use case

Research workflows need clear execution paths and a way to inspect the sources and results produced at each step.

How it works

A visual graph editor with typed ports, branching, nested workflows, and step-by-step run controls. Workflows and run snapshots are persisted per signed-in user.

Inspect the implementation

The repository documents the runtime, provider adapters, persistence layer, and quality checks. The interface capture comes from the repository.

Scope

Built-in Objective, Research, Analysis, Condition, and Record nodes. Runs use a depth limit of 4 and a 24-step budget.

Execution and evidence

Each server step claims the expected run version before invoking an executor. Stale requests are rejected before provider calls. Analysis citations are checked against source IDs retrieved during that run. Missing credentials, empty results, malformed output, and provider failures are recorded as errors.

The documented run envelope is one search, at most five source pages, one model call, depth 4, and a 24-step budget.

Review procedure

npm run typecheck; npm test; npm run build:dev

Content reviewed against repository documentation on November 5, 2026.