Database Schema and Migrations
Prisma schema ownership, generated client, migration workflow, and safety.
Review migration SQL and take a backup before any shared-environment change.
Source boundary
Source boundary: AutoCore current main 7a504f6e430c16d4fcb03ebdea3cc3fb7816df60, checked against immutable v1.0.0-rc.1 at 9edfb109f44cc80385784c694b96392cfc04e70f.
Prisma schema and migrations live in packages/database; API and worker consume the shared client. db:deploy is the controlled deployment path; destructive reset operations are local-only and approval-gated.
| Check | Source-backed expectation |
|---|---|
| Scope | Never run reset, drop, force migration, or broad data mutation without explicit approval. |
| Evidence | Use placeholders, timestamps, release identity, route, status, and request ID where relevant. |
| Safe action | pnpm db:validate && pnpm db:generate |
| Stop condition | Unknown authorization, destructive impact, secret exposure, or conflicting evidence. |
Verification
Run the safe check, record its result, and compare the outcome with the documented contract. If the result depends on external configuration or provider availability, mark it as configuration-dependent rather than claiming a product guarantee.
pnpm db:validate && pnpm db:generate
Safety boundary
Examples are non-production and use placeholders. Do not deploy, reset, force a migration, create secrets, activate providers, replay sensitive work, or expose private data from this page.