From 7afe6ba333a72a4740eda8ee2263322bb6a1c476 Mon Sep 17 00:00:00 2001 From: Eric Rakestraw Date: Thu, 19 Nov 2026 15:01:37 +0000 Subject: [PATCH] Record collection discovery integration finding --- docs/roadmap/remediation.md | 25 +++++++++++++++++++++++++ 1 file changed, 25 insertions(+) diff --git a/docs/roadmap/remediation.md b/docs/roadmap/remediation.md index 5f92039..e0b3c21 100644 --- a/docs/roadmap/remediation.md +++ b/docs/roadmap/remediation.md @@ -56,3 +56,28 @@ Add a `PATENTS` link at the already selected Go Text commit. Retain the verified local BSD text and existing `LICENSE` link. No separate local patent notice or change to the project license is needed under the adopted attribution format. + +## R4: Distinguish discovery peers from ordered framework layers (Stages 6–7) + +The [upgrade guide](../consumers/upgrading-promptkit.md) says a later source +selecting the same ID replaces the whole record. That holds for a later +framework underlay, not for two checkout entries selected by the same +discovery file. Scriptorium turns each resolved `promptkit_sources` selector +into one underlay. The entries discovered by the imports of that selector +are composed as peers; their filename, glob, or checkout order is not +override precedence. + +The built binary rejected two discovered checkout entries defining +`shared/fast` with `compose.conflict`. Selecting the very same entry files +as two ordered `promptkit_sources` items instead succeeded: the later +record's model was selected and `max_tokens`, absent from that record, did +not carry forward from the earlier one. This is the intended distinction, but +the migration wording can lead operators to put an intended override in +a discovery peer, which prevents the engine from loading. + +Qualify whole-record replacement in the upgrade guide and explain in the +[checkout discovery reference](../config.md#collection-checkout-discovery) +that same-ID conflicts within one discovery underlay fail. For an intentional +override, select a separate, later framework source using the existing +application selector list. No scanner, de-duplication, new namespace +restriction, or change to composition is needed.