Package-level declarations
Types
The result of one calibration run: both files as canonical JSON text.
One ranked candidate with the facts the weights act on, and the scenario's label for it. probe is a differing probe that reads the candidate's path, dimensionProbe one that only shares its dimension.
The shipped ranker against the one that classes probe and rule evidence by the observed failure, with the dimension prior beside them, on the same scenarios and the same template bootstrap as Analysis.
Typed reads over a JsonObject; scalars may be strings (YAML failsafe) or JSON numbers.
The inputs of a run: the capsule pairs with probes (Inputs.probed, the fit and the primary evaluation) and the first attribute-only pairs (Inputs.original, for the before numbers). Inputs.results reads <id>.json of data/results; with it the evaluation also scores the ranker conditioned on the observed failure (see EvidenceEval).
The dev scenarios and their capsules. Test ids are refused here unless the lab was built with Unsealed, so no fit or evaluation path can reach a sealed scenario before the unseal.
What the real pipeline produced for one dev scenario: the changed attributes, the probes that differ and the rules that matched (ids), and the ranked candidates.
One solved case directory: its id and the text of certificate.json, null when unreadable.
1-based rank of the cause in an order, null when the order does not hold it.
The dev drift solve certificates scored against the injected causes. One class block per scenario class and all, with Wilson intervals; see bench/README.md.
SplitMix64 on Long arithmetic, so every target draws the same sequence for a seed.
A hand-maintained scenario template. variants are rows of placeholder values (a seeded shuffle picks instances of them), draw placeholders are drawn independently per instance.
Triage scoring; a separate category that never enters the environment tables.
Builds triage/triage.json from triage/items.yml and the bodies under fixtures/triage.
One labelled issue body. facts are key=value (or key=value@passing) strings, claims the claim ids the claim check should raise and correction what a maintainer would answer. source is fixture; a corpus item would carry its own body.
One move of a migration scenario. A break item takes the passing arm's capsule and moves its cause attribute to the failing arm's value, so the measured red arm is the truth. A control item takes the failing arm's capsule and moves to the passing value: the green arm passed every trial, so nothing breaks. downgrade is true when the target is older than the capsule.