Evidence should show the runtime making decisions

The claim boundary

The public claim is narrow: Millrace is a local runtime for compiling and executing governed workflow graphs with durable state, bounded transitions, and inspectable evidence. The current site does not claim arbitrary autonomous work, universal reliability, or a qualified non-coding workflow without a reproducible receipt.

What counts as proof

The runtime architecture documentation describes the evidence chain:

• a workflow package declares stages, routes, terminal actions, assets, and runner bindings;
• the compiler validates that decision structure and produces an authority fingerprint;
• the kernel applies explicit transition inputs against durable state;
• SQLite and content-addressed storage retain the records needed for restart and inspection; and
• status, runs, traces, waits, interventions, and doctor projections expose bounded operating evidence.

These are runtime properties documented in the source release. A page about them is not a substitute for a clean-install or behavior qualification receipt.

Historical record

Historical evidence: the graph-engineering provenance audit records dated source and release events from January through April 2026, including the April 21 compiled graph sidecar, April 23 graph-authority cutover, and April 24 public release receipt. Treat those dates as a record of project history, not as a current benchmark.

Read the current source repository and the tagged v0.22.2 documentation together. The source says what was released; qualification evidence says what was actually verified.