Findings and severity
A finding pairs an expected behaviour with the observed evidence that contradicts it. Each one carries:
- Severity and risk category
- Check type — acceptance criterion or trajectory check
- Expected behaviour
- Observed behaviour
- Supporting transcript and tool evidence
- A diagnosis in plain language
Severity and exit codes
Section titled “Severity and exit codes”| Exit code | Meaning |
|---|---|
0 |
Run completed and no release-gate finding is present. |
100 |
High or critical findings are present and --no-fail-on-findings is not set. |
2 |
Command-line usage error. |
Use --no-fail-on-findings during exploration and demos. Leave it off in CI so high and
critical findings fail the build.
Four layers of result
Section titled “Four layers of result”These are different kinds of thing and the report never mixes them.
| Layer | Values |
|---|---|
| Control verdict | Pass · Fail · Inconclusive |
| Baseline comparison | Unchanged · Regressed · Resolved · New |
| Stability | Stable · Unstable |
| Release gate | PASS · REVIEW · BLOCK |
A control can Fail and still be Unchanged — a pre-existing failure the organisation already
accepted. A control can Pass on this candidate and still be Regressed in stability, if it now
passes on two attempts out of three where it used to pass on all three. The gate is a judgement
over all four, not a restatement of any one of them.