Extend collection inheritance architecture to identified sequences

This commit is contained in:
2026-10-23 01:42:32 +00:00
parent 3298eb916c
commit 6ec23b2de1
3 changed files with 46 additions and 9 deletions

View File

@@ -260,12 +260,22 @@ Consistent combination semantics do not require identical acquisition or lifetim
behavior from every source kind.
Built-in sibling `extends` relationships resolve after source precedence in the
parser-independent document representation. Preserve their existing sibling
scopes and resolve enclosing relationships before nested destination-local
relationships. Mappings combine recursively; sequences use the inheriting
collection's policy. Inheritance remains built-in and creates no acquired source.
parser-independent document representation. Preserve existing mapping-sibling
scopes and allow an identified sequence to provide a sibling scope for its
records. A record may inherit from one parent in that sequence, selected by
complete identity. The child supplies and keeps its own identity while inheriting
the parent's other settings. Parents remain ordinary records subject to normal
validation.
Use the shared dependency ordering and preserve assembled sequence order.
Resolve enclosing relationships before nested destination-local relationships.
Mappings combine recursively; sequences use the inheriting collection's policy.
Whole-record upsert replaces records during combination; explicit inheritance
uses the records that remain. Inheritance remains built-in and creates no
acquired source.
[ADR 0009](../adr/0009-sibling-inheritance.md) records the
continuing scope and ownership decisions, with sequence combination revised by
original scope and continuing ownership decisions, with sequence combination
and identified-sequence inheritance defined by
[ADR 0017](../adr/0017-collection-sequence-policy.md) and CLI ordering by
[ADR 0018](../adr/0018-cli-after-structural-resolution.md).