Rendered from docs/obligations/0048-a-mapping-key-holds-a-dot-and-no-address-reaches.md in the Headwater corpus. Every document on this half of the site is typed by the taxonomy the descriptor names: corpus.json.

A mapping key holds a dot, and no address reaches it

Context

The worked example keys facet_values with a facet and one of its values, joined by a dot, as status.current. The sublanguage rules that a declared key with a dot makes an address ambiguous, and that the meta-schema refuses to declare one. Both clauses belong to spec 2.

Obligation

Either the key becomes two levels of mapping, or the specification states that some declarations are outside the reach of an overlay.

Discharge

engine/crates/meta/meta-schema.yml takes the reading that no overlay reaches inside facet_values, and it marks the position. Nothing else can settle it, because the choice is between two shapes and both parse.