Long-running implementation with explicit review and recovery.
Planning, execution, checking, repair, and closure remain workflow data rather than hidden agent-loop control flow.
Open-source graph engineering
Published · qualification pendingCompile agentic work into governed execution.
Millrace turns workflow configuration into an authority-bearing execution graph, then carries work through durable transitions, retries, approvals, and closure evidence.
00
00 — Demo
In developmentOne-command demo
The packaged one-command demonstration is not released. The current path is the documented core workflow: initialize a workspace, admit a compiled plan, enqueue work, and inspect its durable run evidence.
See exact status and evidence0.22.2 release-line runtime receipt2026-08-15
- Runtime
- millrace 0.22.2
- Plan
- Simple Loop
- Queue
- Ready
- Ready
- 1
Reproduced from local canonical 0.22.2 release-line wheels. Published artifact identities are recorded separately in the receipt.
Inspect JSON receiptDocumented path
- Initialize a workspace and validate its durable state.
- Import a workflow package and admit one compiled plan.
- Enqueue through a declared route, then inspect status, trace, waits, and closure.
01
01 — Compile
Configuration becomes selected authority.
The compiler resolves graph nodes, routes, contracts, runner bindings, terminal actions, and pinned assets before a plan can be admitted.
Compiled planselected authority
- 01
- validated graph
- 02
- selected assets
- 03
- authority fingerprint
02
02 — Run
Harnesses execute; Millrace governs progression.
Stage runners perform bounded work within selected contracts. Millrace owns claims, legal transitions, lineage, and the durable route to the next state.
Active runselected authority
- 01
- claimed work item
- 02
- selected stage contract
- 03
- next legal transition
03
03 — Recover
Interruption does not erase operational state.
Retries, waits, approvals, cancellations, refusals, and blocked outcomes remain explicit so an operator can understand and act without reconstructing an agent transcript.
Recovery evidenceselected authority
- 01
- durable wait
- 02
- bounded rejection
- 03
- operator intervention
04
04 — Inspect
The graph leaves evidence, not just output.
Status, traces, receipts, artifacts, lineage, and terminal closure expose how work progressed and which authority accepted each result.
Run recordselected authority
- 01
- event sequence
- 02
- artifact lineage
- 03
- terminal receipt
05
05 — Extend
Add workflows and providers without weakening the kernel.
Workflow packages, runner adapters, and ecosystem tools integrate through declared contracts. Optional capability stays outside core authority until explicitly selected.
Extension boundaryselected authority
- 01
- package manifest
- 02
- provider contract
- 03
- capability grant
Use cases
One runtime, workflow-defined domains.
Millrace does not hard-code software delivery semantics into the kernel. A selected workflow package defines the graph, contracts, routes, assets, and recovery behavior for its domain.
Bring a different graph without forking the runtime.
Package domain-specific stages and inputs, then admit the resulting plan through the same compiler and durable runtime boundary.
Ecosystem
Separate products. Explicit ownership.
Each component owns a bounded part of the system and carries its own release state. They are not presented as one monolithic process.
Millrace Corecompiler and durable runtimePublished · qualify install
Millrace Plusofficial workflows and assets0.22.2 published
Millforgemodel-agnostic stage harnesses0.1.0 published
Millrace OSoperational API and interfaceIn development
Millrace Authorworkflow authoringPlanned
Millerassistant and operator clientPlanned
Install
Start from the qualified core path.
The exact public bundle, platform matrix, and runnable demonstration are controlled by the frozen launch manifest. This site will not guess them.
Core runtimeAvailable
One-command demoIn development
Millrace OS interfaceIn development
FAQ
Boundaries, stated plainly.
Is Millrace an agent harness?
No. Harnesses execute bounded stage work. Millrace compiles and governs the graph that decides what may run, what evidence is accepted, and which transition is legal next.
Is it a DAG library?
It can express graph-shaped work, but its focus is durable operational authority: claims, retries, waits, approvals, lineage, recovery, and terminal closure.
Does it require one model provider?
No provider is ambient. Runners and their capabilities are selected through explicit configuration and plan authority.
Is the one-command demo available?
Not yet. The site labels that surface In development and directs operators to the currently documented core workflow instead.
Where does state live?
An initialized workspace keeps durable runtime state and content-addressed artifacts locally. External runners receive only the material selected for their work.
What is the license?
Millrace Core is open source under Apache-2.0. Ecosystem repositories and third-party assets retain their own published notices.