Upgrade
ChecklistsReference
Technical worklists for stage and stack transitions.
Read this when you're ready to advance from one stage to the next.
Each transition has entry criteria, work items, and anti-patterns to avoid.
How advancement works
Advancement is intentional, not accidental. Before moving to the next stage:
- Complete several delivery cycles until the work is validated
- Complete the technical checklist below
- Run the relevant audits at your target stage level
Stage Transitions
Checklists for advancing through delivery stages.
POCMVP
Introduce persistence, auth, and basic quality checks.
Entry Criteria
- POC validated with stakeholders
- Core assumptions proven
- Brief checkpoint passed
- MVP scope defined
Anti-Patterns
- Keeping mock data 'temporarily'
- Skipping auth because 'it's internal'
- No error handling on critical paths
- Hardcoded configuration values
Required Work Items
- Replace mock data with real database
- Implement user authentication
- Add proper error handling
- Implement core happy-path tests
- Set up environment configuration
- Add basic logging
- Review and fix security basics
- Update State of Play document
Stack Transitions
Technical checklists for adding backend capabilities.
Stack AStack B
Add auth and persistence with Supabase.
Entry Criteria
- POC validated
- Need for auth or data persistence confirmed
- Supabase is appropriate (not needing Stack C)
Anti-Patterns
- No row-level security on tables
- Exposing service role key to client
- Skipping database design
- No testing of auth flow
Required Work Items
- Create Supabase project
- Add environment variables to .env.local
- Install @supabase/supabase-js and @supabase/ssr
- Create lib/supabase/ with client utilities
- Design database schema
- Implement row-level security policies
- Migrate mock data to database
- Implement authentication flow
- Update API calls to use Supabase
- Test auth flow end-to-end
Next Steps
Where to go from here: