Rendered from docs/obligations/0070-one-of-the-four-warrant-values-has-no-instance-in-this-corpus.md in the Headwater corpus. Every document on this half of the site is typed by the taxonomy the descriptor names: corpus.json.

One of the four warrant values has no instance in this corpus

Context

Every authored document here is accepted, because a human merged each one. regenerated has an instance now. docs/spec/README.md is the generated index of the specification shelf. The census reads that warrant off the marker rather than out of a declaration, and that file carries the marker on its first line.

Obligation

Nothing is transcribed, because no external system of record feeds this repository. asserted has instances of its own. headwater taxonomy audit reports nine documents under that warrant on 2026-08-15: three probes, four obligation records, 15 — The recorder contract and HW-DR-0024. A figure here is a figure that only a person re-derives, and the verb that produces it is named for that reason. Four engine rules turn on the value, and this corpus exercises three of them.

Discharge

The transcribed branch runs over corpus content, and not over the census fixture tree alone. It waits on an importer, which does not feed this repository. The verification block of headwater check states that each observed or suspect state is transcribed from .headwater/observations.yml (#937). That statement is not an instance, because the snapshot is not a document of the corpus and so carries no warrant. What the asserted instances found is a second question, and HW-OBL-0126 holds it rather than this record.