Propose collections built from mounted configuration fragments

This commit is contained in:
2026-10-14 02:24:50 +00:00
parent c7d1b0dca7
commit c7490b783b
3 changed files with 447 additions and 7 deletions

View File

@@ -489,9 +489,13 @@ dependencies instead.
develops a concrete configuration standard for the existing composition rules.
[Proposal 2: identified records](configuration-collections-identified-records.md)
uses an opt-in upstream extension for identity-based record composition and
inheritance. Both retain main-owned specification versioning; broader source
and version changes can be evaluated in a later proposal 3. These are proposals
for comparison; this decision remains open.
inheritance. [Proposal 3: mounted fragments](configuration-collections-mounted-fragments.md)
uses explicit upstream source placement and collection-local mapping keys,
with one installed definition per prompt and an optional flat version field.
All three retain main-owned specification versioning; independent collection
checks remain a separate upstream question. These are proposals for comparison;
this decision remains open. Proposal 3 deliberately revises the version-selection
and listing assumptions elsewhere in this roadmap if that alternative is adopted.
**Desired capability:** describe collection namespace and release version in
configuration and expose an API through which downstream applications can list