Repository navigation
Glossary
Tom Barber edited this page Nov 6, 2026
·
6 revisions
Short definitions. Concepts-and-Vocabulary has longer explanations with examples. The web UI has a Glossary page too (/glossary), with a shorter list of the words the pages use.
| Term | Meaning |
|---|---|
| Backend | The part of Hairspring that runs a trial: sim, wasm or process. |
| Bundle | A small text file that records what is needed to replay one failing trial: seed, build, target, backend, parameters and path. process bundles also record the machine's environment. |
| Busy | A worker that holds a job lease that has not ended. |
| Candidate | A failure that no check has repeated yet: the lowest state of a finding, and the state of every failure found on a simulation target. It says nothing about whether the failure is real or fixed. |
| Chaos mode | A Hermit scheduling mode (chaos = true) that ends timeslices at random points and gives threads random priorities. |
| Claim | A sentence Hairspring generates from stored counts and checks, such as one beginning "Reproduced (confirmed): a property failed in seed ...". Only confirmed or verified findings get one. Never written from free text. |
| Colour theme | The web UI's Light, Dark or System setting (System follows your browser or operating system). Saved in your browser only. |
| Conditional branch | A CPU instruction that picks one of two paths, as at an if or the end of a loop. |
| Confirmation | Recorded checks that a failure repeats: same-seed reruns, bundle replay, and optionally a fixed-build control and Hermit's strict verify. Run with hairspring confirm, or, where the server was started with --max-confirmations, from the failure page with a run token. |
| Confirmation ladder | How the web UI shows a finding's state: Candidate, Rerun repeated, Confirmed, Verified, with Not reproducible and Control failed as ends. The server works it out from the stored checks. |
| Control | A second target running the fixed build, used to check that the fix is clean at the failing seed. |
| Control failed | A finding state: the reruns repeat the failure, but the fixed build (the control) still fails at that seed. An end of the ladder, not a rung. |
| Delta debugging | A shrinking method that removes parts of a failing input and keeps any smaller one that still fails the same way. |
| Deterministic | Same inputs, including the seed, give the same execution. |
| Doctor |
hairspring doctor: runs the same seed twice and reports the first divergence. With --process-backend, checks a machine's prerequisites for Hermit. |
| Events (guest) |
HAIRSPRING_EVENT {json} lines a guest SDK writes so Hairspring can read named properties. Defined by guest event protocol v1. |
| Finding | A recorded failure and its evidence. Its state (candidate, rerun_repeated, confirmed, verified, not_reproducible, control_failed) is derived from stored checks. |
| Guest | The program under test. Hairspring is the host. |
| Guest SDK | A library that lets a guest declare and report named properties. Available for C (and C++), Go, Rust, Python, Java and .NET. |
| Hermit | Meta's deterministic-execution tool for Linux x86-64, used by the process backend. Third-party; installed separately. |
| Hit | A trial in which a property failed. Reports say "hits", not "bugs found". |
| Idle | A worker that holds no lease and was heard from within one lease length. |
| Inconclusive | A trial that could not be judged, such as a timeout. Never a pass. |
| Infra | A trial that failed because of the host or Hermit, not the program. Listed apart; never a pass. |
| Interleaving | The order in which the instructions of different threads actually ran. |
| Lease | The time a worker may hold a job without contacting the server (two minutes by default). |
| MCP | Model Context Protocol. hairspring mcp lets AI agents start runs and read failures. |
| Needs attention | The Overview section that lists failed or errored runs among the latest 20 and the newest failures. It never says that anything is fine. |
| Not reproducible | A finding state: a rerun or the replay did not repeat the failure on the environment it was recorded in. An end of the ladder, not a rung. |
| Not seen recently | A worker that holds no lease and was last heard from longer ago than one lease length. |
| PMU | Performance monitoring unit: CPU hardware that counts events such as retired branches. Hermit needs it. |
| Preemption | The scheduler stopping a running thread to let another run. |
| Property | A rule the system must obey. Kinds: always, always_or_unreachable, sometimes, reachable, unreachable. |
| Rated trial | A trial that counts toward a rate: a pass or a violation, with usable events. |
| Replay | Running a bundle again to see whether the failure repeats. |
| Rerun repeated | A finding state: the same-seed reruns repeat the failure, but no replay of its bundle has yet. |
| Retired | Of an instruction: actually completed by the CPU, not started speculatively and discarded. |
| Run | One job that tests a target with many trials. A search or a sweep. |
| Schedule | The order in which things happened in a trial. Compared by a schedule fingerprint on the process backend. |
| Scheduler | What decides which thread runs next and for how long. Under Hermit, a seeded one. |
| Search | The default run mode. Stops at the first confirmed failure. Gives counts, not a rate. |
| Seed | A number that drives every choice in a trial. Same seed, same choices. |
| Seed explorer | The web UI page for one run's trials: a strip with one mark per judged trial and a filterable table. Its rows open trial pages. |
| Sensitivity line | A report line showing the rate if every unrated trial had been a hit. |
| Shrinking | Reducing a failing trace to a minimal one that still fails the same way. |
| Skid | A performance-counter interrupt landing later than requested. An overshoot makes a schedule unreliable; with skid_margin set, Hermit panics and the trial is infra. |
| Strict verify | A confirmation check made with Hermit's verify mode, which runs the program twice and compares the two runs. Run with hairspring confirm --strict-verify. |
| Sweep | A run that runs its whole trial budget and stores every trial, so it can state a rate. |
| Target | A named thing to test, with its kind and budget. |
| Thread | One line of execution inside a program. |
| Timeslice | How long a thread runs before it is preempted. Under Hermit, counted in retired conditional branches. |
| Trial | One attempt to make a target fail: one seed (process, wasm) or one exploration round (sim). |
| Trusted / Untrusted | Whether an administrator has marked a worker's data as able to back a claim. Untrusted data is shown, labelled as unverified. |
| Unusable | A trial whose reported events were lost, cut or contradictory. Never a pass. |
| Verdict | How a trial ended: pass, violation, inconclusive, unusable or infra. |
| Verified | The highest finding state: confirmed, and Hermit's strict verify agrees. It still does not say the failure is fixed. |
| Virtual time | The clock a program sees under Hermit, controlled by Hermit rather than the real clock. |
| Wilson interval | The 95% interval Hairspring reports around a rate with at least one hit. |
| Witness | Up to four integers the program recorded with an evaluation of a property, kept from the first true and the first false evaluation. See Guest-SDKs-by-Language. |
| Worker | A process that takes queued jobs and runs them. hairspring serve runs one inside the server; hairspring worker registers a remote one. Shown on the Workers page with its state and trust. |
Understand
- What-is-Hairspring
- Concepts-and-Vocabulary
- How-Deterministic-Simulation-Works
- Sweeps-and-Confirmation
- Limits-and-Honesty
Use
- Installation
- Your-First-Run
- Running-Your-Own-Software
- Guest-SDKs-by-Language
- Examples-Overview
- Hairspring-in-CI
- Operate-a-Server
- Upgrading-and-Versions
- Troubleshooting
Reference