What is shipped, what is moving, and what is deliberately out of scope.
Millrace is being expanded from a proven LAD-backed software workflow into a broader loop engineering framework. This roadmap keeps future-facing claims separated from shipped evidence.
The current public proof is workflow-specific.
The public evidence covers a governed software workflow family: Rust port creation, ongoing Rust parity maintenance, and associated receipts.
Queues, stage dispatch, runner boundaries, artifacts, status markers, recovery, and completion handling exist as the basis for governed loops.
The Python runtime and related codebase surfaces are available for inspection and local operation while the public site distinguishes evidence from roadmap.
Millrace OS
The command-center dashboard for daemons, queues, runs, blocked states, evidence, completion, readiness, and remote operation.
Custom graph maturity
Sharper validation for workflow graphs, stage contracts, terminal markers, deterministic transitions, recovery routes, and completion behavior.
Broader workflow support
Moving beyond the shipped LAD proof while keeping each new workflow bounded by explicit contracts and evidence expectations.
Scope control is part of the product.
Millrace is not trying to be a universal chat wrapper, a proof-free autonomy brand, or a dashboard that overrides runtime authority. It also will not claim arbitrary non-coding workflow automation until those workflows have their own specifications, contracts, runs, recovery behavior, and evidence.