eric/ConfigKit
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Document sequence composition for consumers

Browse Source
This commit is contained in:
Eric Rakestraw
2026-10-16 19:37:59 +00:00
parent 77c5d9482a
commit acddce8e2f
18 changed files with 300 additions and 39 deletions
Download Patch File Download Diff File Expand all files Collapse all files

20
docs/roadmap/sequence-composition.md
View File

@@ -1,8 +1,9 @@
# Sequence-Item Placement and Identity-Based Composition
Status: design decisions settled; not implemented. This roadmap owns the target
state and accepted behavior. The [implementation plan](implementation.md) owns
concrete API/syntax choices, execution order, validation, and progress.
Status: implemented. This roadmap records the target state and accepted behavior.
The [configuration contract](../config.md#strict-document-composition) defines
the current behavior, and the [implementation plan](implementation.md) records
delivery sequencing and validation.
## Goal and current baseline
@@ -11,13 +12,12 @@ files. Placement makes a source mapping one sequence item; identity-based strict
composition combines distinct items and rejects repeated identities. These are
complementary operations, with explicit consumer opt-in.
Current [input destinations](../config.md#input-destinations) place source
mappings beneath mapping-key paths. Imports support immediate-parent-relative
destinations. Current [strict composition](../config.md#strict-document-composition)
combines mappings recursively and rejects other overlaps, while
[precedence assembly](../config.md#layered-loading) and
[selected overlays](../config.md#selected-overlays) replace sequences wholesale.
Neither sequence-item placement nor sequence-composition registration exists today.
Sources can explicitly place mappings as sequence items at non-root destinations,
and definitions can register literal sequence paths with one literal string
identity field for duplicate-rejecting strict composition. Ordinary unregistered
sequences retain strict conflict behavior. [Precedence assembly](../config.md#layered-loading)
and [selected overlays](../config.md#selected-overlays) continue to replace
sequences wholesale. The canonical contract documents the exact rules and limits.
This roadmap covers a narrower feature than the
[identified record sequences candidate](future.md#1-identified-record-sequences).