Reso.AI is a mobile-first agent-assisted social product. This repository is the clean-room foundation for the new site and is isolated from the legacy deployment. The current milestone is an executable engineering scaffold; product behavior and final visual assets remain intentionally unimplemented.
apps/web— Next.js frontendapps/backend— modular FastAPI and background-worker backendpackages/ui— shared frontend design primitivescontracts— API, event, and Agent JSON contractscontent— versioned movie, questionnaire, plaza, and NPC contentprompts— versioned model prompts and policiesinfra— deployment templates and operational scriptstests— cross-service and security tests
- Node.js 22
- Python 3.12 or 3.13 (the repository selects 3.13 locally; Ubuntu 24.04 uses 3.12)
uv- PostgreSQL 16 (or Docker for the local database only)
Keep any existing .env and .env.local files. They are private and ignored.
For a fresh checkout, create .env.local from .env.development.example, then:
npm install
uv sync --all-packages --group dev
npm run dev:webRun uv run reso-api and uv run reso-worker in separate terminals. Both are
entry points of the modular backend and remain separate runtime processes. The web
shell listens on 127.0.0.1:3000; the API listens on 127.0.0.1:8000, with
business routes under /api/v1.
See the local development guide, architecture, and infrastructure templates before adding business modules.
The existing root .env is local-only and ignored by Git. Use .env.example as the canonical variable inventory. Never commit API keys, private keys, passwords, session secrets, database URLs containing production credentials, or real user data.
Before committing, run npm run security:secrets and
npm run security:dependencies. The complete frontend and
backend quality gates are documented in docs/development.md.