arete app

The apps/arete/ area: three deployable applications — a Fastify REST API, a Vite/React web dashboard, and an Expo/React Native mobile app — that together ship Arete, the personal-development product modelled on Stephen Covey's "7 Habits of Highly Effective People."

What this area is#

Arete is a self-improvement product: members track habits, set and progress goals, journal, run "Wheel of Life" balance check-ins, manage time, earn gamification rewards, and talk to an AI coach. apps/arete/ holds the three client-facing applications that deliver that product across surfaces. They are the scope:arete apps in the monorepo — distinct from the shared @arete/* libraries (@arete/core, @arete/ai-coach, @arete/habits) that live outside this directory and that the API composes.

@arete/api is the spine. Its buildServer() factory (apps/arete/api/src/app.ts) assembles a Fastify instance with a deliberate plugin order — request-context → CORS → error-handler → Swagger → auth (JWT) → database (PostgreSQL + Drizzle) → Redis → rate-limit → mailer → repositories → routes. Routes are grouped by domain under /v1/* (habits, goals, journal, vision, time, balance, gamification, coach, dashboard, reminders) and registered in apps/arete/api/src/routes/index.ts. The domain logic reaches storage through a repository seam (fastify.repositories.*): Drizzle/Postgres-backed in production, in-memory in tests. The AI coach routes delegate to the @arete/ai-coach library for deterministic CBT prompting, recommendations, and per-user pattern detection over the member's real records.

@arete/web and @arete/mobile are the two consumer front-ends over that API. The web app (apps/arete/web/src/router.tsx) is a React Router SPA with lazy-loaded, auth-gated pages for every domain (dashboard, habits, goals, journal, time, wellness, vision, analytics, coach, settings, profile), a fetch-based API client with token refresh (apps/arete/web/src/api/client.ts), React Query hooks, Zustand stores, and a large in-repo component library (charts, tables, forms, ~50 UI primitives). The mobile app (apps/arete/mobile/App.tsx) is a React Native client with stack + bottom-tab navigation (src/navigation/AppNavigator.tsx), React Query, offline-sync and push-notification services, biometric/social login, and native home-screen widgets for iOS (ios/AreteWidgets/) and Android (android/.../widgets/).

How it fits the wider system#

The three apps relate front-end-to-back-end, not as a library graph: @arete/web and @arete/mobile are independent clients that call @arete/api over HTTP. The API in turn integrates upward into the Oshun platform through a dedicated service-to-service facade, apps/arete/api/src/routes/oshun-facade.ts. That plugin serves /v1/oshun/* (and the /v1/arete/healthz probe) for the Oshun BFF's Arete adapter to dial: it maps Arete's repository records onto the canonical @oshun/domain-arete wire shapes, wraps every response in the @oshun/contracts partial-failure envelope ({ results, errors, partial }), fails closed on a missing/invalid ARETE_OSHUN_FACADE_TOKEN in production, and bridges opaque Oshun member ids to shadow arete_users rows so facade writes land in the same tables the native /v1/* routes read. The API also depends on shared platform libraries (@oshun/auth, @oshun/database, @oshun/errors, @oshun/logging, @oshun/metrics, @oshun/tracing) and the Arete domain libraries (@arete/core schema, @arete/ai-coach, @arete/habits). The boundary is clean: the front-ends never import the API's internals, and the Oshun platform integrates only through the facade contract, never the native routes.