Product surface / demo
In developmentThe demo is a release gate, not a promise
The one-command Millrace demonstration is still in development; this page separates the documented core workflow from the evidence required to publish a runnable demo.
Page state reviewed 2026-08-15. The page does not expand the release evidence.
Current state
The packaged millrace demo surface is not released or launch-qualified. There is no immutable demo package, fixture digest, expected artifact set, or clean qualification receipt in the current launch manifest. The site therefore does not present a fake terminal, a synthetic screenshot, or an unverified command as a call to action.
The current release evidence identifies millrace-ai version 0.22.2 from the v0.22.2 source tag. That proves the tagged source and package boundary; it does not prove a one-command demo journey.
What the current runtime documents
The v0.22.2 getting-started guide describes the real sequence: initialize a fresh workspace, import and enable an official workflow package, verify and admit a compiled plan, enqueue work, and inspect durable status and run evidence.
That is the evidence-backed core path. It is more deliberate than a demo command because the operator selects the workflow package, entrypoint, plan fingerprint, and runner configuration explicitly.
What must be true before this changes
Publishing a runnable demo requires an immutable command, a pinned fixture, expected output and artifact digests, clean-install receipts for each claimed platform, and a passing behavior qualification. Those records belong in the launch manifest before the page changes state.
Until then, the honest next action is to read the runtime documentation and inspect the source release.