Operations / operator guide
In developmentOperate the records, not the transcript
The current Millrace operator surface is a documented CLI for inspecting durable state, following runs, managing waits, and applying replay-safe interventions.
Page state reviewed 2026-08-15. The page does not expand the release evidence.
Read first
The tagged getting-started guide is the authoritative operator reference for the current release. It documents workspace checks, package verification, plan admission, queue status, run inspection, trace inspection, waits, interventions, and doctor output.
The operating model
Status, runs, traces, waits, interventions, and doctor are read-only projections of durable state. Runner output is evidence that the kernel evaluates; it is not a direct state mutation channel. A current adapter error or refused result should be inspected through the bounded run projection and, where appropriate, its redacted rejected-evidence view.
Restart and cancellation
The daemon lifecycle guide explains restart classification, lock ownership, orderly signal shutdown, and orphan-risk reporting. Runner-session cancellation is coordinator-owned and durable; shell, terminal, and tmux state are not lifecycle authority.
Scope of this page
This page documents the current source-backed operator boundary. It does not claim a hosted dashboard, Millrace OS interface, automatic repair, or a public launch workflow beyond the qualified release evidence.