How it works
A workflow engine you can watch
FlowPilot turns a task into explicit steps, executes them one at a time on the server, records every state change, and pauses for a human decision before anything is finalized. It is a demonstrator: it works on the data you paste in and on local application state only.
Step state machine
Every transition is checked; anything not listed below is rejected.
| From | Allowed next states |
|---|---|
| pending | running, skipped |
| running | completed, failed, awaiting_approval |
| awaiting_approval | completed, rejected, skipped |
| failed | pending, skipped |
| completed | — (terminal) |
| rejected | — (terminal) |
| skipped | — (terminal) |
Guarantees in this demo
- — Steps run strictly in order; a step cannot start until every earlier step has completed.
- — The approval checkpoint cannot be auto-approved: the run stays paused until a person approves or rejects.
- — Rejecting requires a reason, skips the remaining steps and ends the run without a final report.
- — Failed steps marked retryable can be retried up to their attempt limit; validation failures cannot.
- — The optional fault injection is a labelled demo switch to show retry; it is off by default.
Limitations
- — No live research or third-party integrations. Competitor briefings use only the notes you supply.
- — Run state is kept in your browser tab and sent with each request; the server validates every transition but does not persist runs. A production system would store runs server-side with authenticated reviewers.
- — Without an AI key, analysis is rule-based pattern matching and is labelled as such.
- — Run history is stored in this browser's local storage (titles and statuses only).