OUTCOMES
What this Prompt helps you deliver
- The Django API is healthy
- You receive a backend call-chain map tied to product goals
BEFORE YOU START
Before you start
- Python and Docker are available
- You have read the TabTin domain model
What AI should inspect first
apps/tabtin_djangoAGENTS.mddocs/principledocs/agent/commands.mdREADY TO RUN
Complete Prompt
Copy the complete Prompt with its execution and acceptance boundaries.
Start and explain the TabTin Django backend through real product calls, not a tour of Django folders. Read AGENTS.md, docs/principle, docs/agent/commands.md, and apps/tabtin_django. Confirm database mode, environment source, API port, background jobs, and realtime boundaries. Do not enter deprecated Django IM or replace PostgreSQL with SQLite.
Start database, cache, Django, and required Celery services and check migrations. Trace one representative request through URL, serialization, domain service, model, permission, and event. Explain how Organization, Workspace, Project, Agent, App, and Device are owned. Distinguish synchronous API, asynchronous work, and collaboration services, and identify the correct extension layer. Fix startup causes from logs without deleting development data.
Call health and a read-only business API, verify database and authorization, and run the closest Django tests against PostgreSQL. Restart non-hot-reloading services after fixes. Check for secrets or cross-Organization data leaks. Report services, ports, domain relations, call chain, extension guidance, tests, current paths, and legacy paths. Do not create migrations, commit, or push unless asked.