Ensign Scope

Title

Tags

Body (markdown)

The next-gen Ensign codebases and what each is for. When scoping new work, reference the right one rather than reinventing.

| Repo | Stack | Purpose | Port |
| --- | --- | --- | --- |
| **project-commander** | Next.js 16, React 19, Redux Toolkit | Frontend web app — projects, financials, procurement, subcontractors, reporting | 3000 |
| **commander-api** | NestJS, TypeORM, Postgres, Redis | Backend REST API — all business logic, 30+ modules, Swagger at `/swagger` | 4000 |
| **ensign-sso** | NestJS, TypeORM, Postgres, JWT | Authentication & multi-tenant identity — login, users, companies, sessions, licenses | 4001 |
| **ensign-ui** | Next.js, shadcn registry | Shared component registry distributed via the shadcn CLI | — |
| **report-engine** | — | Document/report generation (PDF via Carbone templates) | — |
| **ensign-help** | Next.js | Help centre / docs site | — |

## How they fit together

```
Browser → project-commander (Next.js)
            → commander-api (NestJS)  ── JWT verified against ──→ ensign-sso
                                        └─ Postgres (+ Redis cache/queues)
```

- **Auth** is always ensign-sso. commander-api verifies its JWTs; they share `JWT_SECRET`.
- **Frontend ↔ backend contract** is the OpenAPI schema; frontend types are generated from it.
- **Shared UI** comes from ensign-ui.
- **Integrations** (Xero, Sage, Monday.com) run through commander-api background queues / ensign-sso modules.

Which to reference for what: financial/business rules → commander-api; auth/identity/multi-tenancy → ensign-sso; UI primitives/patterns → ensign-ui; user-facing app flows → project-commander.

Edit context doc