The runtime is held to a written standard of its own, laid out in docs/quality-report.md and docs/2026-11-12-plan-quality.md.
For each part of the runtime that has been through it, three steps are done. The part’s states, events and waits are written down from the code. Each decision it makes is made visible as an event. Then an explorer drives it through every ordering of its events, with faults injected, and checks each against the written table. A combination with no entry in the table fails. An ordering that breaks its row is reported and never fixed in the same change.
%% The three steps each part of the runtime goes through
flowchart TB
table["1 Write down states,<br/>events and waits<br/>from the code"] --> visible["2 Make each decision<br/>visible as an event"]
visible --> explorer["3 An explorer drives every ordering<br/>of events, with faults injected"]
explorer --> check{"Matches the<br/>written table?"}
check -- "yes" --> done["Part passes"]
check -- "no entry, or breaks its row" --> fail["Reported, not fixed<br/>in the same change"]
Other checks run beside that:
- Mutation testing breaks the code in small ways, one at a time, and checks that a test fails for each break. The first full sweep is the number above. Four reports record the triage of its survivors (
docs/2026-11-12-report-mutation-triage-runtime.md and the three of 15 November).
- The race detector runs under the Go suite on every pull request.
- Stress and soak runs look for wrong answers: lost messages, two turns of one actor committing, a parked actor waking.
arbor soak drives scripted conversations through a running node.
It is not finished. Only the wake path has been through all three steps, by the quality report. Held calls and reading while writing are partly done: held calls have the written table and their fixes have tests, but their decisions are not yet visible and no explorer has run; reading while writing has the table and visible decisions, and no explorer yet. Ending a session has not been begun. The sweep covered ten files, not the whole runtime. Benchmarks shows what the load and stress tests found, and History lists every defect, with the open ones marked.