The Expo rewrite is approved and ticketed. The Expo mock Inbox and the existing SwiftUI and Mac Catalyst prototype, plus the native Mac mock Inbox, are executable. Read documents according to their scope below; publication of a plan does not prove implementation or release.
-
Google registration, Gmail consent and protected OAuth qualification
-
Apple registration, mailbox choice and current Gmail authorization
-
IMAP mailboxes: setup, synchronization, reading and SMTP sending
-
Catch Up, the planned chat-style Inbox, and background summaries
-
System Category model benchmark for English and Czech (spike #828)
-
Custom Category model benchmark for English and Czech (spike #829)
-
Command Palette: finding and running actions from any screen
- Root agent guide and backend guide
- Implement a GitHub issue through PR babysitting
- Implementation handoff, incremental OCR checkpoints, thermo-nuclear and design review agents
- Domain vocabulary by topic and maintenance policy
- Native design system: tokens, type, layout and components
- Test admission, retirement, and feedback budgets
- Effect conventions and lint enforcement
- Effect service constructors, methods and layers
- Native validation and resource ownership
- GitHub issue workflow and triage labels
- Automated reviews and PR babysitting
The implementer uses this index to find requirements and operational guidance. Only the review agent opens architecture docs and decision records under the implementation and review workflow.
These operating guides remain useful while the prototype is present. Their commands and results do not transfer to new hosts.
- Swift setup and current behavior
- Scoped Swift agent guide
- Mail test environment
- Protected Gmail test tenant
- Storage and Private Sync export
The reviewer-only architecture index routes extracted companions, ADRs, patterns, research, qualification evidence and historical sources. Implementers do not open those files. The reviewer verifies applicable decisions and deferred release checks under the handoff workflow.
Update affected operational documentation in each implementation slice. At cutover #627, remove the remaining Swift implementation, build targets and tests after their replacement slices are complete. Prototype commands and results do not qualify replacement hosts.