Distinguish mapping and record inheritance syntax

This commit is contained in:
2026-11-18 00:30:57 +00:00
parent fb58aef8c2
commit 5e269f9760
2 changed files with 11 additions and 4 deletions

View File

@@ -141,9 +141,12 @@ see [PromptKit Profiles](#promptkit-profiles).
## Sibling Inheritance
ConfigKit supports native `extends` composition in mappings and identified
sequence records. A directive
names exactly one immediate sibling in the same mapping; it is not a path or a
cross-scope lookup. Imports and the selected overlay are composed before
sequence records. In a mapping, `extends: production` selects the named immediate
sibling in that same mapping. In an identified sequence, the reference is an
identity mapping: for steps identified by `id`, `extends: {id: parent}` selects
a record in the same final sequence. Neither form is a path or cross-scope
lookup. See the pinned [native inheritance examples](https://forge.maximumdirect.net/base-layer/configkit/src/commit/c1c7e87f2cdf77a0cbf3327831ac05578e756b9e/docs/config.md#sibling-inheritance).
Imports and the selected overlay are composed before
inheritance and typed decoding. Explicit CLI assignments follow decoding and
inheritance, before Notarius resolution and validation; they cannot repair an
earlier structural or decoding error. Every definition, including a parent and definitions not

View File

@@ -236,7 +236,11 @@ required for either finding.
### Finding CK-1 — Distinguish Mapping And Record Inheritance Syntax
Priority: P3. Category: documentation accuracy. Status: open.
Priority: P3. Category: documentation accuracy. Status: complete.
Completed 2026-11-18: documented both reference forms and their lookup scopes,
linking to the pinned native examples. Checked against v1.2.0's contract and
existing inheritance coverage; no non-executable example was added.
Evidence: `docs/config.md:143–149` introduces both mapping and identified-record
inheritance, then says a directive names an immediate sibling in the same