Document native configuration inheritance

This commit is contained in:
2026-10-04 15:25:48 +00:00
parent 39af6ef941
commit f1f71d8cdf
7 changed files with 75 additions and 13 deletions

View File

@@ -13,7 +13,8 @@ pipeline-loading boundary implemented by `internal/config`.
exact `default` selections use the base; named overlays use the fixed
`overlays/<name>.yml` convention.
2. ConfigKit parses the root and declared imports, additively merges base
sources, applies only the selected overlay, and strictly decodes the result.
sources, applies only the selected overlay, resolves native sibling
inheritance, and strictly decodes the result.
3. The definition resolver applies recorded entry-level and inherited defaults,
runs deterministic domain normalization, records derived publish destinations,
and resolves ordinary paths relative to the root pipeline file.
@@ -44,8 +45,10 @@ download retain that exact pipeline object and its private provenance. Removing
a temporary downloaded session file therefore cannot invalidate the resolved
pipeline or campaign context.
Campaign and session files use independent ConfigKit definitions with imports
and overlays disabled. Campaign files normally load directly from their source;
Campaign and session files use independent single-source ConfigKit definitions
with imports and selected overlays disabled; native sibling inheritance remains
available within each document. Canonical-party input follows the same
single-source rule. Campaign files normally load directly from their source;
session files are first read through the 8 MiB bounded-read boundary because the
application must reject unresolved template placeholders before passing an exact
byte snapshot to ConfigKit. Local and remotely downloaded session bytes then use
@@ -132,6 +135,15 @@ for core pipeline/session rules, external adapters, publish/storage, Notarius,
Scriptorium, and shared scalar/path checks. These are package-local ownership
boundaries rather than extension points or a general validation framework.
ConfigKit supplies composition, inheritance, presence, typed-secret, and
provenance mechanics; Narratio supplies the domain rules applied to the
effective decoded entries. There is no separate authoring-history acceptance
gate: contributors and declaration history remain inspection evidence, not an
additional validity condition.
The [configuration reference](../config.md#pipeline-imports-and-overlays)
documents sibling syntax, reserved-key migration, and the operator-visible
inspection behavior.
Validation is read-only, fails fast, and does not define which of several
independent invalid fields is reported first. Map-backed declarations are
nevertheless traversed deterministically. Reusable domain normalization is an