Expose sequence placement controls in the public API

This commit is contained in:
2026-10-16 19:23:43 +00:00
parent c19825620c
commit adef16ccdd
13 changed files with 573 additions and 55 deletions

View File

@@ -170,6 +170,13 @@ Tier precedence is explicit; traversal order within a tier establishes stable
reporting, not permission to override. The distinction and its rationale are
recorded in [ADR 0001](../adr/0001-separate-composition-and-overlay.md).
At definition-registered sequence paths, strict composition appends mapping
records with distinct present string identities and rejects duplicates.
Placement and registration are explicit source and definition controls; they do
not change precedence replacement. The [configuration contract](../config.md#strict-document-composition)
defines the behavior, and [ADR 0014](../adr/0014-sequence-placement-and-composition.md)
records the decision.
The main document and its imports form a strictly composed tier. Explicit
underlay groups compose strictly within each group, then combine recursively
from lowest to highest beneath the main tier. Source acquisition kind does not