Mission Rebuild the capability of Phase 34 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 Deploy the real topology—Next.js, NestJS image, Supabase services, migrations, domains/TLS/CORS, secrets, health checks, smoke tests, and rollback—as one release system.
Required artifact Staging and production deployment runbooks with release identity, environment matrix, smoke tests, and rollback procedure.
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 describe the whole topology. • Can separate environment configuration. • Can execute smoke tests. • Can explain code vs database rollback constraints.
Independent build sequence 1. Create separate staging/production environment matrices before entering any dashboard values. 2. Deploy Next.js from the intended monorepo root with public/server env vars separated. 3. Deploy the exact API container artifact and verify bind address, PORT, and readiness endpoint. 4. Apply database migrations as a controlled release step and document backward-compatibility assumptions. 5. Configure custom domains/TLS and the exact CORS/redirect origins for production. 6. Run a smoke-test checklist and practice rollback of code while reasoning about whether the database migration is reversible.
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.
Deployment is the controlled movement of a versioned artifact into a configured runtime with evidence of health and a credible rollback path.
Restate the goal of “Phase Synthesis & Independent Challenge” as one observable behavior. Write the success signal before touching code.
Trace the boundary map: versioned artifact → production config → runtime → health/smoke test → rollback path. 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: Staging and production deployment runbooks with release identity, environment matrix, smoke tests, and rollback procedure.. 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.
1. Build an immutable artifact.
2. Apply production configuration/secrets.
3. Run compatible migrations.
4. Start the new version.
5. Check readiness and smoke tests.
6. Observe errors/latency.
7. Promote or execute rollback.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.
Separate platform deploy status from application readiness; run smoke tests against real routes and dependencies.
Use expand/contract migrations and keep rollback compatibility explicit before release.
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.
Deploy the exact API container artifact and verify bind address, PORT, and readiness endpoint.
Use the smallest change that demonstrates this lesson. Stop after it works and capture evidence.Code deploy occurs before required migration or vice versa without compatibility plan
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.