Rendered from docs/obligations/0069-a-suppressed-finding-leaves-its-obligation-verified-and-spec-4.md in the Headwater corpus. Every document on this half of the site is typed by the taxonomy the descriptor names: corpus.json.

A suppressed finding leaves its obligation verified, and spec 4 does not say so

Context

A suppression runs after the runner stamps each finding with the obligation that its control discharges, so the inventory holds findings that name obligations. Spec 4 does not say what an obligation with two accepted deviations against it is.

Obligation

What is open is whether spec 4 admits the engine's reading. A second question is whether the register needs a rate rather than a count.

Discharge

The engine rules that it stays verified. A disposition is about whether a control discharges the invariant, and not about whether the corpus conforms today. A suppression is one author's judgment about one finding, and it removes no control. So the register prints the escaped count beside the obligation rather than moving the disposition.