Live screenshot
The screenshot reflects the current production gate: health and database durability passed, while rollback remains open.
FEATURED PROJECT • COMMAND CENTER
Command Center
A Next.js agency workspace for morning briefings and proposal generation, now tracked through production health, database durability, demo-boundary, and rollback-readiness gates.
Next.js App Router
Production health verified
Rollback pending
Role
Proposal workflow, production gates, and deployment verification
Focus
Database mode, no demo fallback, health checks, and redeploy durability
Surface
Briefing, proposal generation, proposal dashboard, HTML export, health route
Status
Phase 1 open only for rollback drill
Case study
Command Center milestones and rollback status.
The important part is which production checks passed and which one is still open.
Challenge
Separate real production data from demo convenience.
Command Center needed proposal workflows that could run in a recruiter-safe demo mode while making sure production never silently falls back to seeded fixtures when a database is configured.
Approach
Add health, mode boundaries, and deployment evidence.
I added `/api/health`, production-like no-fallback behavior, Vercel production verification, database-backed read/write checks, and redeployment persistence for a controlled proposal record.
Current limit
Production health passed; rollback still needs execution.
On August 21, 2026, production `/api/health` reported database mode, migrations ready, and `demoFallbackAllowed: false`. The remaining Phase 1 gate is an application rollback drill without reversing database migrations.
Verified milestones
- Proposal generation supports website, finance, school, medical, and custom project types.
- Manual proposal submit persists through generate route, demo storage, redirect, and saved detail render.
- Production/demo boundaries prevent database-backed reads from falling through to local demo fixtures.
- Production `/api/health` verifies database mode, migration readiness, and disabled demo fallback.
- Controlled proposal `cmt3cs0xp0003ld04lk2q3owx` survived redeployment.
Remaining production gate
- Rollback from the deployed version to an eligible previous release still needs to be tested.
- The controlled proposal must remain readable after rollback.
- The app must roll forward to the current health/no-fallback deployment.
- PDF export still depends on runtime Chromium; HTML export is the deployment-safe path that has passed.