diff --git a/ai/logs/2026-04-10.md b/ai/logs/2026-04-10.md
index 0f9222c..a03bc68 100644
--- a/ai/logs/2026-04-10.md
+++ b/ai/logs/2026-04-10.md
@@ -12,4 +12,7 @@
 - In standups, format Jira references as `ID - Title` or `ID Title`, not `ID, Title`.
 - Jeff clarified that `PDIAP-15838` is the next story to work on and `PDIAP-15836` comes later.
 - Clarification: the feature-flag and rollout planning feedback applies to the broader UIKit-removal spike, not only to the dismissal sequencing changes; the sequencing work should fit into that same consumer rollout plan.
+- Current priority is to create a process-oriented document that explains the rollout plan Jeff described for the UIKit-removal spike, with the goal of sharing it for feedback.
+- Clarification: the document should frame the work as a more deliberate migration phase toward the SwiftUI-only path, not as a correction to a prior failed attempt. The dismissal sequencing work is only one part of that broader migration plan.
+- The document should clearly explain that the rollout uses a dual-path pattern to switch between the `UIHostingController` path and the SwiftUI-only path during migration.
 - Jeff said the remaining spike deliverable is a clear consumer-facing rollout plan covering risky entry points like FTTransfer, consumer communication, XQ1 validation, a 30-day production period with no reported bugs, and a follow-up release to remove the feature flag and old code; he suggested sending that process-oriented document to Quy for feedback when ready.
diff --git a/ai/state/current.md b/ai/state/current.md
index 114ef7f..d94fbfd 100644
--- a/ai/state/current.md
+++ b/ai/state/current.md
@@ -10,6 +10,9 @@
 - Finalize `PDIAP-14859` with a dual UIKit/SwiftUI plan that removes `UIHostingController` dynamically while preserving both flows appropriately
 - Prioritize `PDIAP-15838` next; `PDIAP-15836` comes later
 - Include feature-flag planning for the broader UIKit-removal spike, including dismissal sequencing changes that affect consumers
+- Focus now on creating a process-oriented rollout document for the UIKit-removal spike that can be shared for feedback
+- The rollout document should frame the work as a more deliberate migration phase toward the SwiftUI-only path, not as a correction to a prior failed attempt
+- The rollout document should make clear that the migration plan uses a dual-path pattern to switch between the `UIHostingController` path and the SwiftUI-only path during rollout
 
 ---