Include message normalization in future provenance review
This commit is contained in:
@@ -49,6 +49,13 @@ field-level change history while preserving the origins needed to resolve
|
|||||||
relative resources such as `content_file`. Assess whether that inspection
|
relative resources such as `content_file`. Assess whether that inspection
|
||||||
benefit justifies changing the execution-owned normalization approach.
|
benefit justifies changing the execution-owned normalization approach.
|
||||||
|
|
||||||
|
Include message-role and cache-control normalization in this reevaluation.
|
||||||
|
Upstream support would need to preserve untouched field origins within nested
|
||||||
|
message lists as well as outer resource lists. PromptKit would continue owning
|
||||||
|
the normalization rules; ConfigKit would record their effects and provenance.
|
||||||
|
Consider moving these transformations only if it improves inspection consistency
|
||||||
|
and simplifies implementation without changing execution behavior.
|
||||||
|
|
||||||
Upstream support is the reconsideration trigger, not a dependency of the
|
Upstream support is the reconsideration trigger, not a dependency of the
|
||||||
current ConfigKit migration or a commitment to adopt the enhancement.
|
current ConfigKit migration or a commitment to adopt the enhancement.
|
||||||
|
|
||||||
|
|||||||
Reference in New Issue
Block a user