Record future provenance-preserving normalization support
This commit is contained in:
@@ -38,8 +38,19 @@ consumers.
|
|||||||
|
|
||||||
## Ideas
|
## Ideas
|
||||||
|
|
||||||
No ideas are currently awaiting selection. Active feature work belongs in its
|
### Field-Level Normalization With Preserved List Provenance
|
||||||
focused roadmap rather than this catalog.
|
|
||||||
|
Reevaluate normalizing resource fields directly in ConfigKit's effective
|
||||||
|
configuration after upstream ConfigKit supports recording changes within a
|
||||||
|
list without replacing the source attribution of unchanged fields.
|
||||||
|
|
||||||
|
This could let configuration inspection show PromptKit-normalized values and
|
||||||
|
field-level change history while preserving the origins needed to resolve
|
||||||
|
relative resources such as `content_file`. Assess whether that inspection
|
||||||
|
benefit justifies changing the execution-owned normalization approach.
|
||||||
|
|
||||||
|
Upstream support is the reconsideration trigger, not a dependency of the
|
||||||
|
current ConfigKit migration or a commitment to adopt the enhancement.
|
||||||
|
|
||||||
## Entry Format
|
## Entry Format
|
||||||
|
|
||||||
|
|||||||
Reference in New Issue
Block a user