Mission Rebuild the capability of Phase 09 without following the exact code line-by-line. The goal is transfer: can you use the ideas when the variable names, UI, or route shape changes?
Required outcome Integrate Prisma 7.9.1 as a repeatable persistence layer with schema, generated client, adapter/configuration, migrations, and NestJS lifecycle.
Required artifact Prisma schema + migration history + generated client + NestJS PrismaService connected to TaskFlow PostgreSQL.
Constraints • Start from the previous phase checkpoint or a fresh branch. • Use the course architecture boundaries, but do not copy the reference implementation until after your first attempt. • Keep changes scoped to the capability. • Preserve validation, authorization, error handling, and observability expectations already earned in earlier phases. • Record any design decision where more than one implementation is reasonable.
Acceptance criteria • Can explain schema vs migration vs generated client. • Can create and inspect a migration. • Can wire Prisma to NestJS cleanly. • Can diagnose common connection/migration failures.
Independent build sequence 1. Pin Prisma packages to the course version contract and verify all Prisma package versions match. 2. Initialize Prisma with the intended generated-client output and PostgreSQL configuration. 3. Model one entity, create the first migration, and inspect the SQL before applying it. 4. Generate the client and wire a PrismaService into NestJS with controlled lifecycle. 5. Perform a smoke query through the service, then inspect the created database object independently. 6. Cause a safe migration/configuration failure and practice reading Prisma error codes instead of reinstalling randomly.
Self-review Compare your implementation to the reference only after the acceptance criteria pass. Differences are not automatically mistakes. For each difference, ask: does it preserve the same contract, security boundary, correctness, maintainability, and operational behavior? Keep the alternative when you can justify it with evidence.
Stretch challenge Change one assumption: more users, a second tenant, a slow network, an expired session, a concurrent mutation, a deployment restart, or a failed dependency. Predict whether your design still behaves correctly. If not, document the next architectural improvement rather than adding complexity blindly.
Phase exit Run the relevant checks, inspect Git diff, and write a three-sentence summary: what the system can do now, which boundary owns the new responsibility, and which failure you now know how to diagnose. Only then mark the phase complete.
Prisma improves developer ergonomics, but migrations and generated queries still change a real relational database. You should be able to inspect both sides.
Restate the goal of “Phase Synthesis & Independent Challenge” as one observable behavior. Write the success signal before touching code.
Trace the boundary map: domain intent → Prisma Client → generated SQL → PostgreSQL → mapped result. Mark the one boundary this lesson changes.
Inspect the current repository state and record the exact files, route, table, or runtime involved. Avoid creating an abstraction before you can name the existing owner.
Implement the smallest vertical slice. Add one coherent change, run the narrowest verification command, and read the output before continuing.
Connect the slice to TaskFlow’s phase artifact: Prisma schema + migration history + generated client + NestJS PrismaService connected to TaskFlow PostgreSQL.. Verify behavior from the outside as a user or API client would.
Create one controlled failure that is safe to reproduce. Predict the symptom first, capture evidence, locate the earliest broken boundary, then fix only that cause.
Close the reference and rebuild or explain the core change from memory. Record what you would monitor or test before trusting the same change in production.
const tasks = await prisma.task.findMany({
where: { workspaceId },
orderBy: [{ createdAt: "desc" }, { id: "desc" }],
take: 20,
});Do not copy this as a finished answer. Predict what each boundary does, type the smallest useful slice, run it, then compare the result with your prediction.
Verify connection string, host, port, SSL/pooler mode, network reachability, and which environment file the process loaded.
Read the generated SQL before applying it and compare the change against existing production-shaped data.
Without copying the final source, create a second small scenario that applies “Phase Synthesis & Independent Challenge” to a different TaskFlow resource or input. Write the acceptance criteria first, implement it, and provide the evidence that each criterion is satisfied.
Pin Prisma packages to the course version contract and verify all Prisma package versions match.
Use the smallest change that demonstrates this lesson. Stop after it works and capture evidence.CLI/client version mismatch
Predict the symptom before causing the failure. Then locate the earliest boundary where reality diverges from expectation.Why does this responsibility live here, what input does it trust, what output proves success, and what would go wrong if another layer owned it?
If your explanation is vague, repeat the boundary trace before moving on.Close the reference. Reproduce the core idea from memory or explain the exact request/data flow aloud. Then check your diff or notes for accidental shortcuts that bypass validation, authorization, error handling, or verification earned in earlier phases.