Accept composed ConfigKit artifact definitions
This commit is contained in:
@@ -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
|
||||
|
||||
|
||||
@@ -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.
|
||||
|
||||
Reference in New Issue
Block a user