ADR-002: Database Workspace

Status

Accepted

Context

The Admin and Resident applications will eventually need a common database boundary. Installing database dependencies directly into either application would make that boundary application-owned.

Decision

Create packages/db, install Prisma as a development dependency and @prisma/client as a runtime dependency there, and keep the PostgreSQL schema, Prisma configuration, generated client, and reusable @aspire/db export in that package. The schema may contain a neutral convention model to establish Aspire-controlled UUID identity and mapped timestamps. Domain-model design, migrations beyond the initial infrastructure migration, and application queries remain out of scope until a dedicated database feature specifies them.

Consequences

Prisma tooling has one home in the workspace and does not add a Python runtime. A future database feature must add domain models, migrations, and application queries; it must regenerate the client after schema changes. The package provides reviewed development, production deployment, status, and read-only connection-verification commands. External provider identifiers are never used as primary keys.

Date

2026-09-18