From 1febd2edfadffc25cc4a9d625308bdd7e1823070 Mon Sep 17 00:00:00 2001 From: Eric Rakestraw Date: Wed, 18 Nov 2026 00:31:11 +0000 Subject: [PATCH] Clarify native imported step ordering --- docs/config.md | 8 +++++++- docs/roadmap/remediation.md | 6 +++++- 2 files changed, 12 insertions(+), 2 deletions(-) diff --git a/docs/config.md b/docs/config.md index f7a333d1..5f9dfc6e 100644 --- a/docs/config.md +++ b/docs/config.md @@ -169,7 +169,13 @@ pipelines: Pipeline names are siblings within `pipelines`; nested mappings such as named 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 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` diff --git a/docs/roadmap/remediation.md b/docs/roadmap/remediation.md index a3cb3b5b..39ca3447 100644 --- a/docs/roadmap/remediation.md +++ b/docs/roadmap/remediation.md @@ -271,7 +271,11 @@ a documentation snapshot or changing runtime behavior to fit the prose. ### 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 "in source order." ConfigKit distinguishes acquisition/import declaration order