Accept composed ConfigKit artifact definitions

This commit is contained in:
2026-10-04 13:10:53 +00:00
parent c4abdc19df
commit 428f435734
8 changed files with 226 additions and 95 deletions

View File

@@ -169,9 +169,10 @@ another `configkit` control section.
Base merging is additive. A map may be extended by multiple files when every
leaf is distinct, but a scalar, list, or map/list/scalar kind cannot be claimed
more than once, even when the repeated values are identical. Conflict errors
name the full field path and every source that claimed it. Narratio additionally
rejects an artifact or artifact-family key declared by more than one base file,
even when those files contribute disjoint children.
name the full field path and every source that claimed it. These rules apply at
every map path, including artifact and artifact-family entries, so distinct
fields of one entry can compose across imports. Narratio validates the resulting
effective entry using its ordinary domain rules.
Overlay names are case-sensitive and use ConfigKit's safe fixed-path naming
rules. Only the selected overlay is opened; a malformed unselected overlay does

View File

@@ -20,9 +20,9 @@ pipeline-loading boundary implemented by `internal/config`.
4. The definition validator performs read-only checks that require only the
pipeline file. Checks requiring canonical-party family expansion remain at
the existing explicit pipeline/campaign resolution boundary.
5. Narratio inspects public ConfigKit metadata to reject artifact and family keys
declared by multiple base files, adapts source ownership records, attaches
runtime-only state, and computes the normalized effective digest.
5. Narratio retains public ConfigKit metadata for source ownership, attaches
runtime-only state, and computes the normalized effective digest. Artifact
and family validation applies to the composed effective entries.
This ordering preserves monolithic configuration behavior. Moving a field to
an imported fragment changes its source ownership, not its path base, default,

View File

@@ -38,25 +38,25 @@ The [configuration reference](../config.md) owns Narratio's current public
semantics; [configuration internals](../internal/configuration.md) describe
loading and inspection.
- Pipeline loading uses ConfigKit with explicit additive imports and one
- Pipeline loading uses ConfigKit v0.5.0 with explicit additive imports and one
selected overlay, typed defaults, recorded resolution, and domain validation.
- Campaign, session, and canonical-party inputs use separate single-source
loads. Secret-directory bootstrap remains an explicit invocation operation.
- Fields with root-relative pipeline path semantics retain that base when their
declarations move into imports. For example, enabled Notarius configuration
and working-directory paths resolve from the root pipeline directory.
- Narratio adds a declaration-ownership check: each artifact or artifact-family
key may be declared by only one base file. Overlay modifications are allowed.
- Distinct fields of one artifact or artifact-family entry can compose across
base files under ConfigKit's structural rules. Narratio validates the resulting
effective entry, and the selected overlay may replace or remove those values.
- Source inspection and artifact catalogs consume retained ConfigKit metadata.
Effective show, diff, and digest projections describe the resolved domain
configuration rather than source layout.
The review selected v0.5.0 through a temporary module file and ran Narratio's
existing test suite successfully. An additional probe exposed an integration
gap: a child artifact inheriting from a parent in another imported file is
rejected as declared by multiple base files. The same definitions in one file
load successfully. The check currently counts inherited history contributions
as if they were direct declarations.
The released v0.5.0 module is now selected directly, and its attribution points
to the reviewed commit. Cross-file artifact and family inheritance and disjoint
entry composition now pass through Narratio's effective configuration checks.
The remaining integration work verifies native provenance, explicit presence,
safe projections, and the assembled inspection workflow described below.
## Targeted End State

View File

@@ -100,7 +100,7 @@ Complete when the released dependency and notices agree and current focused
tests pass. The cross-file inheritance defect is addressed in the next stage;
this stage does not claim that new inheritance behavior is fully integrated.
## Stage 2: Remove source-authoring acceptance gates
## Stage 2: Remove source-authoring acceptance gates [x]
Purpose: accept structurally composed configuration from ConfigKit and reject
only invalid effective Narratio domain configuration.