Document Expo migration plan - #63
Merged
Merged
Conversation
This was referenced Aug 8, 2026
Merged
ejones23
marked this pull request as ready for review
August 8, 2026 20:58
DavidMoritz
approved these changes
Aug 9, 2026
DavidMoritz
left a comment
DavidMoritz
left a comment
Owner
There was a problem hiding this comment.
Really impressive work across this whole stack, Emmanuel. The RFC is thorough and thoughtful — I especially appreciate how you identified the auth boundary as something to get right rather than rush, and the phased approach with clear exit criteria is exactly what we need. The scaffold and ballot spike are clean, well-tested, and production-minded from day one. This is a fantastic foundation for the migration. Merging the stack — excited to see where this goes!
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Bottom layer of the Expo migration stack. Documents the proposed incremental Expo migration, including the current feature and API inventory, security boundary, target architecture, phased rollout, test policy, risks, and first implementation slice. No production code changes.