Rendered from docs/obligations/0051-downstream-delivery-of-a-standards-corpus.md in the Headwater corpus. Every document on this half of the site is typed by the taxonomy the descriptor names: corpus.json.

Downstream delivery of a standards corpus

Context

Spec 7 shares a schema, doctrine prose and the publisher's obligations, and it shares no corpus content. So a publisher whose method includes standards documents reaches a consumer with a conformance rule, and never with a document. The same specification rules that a reference runs upward, and no resolver in spec 2 carries content down to meet it.

Obligation

The parts of a third arrangement exist already: an export profile, a committed pin at the consumer, and one anchor kind over that pin. Each edge into a changed item then takes a drift finding, exactly as Q19 rules for a requirements snapshot. No section composes those parts downward, and no entry in the register rules on the direction.

Discharge

Either one section states that arrangement, or corpus content never travels downward and a shared standard is always a package rule. Q9 holds the tier that would carry it, and it has no instance.