Implementation snapshot · 2 September 2026
BuzzBaby, as the app works today
A code-based map for product, engineering, and onboarding. It separates the Expo frontend from the copied Fastify/PostgreSQL backend.
index.ts/App.tsx and executable backend code in buzzbaby-be-main/src plus its OpenAPI/Prisma/migration sources are authoritative. Plans, TODOs, historical descriptions, and unused route configuration are excluded.01
Content dashboard
Interactive charts for milestone distribution, monthly coverage, skill age spans, estimates, and database-view statistics.
02
Business requirements
Actors, feature rules, user journeys, and process flows in plain language.
03
Data structure
Implemented entities, field shapes, ownership, and local persistence keys.
04
Architecture
Frontend/backend boundaries, flow ownership, business-rule locations, state, storage, and integrations.
05
API reference
Client-used endpoints, authentication, request fields, response shapes, and status handling.
06
Milestone analysis
Survey selection, answer mapping, downstream use, profile behavior, and content distribution.
Reading order
- Start with the Content dashboard for the current corpus, age-band, skill, and database-view picture.
- Read Business requirements to understand what a caregiver can do.
- Read Milestone analysis for the detailed personalization and profile logic.
- Use Data structure when tracing state or payloads.
- Use Architecture to trace each flow across UI, client rules, repositories, backend responsibilities, and durable state.
- Use API reference while integrating or debugging the backend.
How this was derived
The app entry point, reachable imports, repositories, services, screen handlers, shared types, storage adapters, endpoint builders, backend route registry, handlers, server services, database schema, migrations, and OpenAPI operations were traced. Existing product documents were used only to locate code, not to claim a feature exists.