Lovat Backend

The in-progress v2 Lovat API, structured as a Hono modular monolith.

Runtime

• Bun is used for local development and tests.
• SST packages the same Hono application for AWS Lambda.
• PostgreSQL is accessed through Drizzle.

Setup

1. Install dependencies:

   bun install

2. Copy .env.example to .env and provide local values.

3. Start the local API:

   bun run dev

The health endpoint is available at GET /v2/health.

Implemented API

• GET /v2/accounts/me and DELETE /v2/accounts/me
• GET /v2/api-keys and POST /v2/api-keys
• PATCH /v2/api-keys/{uuid} and DELETE /v2/api-keys/{uuid}
• GET /v2/openapi.json

Dashboard routes require an Auth0 bearer token. API-key management additionally requires membership in an email-verified team; analysts manage their own keys, while scouting leads can manage keys belonging to members of their team.

Quality checks

bun run typecheck
bun run lint
bun run format:check
bun run test

Database migrations

The TypeScript schema in src/platform/database/schema is the intended source of truth.

bun run db:generate
bun run db:migrate

The existing migration predates the restarted implementation and must not be applied to production until its compatibility with the current Lovat database has been reviewed.

Modules

Each business capability owns its routes, contracts, service, repository, policies, and tests under src/modules. Shared runtime concerns live under src/platform, while external systems live under src/integrations.