Clarify native imported step ordering

This commit is contained in:
2026-11-18 00:31:11 +00:00
parent 5e269f9760
commit 1febd2edfa
2 changed files with 12 additions and 2 deletions

View File

@@ -169,7 +169,13 @@ pipelines:
Pipeline names are siblings within `pipelines`; nested mappings such as named Pipeline names are siblings within `pipelines`; nested mappings such as named
artifact lanes also have their own sibling namespace. Distinct imported step IDs artifact lanes also have their own sibling namespace. Distinct imported step IDs
combine in source order; duplicate peer IDs conflict. Across an overlay or combine in ConfigKit's dependency-ready assembly order, not necessarily import
declaration or acquisition order; duplicate peer IDs conflict. Ready contributions
are selected by their stable source keys. See the pinned
[import assembly contract](https://forge.maximumdirect.net/base-layer/configkit/src/commit/c1c7e87f2cdf77a0cbf3327831ac05578e756b9e/docs/config.md#explicit-imports)
for full ordering semantics. In the complete example, the imported describe-session
step precedes the importing body's extract-events step because an imported
dependency is assembled before its importer. Across an overlay or
inheritance, upsert replaces a matching step as a complete record in place and inheritance, upsert replaces a matching step as a complete record in place and
appends new IDs. It does not merge individual fields of a matching step. An appends new IDs. It does not merge individual fields of a matching step. An
identified record can itself use native `extends`. Authors may select `replace` identified record can itself use native `extends`. Authors may select `replace`

View File

@@ -271,7 +271,11 @@ a documentation snapshot or changing runtime behavior to fit the prose.
### Finding CK-2 — Describe Dependency-Ready Step Assembly Order ### Finding CK-2 — Describe Dependency-Ready Step Assembly Order
Priority: P3. Category: documentation accuracy. Status: open. Priority: P3. Category: documentation accuracy. Status: complete.
Completed 2026-11-18: replaced the source-order claim with native dependency-ready
assembly, linked the pinned contract, and explained the complete example's ordering.
Verified against the pinned scheduler contract and unchanged example assertions.
Evidence: `docs/config.md:167–170` says distinct imported step IDs combine Evidence: `docs/config.md:167–170` says distinct imported step IDs combine
"in source order." ConfigKit distinguishes acquisition/import declaration order "in source order." ConfigKit distinguishes acquisition/import declaration order