Components + App Shell
Every later screen assembles from these pieces.
Cross-cutting #8 + App shell #2a · 16 surfacesBuild order locked
ARVO frontend starts with the reusable operating layer.
Cross-cutting components and the app shell are first-class here, so every schedule, portal, billing, and back-office screen inherits the same trust, tenant, and activity grammar.
What should Arvo handle next?
Solo build sequence
Auth + Onboarding
All portals branch from invite, role, and tenant state.
Foundations #1 · 15 surfacesSchedule
Biggest module and the first two demo wedges.
Schedule #2e · 19 surfacesStudents, Families + Booking
Inquiry capture and enrollment become concrete here.
Students #2f + Booking #6 · 13 surfacesCommand Center + Work
Owner morning summary, tasks, and execution proof.
Command #2b + Tasks #2d + Activity #2c · 10 surfacesParent + Teacher Portals
Mobile parity is doctrine, not polish.
Parent #4 + Teacher #5 · 11 surfacesBilling, Reports, Settings
Revenue, policy, and operational truth surfaces.
Billing #2k + Reports #2j + Settings #2l · 27 surfacesLocations, Services, Team + Back Office
The admin substrate and internal ARVO control plane.
Locations #2g + Services #2h + Team #2i + Back Office #7 · 31 surfacesReusable components, first pass
Arvo proposes
Move Ava Chen to Tuesday 4:30 and reserve Studio B.
Policies consultedCancellation window, makeup eligibility, room capacity
Data evaluated7 entities · 3 conflicts · 2 parent preferences
Execution previewNotify family, reserve Studio B, write Activity row
Ava Chen
M. Rivera
Jonah Miles
L. Park
Smart-ranked slots
drafted a teacher absence plan
approved makeup conversion for Mila
blocked demo booking submission
No overdue recordings
Pending teacher items will appear here with deadline and family context.
Policy preview unavailable
Retry after the rule engine returns a typed bucket result.