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