Rendered from docs/obligations/0151-the-glossary-s-package-entry-omits-conformance-and-still-lists-plugins-which-367-dropped.md in the Headwater corpus. Every document on this half of the site is typed by the taxonomy the descriptor names: corpus.json.

The glossary's Package entry omits conformance and still lists plugins, which #367 dropped

Context

This surfaced while verifying #367, the correction to spec 7's manifest example. The glossary defines Package in one line, at docs/spec/glossary.md:690, listing the parts a published package carries. No rule reads that line the way reachable or required_kind read the manifest itself, so the entry can drift without failing a check.

Obligation

The entry omits conformance, a contents key that has named the rule set and levels a package ships since well before #367. It still names plugins, which #367 removed from the canonical manifest example in spec 7. No citation in the corpus commits to a manifest key by that name. The only other appearance of plugins is spec 12's unrelated check-plugin architecture, DocumentCheck and WASM hosting. That architecture never ties itself to spec 7 or to contents.

A correct entry lists exactly six contents keys: taxonomy, conformance, bundles, migrations, doctrine, and templates. It also covers the top-level profiles and interview keys, if the entry means to name those too.

Discharge

This closes when the Package entry in docs/spec/glossary.md names the six contents keys spec 7's corrected example carries. The wording should stay consistent with spec 7's own account of a package. The fix touches only that one glossary line, not spec 7 itself, spec 12's check-plugin architecture, or the manifest schema.

This record is discharged. #1487 rewrote the Taxonomy package entry in docs/spec/glossary.md. It names seven contents keys rather than six. The seventh, assemblies, joined spec 7's example after this record was written. The seven are taxonomy, conformance, bundles, assemblies, migrations, doctrine and templates. It names the top-level profiles and interview keys too, and it does not name plugins. The list is the one that spec 7's manifest example declares, and required_kind in engine/crates/resolve/src/package.rs reads the same seven keys.