Dattavani Backend: core-service Module Map Diagram

How the code is split

Routers in app/routers hold HTTP shape: path, auth dependency, response envelope.
Services in app/services hold the logic and all Supabase reads and writes.
main.py registers 27 routers. Domains here are logical groups; the files are flat folders.
Most domains have one big router and several services. user_management.py (2,612 lines) and ask_tataji.py (2,516 lines) are the largest routers.

Where auth is decided

There is no global auth middleware. Each route picks a dependency.
get_current_user: parent Supabase JWT. get_active_kid_context: Kid Profile JWT.
get_parent_context_from_parent_or_kid_jwt accepts either token; config and subscription routes use it.
rag.py is the only router that gets auth at include time (main.py:333).

Background work runs outside the API

jobs/ holds 17 CLI entry points, run as python -m app.jobs.run_<name> by host cron.
Each CLI calls a services/*_job.py function, so jobs share the API's Supabase and email code.
Two jobs are pg_cron SQL instead: trial usage prune (migration 20260624200000) and stale Ask Tataji conversation anonymisation (migration 20260706150000).

Where to add things

New endpoint: add it to the domain's router, put logic in a service, register new routers in main.py.
New error code: add it to constants/response_codes.py and response_messages.py.
New request body: add a Pydantic model in schemas/models.py (StrictRequestModel rejects unknown fields).
New email: add an EML-* body under email_templates/bodies and use a layout.