05 /Pipeline
Pipeline explorer
Runs the real state machine client-side against a committed synthetic brief. Approval gates cannot be skipped; retry is only possible from failed or cancelled — exactly the rules the engine enforces server-side in a real deployment.
Fixture mode, no live providers. Every script, storyboard, and asset here is a deterministic, committed fixture — no LLM call, no render worker, no API keys. Assets are synthetic placeholders (CC0, described in
fixtures/assets.json). The interactive pipeline below runs the real engine in your browser, with zero network calls. Runnable harness: benchmarks/vionto.01 /Live
Step the pipeline yourself
A 30-second teaser announcing a new product launch, upbeat and modern.
Queued job-B-01-0
Script→Storyboard→Asset plan→Render→Done
02 /Try this
Three things worth clicking through
Start, then Approve. The asset plan fails schema validation on the first attempt — watch it land in failed, then hit Retry to see the regenerated plan pass and the run continue.
Start, Approve, Approve. The render stage fails once (a simulated transient encode error), then Retry succeeds without regenerating anything upstream.
Start, then Reject. The run ends at cancelled — a legitimate stop, not a failure, and nothing forces you to retry it.