Fleet run
f-0042 · 8 Oct 2026, 09:14 UTC
$ kymograph fleet run --manifest corpus.yaml --store findings.sqlite --repeat --parallel 16 --include-remote
Keys (entry × scenario)
8
7 entries · 2 scenarios
Series complete
5
every identity decided
Undecided
1
budget reached, interval shown
Incomplete
1
non-results blocked a decision
Refused
1
not run, recorded as result
Runs
454 / 485
considered / scheduled · 3 retried
Series by entry and scenario
{{r.prov}}
{{r.transport}}
era: {{r.era}}
{{r.iso}}
egress not observed
{{r.runs}}
{{r.runsNote}}
{{r.stable}} stable
{{r.flaky}} flaky
{{r.absent}} absent
{{r.undec}} undecided
Runs that were not results
A cause the server can bring about keeps the run in the worst case. A run whose causes are all outside the server’s reach is not counted and is run again. How a run’s state is read back →
How to read a class
- stable
- present at ≥ 80 %, α = β = 0.05 — 14 runs with a hit
- flaky
- present, but not at a stable rate; rate and Wilson interval shown
- absent
- below 10 % at β = 0.01 — 44 runs (evidence) or 48 (sequential test)
- undecided
- budget spent, the data sits between the hypotheses — never new or gone in a comparison
A finding says “signal X fired at place Y”. It is a candidate for a person to look at, never a verdict on the server.