Rendered from docs/obligations/0076-a-generated-check-reads-its-severity-from-the-taxonomy.md in the Headwater corpus. Every document on this half of the site is typed by the taxonomy the descriptor names: corpus.json.

A generated check reads its severity from the taxonomy

Context

Spec 12 gives a check its severity and gives a control the decision to block, which makes a promotion a configuration change. A participation expectation declares severity: warn in the taxonomy, and the generated check reports what the declaration says.

Obligation

So an adopter moves a finding from warn to error by editing data, and no code changes. What is open is whether spec 12 admits it, because its own sentence reads as though only a control is data.

Discharge

For a generated rule the declaration is the check, so the engine reads this as consistent. A sentence in spec 12 is what settles whether that reading is the intended one.