Identity that is already connected
Email verification, Google sign-in, account settings, provider-backed email, and role-aware administration share one Better Auth foundation.
Cloudflare-first product foundation
Begin with a connected system.
App-first Dayhome platform for Agencies supervising independent Dayhomes, Providers recording daily care, and parents following their child. Expo iOS and Android apps are the primary Provider and parent experience; Web supports Agency operations, administration, public presentation, and no-install parent access. Basic includes all core features with manual records; AI automates photo and record organization as reviewable drafts.
Keep only what the product needs.
The Blueprint controls pages, SaaS modules, external capabilities, providers, and release lanes before AI changes the repository.
Cloudflare release boundaries
Development is the normal release lane. Production remains a separate explicit action with its own Worker, domain, and database.
Optional modules stay optional
Organizations, Stripe billing, maps, and growth pages enter the application only after selection and materialization.
Context survives the conversation
Markdown, catalogs, Change Specs, and the generated Development Plan tell the next AI what exists and what remains unverified.
Describe. Configure. Verify. Release.
Every stage leaves a repository-readable contract, so later work does not depend on chat memory.
- DescribeRecord the product, platforms, and constraints.
- ConfigureSelect exact routes, modules, providers, and design profile.
- VerifyBuild from an empty database and attach current evidence.
- ReleasePublish Development first. Promote only with explicit Production intent.
Begin with a reviewed Blueprint.
Use the product shell now, or inspect the public documentation before changing the assembly.