diff --git a/docs/roadmap/future.md b/docs/roadmap/future.md
index 7b964e1..45f5c4e 100644
--- a/docs/roadmap/future.md
+++ b/docs/roadmap/future.md
@@ -49,10 +49,14 @@ 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.
 
-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.
+Include normalization of roles and cache-control values in configured messages
+in this reevaluation. This could make inspection reflect the values used for
+execution and reduce separate normalization paths. 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. Caller-appended messages
+would still need request-time normalization because they do not pass through
+ConfigKit.
 Consider moving these transformations only if it improves inspection consistency
 and simplifies implementation without changing execution behavior.