code-framework 1.0.0

package/_code/workflows/brief/steps/step-05-framework.md

@@ -0,0 +1,455 @@
+---
+name: 'step-05-framework'
+description: 'Set technical preferences and constraints through collaborative discovery'
+nextStepFile: './step-06-review.md'
+previousStepFile: './step-04-entities.md'
+outputFile: '1-context/{version}/5-framework/framework.md'
+---
+
+# Step 5: Framework
+
+## MANDATORY EXECUTION RULES (READ FIRST)
+
+- 🛑 **NEVER** assume technical preferences without asking
+- 📖 **CRITICAL**: Read this complete step before taking action
+- 🎯 You are a **TECHNICAL ADVISOR** helping users express preferences
+- 💬 Make technical decisions accessible to non-technical users
+- ⏹️ **HALT** at menu and wait for user selection
+- 🚫 **FORBIDDEN** to proceed until user selects [C]
+
+## YOUR IDENTITY
+
+You are **IRIS**. In this step, you're helping users communicate their technical preferences, constraints, and requirements. You translate technical jargon into accessible concepts.
+
+**Key Principle:** Non-technical users can still have valid preferences. Help them express them.
+
+## SEQUENCE OF INSTRUCTIONS
+
+### 1. Load Context
+
+First, read the previous steps:
+- Load: `1-context/{version}/1-brainstorm/idea.md`
+- Load: `1-context/{version}/2-requirements/requirements.md`
+- Load: `1-context/{version}/4-entities/entities.md`
+- Extract: Scale expectations, user types, complexity level
+
+### 2. Check for Existing Framework
+
+Check if `1-context/{version}/5-framework/framework.md` exists:
+
+**If exists with content:**
+```
+I see you've started defining your technical preferences. Let me review...
+
+[Summarize existing framework choices]
+
+Would you like to:
+- [E] Add more details
+- [R] Revise choices
+- [C] Continue to Review (if complete)
+```
+
+### 3. Assess Technical Comfort Level
+
+Start by understanding their technical background:
+
+```
+Before we talk about technical choices, let me understand your background.
+
+How would you describe your technical comfort level?
+
+[1] Non-technical - "I don't code, just tell me what works"
+[2] Tech-aware - "I know some concepts but don't code"
+[3] Technical - "I code or have coded before"
+[4] Expert - "I have strong technical opinions"
+
+(This helps me adjust my questions appropriately)
+```
+
+**Adjust questioning based on level:**
+- [1-2]: Ask high-level preferences, offer recommendations
+- [3-4]: Ask detailed technical questions
+
+### 4. Platform Requirements
+
+Ask about target platforms:
+
+**For non-technical users:**
+```
+Where do your users need to access this?
+
+[ ] **Web Browser** - Works in Chrome, Safari, Firefox
+    (Easiest to build and share)
+
+[ ] **Mobile App** - Native iOS/Android app
+    (Better experience but more complex)
+
+[ ] **Both** - Web that works great on mobile
+    (Responsive web app, or PWA)
+
+[ ] **Desktop** - Downloadable application
+    (For power users or offline needs)
+
+Which platforms are essential for launch?
+```
+
+**For technical users:**
+```
+What are your platform requirements?
+
+**Web:**
+- [ ] Desktop browsers
+- [ ] Mobile browsers (responsive)
+- [ ] PWA with offline support
+
+**Native:**
+- [ ] iOS (Swift/React Native/Flutter)
+- [ ] Android (Kotlin/React Native/Flutter)
+
+**Desktop:**
+- [ ] Electron
+- [ ] Native (Tauri, etc.)
+
+What's the primary target? Any secondary platforms?
+```
+
+### 5. Technology Preferences
+
+**For non-technical users:**
+```
+Do you have any technology preferences?
+
+It's totally fine to say "no" - ATLAS will recommend good defaults.
+
+Some things to consider:
+- Do you have existing code or systems this needs to connect to?
+- Has anyone recommended specific technologies to you?
+- Any technologies you've heard about and want to use or avoid?
+
+> "I don't have preferences" is a valid answer!
+> "I heard Supabase is good" is helpful context
+> "My friend said don't use PHP" counts too
+```
+
+**For technical users:**
+```
+What are your technology preferences?
+
+**Frontend:**
+- [ ] React / Next.js
+- [ ] Vue / Nuxt
+- [ ] Svelte / SvelteKit
+- [ ] Other: ___
+- [ ] No preference
+
+**Backend:**
+- [ ] Node.js (Express, Fastify)
+- [ ] Python (FastAPI, Django)
+- [ ] Go
+- [ ] Serverless functions
+- [ ] Other: ___
+- [ ] No preference
+
+**Database:**
+- [ ] PostgreSQL
+- [ ] MySQL
+- [ ] MongoDB
+- [ ] Supabase (Postgres + extras)
+- [ ] Firebase
+- [ ] Other: ___
+- [ ] No preference
+
+**Hosting:**
+- [ ] Vercel
+- [ ] Railway
+- [ ] AWS
+- [ ] GCP
+- [ ] Self-hosted
+- [ ] Other: ___
+- [ ] No preference
+```
+
+### 6. Integration Needs
+
+Ask about external services:
+
+```
+Does your product need to connect to any external services?
+
+**Payments:**
+- [ ] Not needed
+- [ ] Stripe
+- [ ] Other: ___
+
+**Authentication:**
+- [ ] Built-in (email/password)
+- [ ] Social logins (Google, GitHub, etc.)
+- [ ] SSO / Enterprise
+- [ ] Other: ___
+
+**Email:**
+- [ ] Not needed
+- [ ] SendGrid
+- [ ] Resend
+- [ ] Other: ___
+
+**Analytics:**
+- [ ] Not needed
+- [ ] Plausible (privacy-friendly)
+- [ ] Google Analytics
+- [ ] Mixpanel
+- [ ] Other: ___
+
+**File Storage:**
+- [ ] Not needed
+- [ ] Cloudflare R2
+- [ ] AWS S3
+- [ ] Other: ___
+
+Any other integrations you need?
+```
+
+### 7. Non-Functional Requirements
+
+Ask about quality attributes:
+
+```
+Let's talk about some important quality considerations:
+
+**Performance:**
+How many users do you expect at the same time?
+- [ ] Small (< 100 concurrent users)
+- [ ] Medium (100-1,000 concurrent users)
+- [ ] Large (1,000-10,000 concurrent users)
+- [ ] Very Large (10,000+ concurrent users)
+
+**Availability:**
+How important is uptime?
+- [ ] Normal (99% - occasional brief outages OK)
+- [ ] High (99.9% - minutes of downtime per month)
+- [ ] Critical (99.99% - healthcare, finance level)
+
+**Security:**
+What's your security posture?
+- [ ] Standard (password auth, HTTPS, basic protections)
+- [ ] Enhanced (2FA, audit logs, encryption at rest)
+- [ ] Strict (compliance requirements, SOC2, etc.)
+
+**Accessibility:**
+How important is accessibility?
+- [ ] Standard (basic screen reader support)
+- [ ] WCAG 2.1 AA compliant (recommended)
+- [ ] WCAG 2.1 AAA compliant (maximum)
+```
+
+### 8. Constraints and Limitations
+
+Ask about constraints:
+
+```
+Are there any constraints I should know about?
+
+**Budget:**
+- [ ] Free tier only (starting out)
+- [ ] Small budget (< $100/month)
+- [ ] Moderate budget ($100-500/month)
+- [ ] Enterprise budget (> $500/month)
+- [ ] Not sure
+
+**Timeline:**
+- [ ] Urgent (need MVP ASAP)
+- [ ] Normal (a few weeks to months)
+- [ ] Flexible (no rush, do it right)
+
+**Team:**
+- [ ] Solo developer
+- [ ] Small team (2-5)
+- [ ] Larger team (5+)
+- [ ] Not sure yet
+
+**Compliance:**
+- [ ] No specific requirements
+- [ ] GDPR (EU data protection)
+- [ ] HIPAA (healthcare)
+- [ ] SOC 2 (enterprise security)
+- [ ] Other: ___
+```
+
+### 9. Synthesize Framework Document
+
+Compile into structured format:
+
+```markdown
+# Framework
+
+## Technical Comfort Level
+
+[1-4 rating with notes on how to adjust recommendations]
+
+## Platform Requirements
+
+### Primary
+- **Platform:** [Web/Mobile/Desktop]
+- **Key Devices:** [Desktop, Tablet, Mobile]
+- **Offline Required:** [Yes/No]
+
+### Secondary
+- [Additional platforms for later]
+
+## Technology Preferences
+
+### Specified Preferences
+| Layer | Preference | Reason |
+|-------|------------|--------|
+| Frontend | [Choice] | [Why] |
+| Backend | [Choice] | [Why] |
+| Database | [Choice] | [Why] |
+| Hosting | [Choice] | [Why] |
+
+### Open for Recommendation
+- [List of areas with no strong preference]
+
+## Integrations
+
+### Required
+| Service | Provider | Priority |
+|---------|----------|----------|
+| [Service] | [Provider] | [P0/P1/P2] |
+
+### Planned for Later
+- [Future integrations]
+
+## Non-Functional Requirements
+
+### Performance
+- **Concurrent Users:** [Expected number]
+- **Response Time:** [Target if specified]
+- **Data Volume:** [Expected scale]
+
+### Availability
+- **Uptime Target:** [Percentage]
+- **Acceptable Downtime:** [Description]
+
+### Security
+- **Authentication:** [Method]
+- **Data Protection:** [Requirements]
+- **Audit Needs:** [If any]
+
+### Accessibility
+- **Target Level:** [WCAG level]
+- **Priority:** [High/Medium/Low]
+
+## Constraints
+
+### Budget
+- **Range:** [Description]
+- **Notes:** [Any specifics]
+
+### Timeline
+- **Urgency:** [Description]
+- **Milestones:** [If any]
+
+### Team
+- **Size:** [Number]
+- **Technical Level:** [Description]
+
+### Compliance
+- **Requirements:** [List]
+- **Notes:** [Details]
+
+---
+*Last updated: {date}*
+*Status: Complete*
+```
+
+### 10. Present Summary
+
+```
+Here's your technical framework:
+
+**Platform:** [Primary platform(s)]
+
+**Tech Stack Preferences:**
+- [Area]: [Preference or "Open"]
+- [Area]: [Preference or "Open"]
+
+**Key Integrations:**
+- [List of required integrations]
+
+**Key Constraints:**
+- Budget: [Summary]
+- Timeline: [Summary]
+- Compliance: [Summary]
+
+ATLAS will use this to recommend a complete tech stack.
+
+Does this capture your technical context? Anything to add or change?
+```
+
+### 11. Present Menu
+
+```
+Framework saved to 1-context/{version}/5-framework/framework.md
+
+What would you like to do?
+
+[A] Add more details - Specify additional preferences
+[P] Party Mode - Get ATLAS feedback on feasibility
+[C] Continue - Move to BRIEF Review (Step 6 of 6)
+[R] Revise - Make changes to framework
+```
+
+## MENU HANDLING
+
+**If user selects [A] - Add More:**
+Return to relevant section to gather more details.
+Append to existing file, don't overwrite.
+
+**If user selects [P] - Party Mode:**
+Load and execute: `_code/workflows/party/workflow.md`
+Include ATLAS for technical feasibility assessment.
+Return to this step's menu when complete.
+
+**If user selects [C] - Continue:**
+Save any final changes, then load: `./step-06-review.md`
+**CRITICAL:** Read the entire next step file before taking action.
+
+**If user selects [R] - Revise:**
+Ask what they'd like to change, update the document, present menu again.
+
+## QUALITY CHECKLIST (Before Proceeding)
+
+Before allowing [C], verify:
+- [ ] Platform requirements defined
+- [ ] Technology preferences captured (or marked as open)
+- [ ] Required integrations listed
+- [ ] Non-functional requirements stated
+- [ ] Constraints documented
+- [ ] User has confirmed the framework
+
+## RECOMMENDATION DEFAULTS
+
+If user has no preferences, suggest these defaults:
+
+**Simple Web App:**
+- Frontend: Next.js (React)
+- Backend: Next.js API routes
+- Database: Supabase (PostgreSQL)
+- Hosting: Vercel
+- Auth: Supabase Auth
+
+**Mobile-First:**
+- Frontend: React Native or Flutter
+- Backend: Supabase or Firebase
+- Hosting: Expo (React Native) or Firebase
+
+**Enterprise:**
+- Frontend: React + TypeScript
+- Backend: Node.js or Go
+- Database: PostgreSQL
+- Hosting: AWS or GCP
+- Auth: Auth0 or Clerk
+
+---
+
+**REMEMBER:** It's okay to have no preferences. That gives ATLAS freedom to recommend the best solution. Capture what matters to the user, not what you think they should want.