Rendered from docs/obligations/0192-assumptions-that-a-library-entry-takes-where-the-specification-does-not-speak.md in the Headwater corpus. Every document on this half of the site is typed by the taxonomy the descriptor names: corpus.json.

Assumptions that a library entry takes where the specification does not speak

Context

Tier 3 of the library index's finding rule asks an entry to record the assumptions that the specification does not cover. It asks for them grouped under one item. This record is that item. Each entry adds its group to the list below, and the argued form stays in the entry's own doctrine.

standards-spec, at line 166 of its doctrine. Neither shelf declares a layout, because a layout has no form for a subdirectory per component and the tradition's files are <component>/functional.md. volatility: stable on spec_layer is the assumption that the design-spec entry recorded for doc_type. Whether an entry may declare an identifier scheme with no namespace has two live patterns in this library and no ruling. The two expectation windows are judgments rather than measurements.

brd-prd, at line 175 of its doctrine. The shelf declares no layout, because a layout has no form for a subdirectory per initiative and the tradition's files are <initiative>/brd.md. volatility: stable on requirement_tier is the same assumption again. Both kinds are named by acronym, which no other kind in this library is. brd carries two traditions' names for one slot, and no facet distinguishes them, because a facet that no check reads fails the relevance canon. The 90-day window is a judgment rather than a measurement. The identifier schemes carry no namespace, which is the same open pattern.

Obligation

Six questions stand behind the two groups, and each one is a place where the meta-schema has to speak eventually.

A shelf layout has no form for one subdirectory per component. Nothing states when volatility: stable is a claim that an entry may make about a facet it declares. The library runs two identifier-scheme patterns, one with a namespace and one without, and no ruling picks between them. An expectation window is a number that an entry invents, and no document says what evidence sets one. Nothing states whether a kind may be named by an acronym where no other kind in the library is. Nothing states how one slot carries two traditions' names, because a facet that no check reads fails the relevance canon.

Discharge

This record discharges when each of the six has an answer in the specification. It discharges the other way when the library index states that an entry takes them as readings. A partial answer discharges nothing, because the tier rule makes this one item by timing rather than by subject.