Rendered from docs/obligations/0195-a-requirement-has-no-identity-so-a-descoped-requirement-has-no-form.md in the Headwater corpus. Every document on this half of the site is typed by the taxonomy the descriptor names: corpus.json.

A requirement has no identity, so a descoped requirement has no form

Context

A requirement is descoped, deferred, out of scope, or not met at release. Each of those is a state of one line under a heading, and never an edge between two documents. The product tradition's equivalent of a registered deviation therefore has a different shape from the compliance tradition's.

The brd-prd entry records this as its fifth finding, at line 171. OB-BP-3 of that entry is unverifiable for the same reason. The descoping that the tradition does every week is invisible to the corpus.

Obligation

This is the sub-document identity gap of HW-OBL-0036 seen from the state side rather than the citation side. A requirement has no identity, so it has no state, and no lifecycle regime can reach it.

The gap of HW-OBL-0187 is not this gap. That one wants an edge between two documents, and this one wants a state on a line. A ruling that supplies the edge leaves this record open.

Discharge

This record discharges when a state below the grain of a document has a form. It discharges the other way when a descoped requirement becomes a document of its own. A ruling on sub-document identity that reaches only citation discharges nothing here, because a citation names a thing and a state changes one.