oneie
Version:
Build apps, websites, and AI agents in English. Zero-interaction setup for AI agents (Claude Code, Cursor, Windsurf). Download to your computer, run in the cloud, deploy to the edge. Open source and free forever.
605 lines (454 loc) • 21.1 kB
Markdown
title: Wave1 Orchestration Summary
dimension: things
category: plans
tags: agent, ai, architecture, cycle, ontology
related_dimensions: events, groups, people
scope: global
created: 2025-11-03
updated: 2025-11-03
version: 1.0.0
ai_context: |
This document is part of the things dimension in the plans category.
Location: one/things/plans/wave1-orchestration-summary.md
Purpose: Documents wave 1 creator onboarding - orchestration summary
Related dimensions: events, groups, people
For AI agents: Read this to understand wave1 orchestration summary.
# Wave 1 Creator Onboarding - Orchestration Summary
**Generated:** 2025-11-01
**Status:** Ready for Immediate Execution
**Team Lead:** Agent-Director
**Duration:** 10-12 calendar days
## What Was Just Done
The Agent-Director has completed **Phase 1: Foundation & Validation (Cycle 1-10)** for Wave 1 Creator Onboarding.
### Three Comprehensive Plans Generated
1. **`wave1-onboarding-vision.md`** (7,500+ words)
- Executive summary
- Complete 6-dimension ontology validation
- 4 detailed user personas
- 8-stage onboarding flow diagram
- Success metrics + first-day quick wins
- Architecture notes + integration points
- Out of scope clarification
- Dependencies identification
2. **`wave1-onboarding-100-cycles.md`** (12,000+ words)
- Complete 100-cycle breakdown (Cycle 1-100)
- Each cycle has: task, deliverable, duration, status
- Dependencies clearly marked
- Parallel execution strategy (10-12 calendar days, 38 person-days)
- Risk mitigation planning
- Success criteria for each phase
- Resource requirements
3. **`wave1-specialist-assignments.md`** (10,000+ words)
- Specialist 1 (Backend): 40 cycles (10 days)
- Specialist 2 (Frontend): 20 cycles (5-6 days)
- Specialist 3 (Quality): 10 cycles (2-3 days)
- Specialist 4 (Design/Documentation): 10 cycles (5-7 days)
- Specialist 5 (Director/Orchestrator): 100 cycles (10 days)
- Detailed task breakdown for each specialist
- Deliverables checklist
- Gate decisions + blockers
## 6-Dimension Ontology Validation: COMPLETE ✅
**All 6 dimensions perfectly mapped:**
### 1. GROUPS ✅
- Creator's workspace = new `organization` group
- Team members = additional people in group
- Hierarchical support (personal → departments)
- Group ownership (creator = group_owner)
- All data scoped to group
### 2. PEOPLE ✅
- Creator = person with properties
- Roles: group_owner, group_user (editor/viewer)
- Authentication: email verified
- Permissions: workspace-scoped
- Governance: creator controls access
### 3. THINGS ✅
- Creator thing (email, username, bio, niche, skills)
- Organization thing (workspace, name, plan, members)
- Invitation_token thing (for team invites)
- Verification_token thing (for email verification)
- UI_preferences thing (user settings)
### 4. CONNECTIONS ✅
- member_of: creator → workspace (role: group_owner)
- member_of: team_member → workspace (role: group_user)
- owns: creator → workspace (ownership)
- refers relationships (future)
### 5. EVENTS ✅
- user_registered, email_verification_sent, email_verified
- profile_updated, thing_created (workspace)
- user_invited_to_group, user_joined_group
- wallet_connected, thing_updated (skills)
- onboarding_completed
- All events logged for audit trail + analytics
### 6. KNOWLEDGE ✅
- Skill labels: skill:video-editing, skill:copywriting, etc.
- Industry labels: industry:fitness, industry:education, etc.
- Interest labels: topic:personal-branding, topic:monetization, etc.
- Goal labels: goal:income, goal:audience, goal:collaboration, etc.
- All linked to creators via knowledge junctions
**Validation:** ✅ APPROVED - Feature maps perfectly to all 6 dimensions
## The 100-Cycle Plan Overview
### Phase 1: Foundation (Cycle 1-10) ✅ COMPLETE
- Ontology validation
- Entity type definition
- Event type specification
- Connection type definition
- Knowledge taxonomy
- Implementation checklist
- **Status:** Ready for next phase
### Phase 2: Backend Schema & Services (Cycle 11-30)
**Specialist:** Agent-Backend
**Duration:** 10 days (20 cycles)
**Key Deliverables:**
- Creator entity extended
- Organization entity extended
- Invitation_token entity created
- Onboarding service (Effect.ts)
- All mutations (signup, verify, profile, workspace, team, wallet, skills)
- All queries (status, users, workspaces, members)
- Email templates (5 types)
- Verification system
- Rate limiting configured
**Blocker:** Unblocks Frontend API integration (Cycle 51+)
### Phase 3: Frontend Components & Pages (Cycle 31-50)
**Specialist:** Agent-Frontend
**Duration:** 5-6 days (20 cycles)
**Can start:** Day 3 (while backend still working on Cycle 11-30)
**Key Deliverables:**
- 8 reusable components (SignupForm, EmailVerification, ProfileForm, etc.)
- 8 onboarding pages (signup → complete)
- Team management page
- Helper components (avatar upload, skill selection, loading states, etc.)
- Mobile responsive design
- Accessibility compliance
- Dark mode support
**Blocker:** Needs API routes ready by Cycle 51+
### Phase 4: API Routes & Integration (Cycle 51-70)
**Specialist:** Agent-Backend + Agent-Integration
**Duration:** 5-6 days (20 cycles)
**Key Deliverables:**
- 25+ HTTP API routes (auth, profile, workspace, team, wallet, skills, onboarding)
- Resend email configuration
- Email template integration
- Integration testing
**Blocker:** Unblocks integration testing (Cycle 71+)
### Phase 5: Testing & Quality (Cycle 81-90)
**Specialist:** Agent-Quality
**Duration:** 2-3 days (10 cycles)
**Key Deliverables:**
- Unit tests (90%+ backend, 85%+ frontend coverage)
- Integration tests (full flows)
- E2E tests (browser-based)
- Security audit
- Accessibility audit
- Performance audit
**Blocker:** Unblocks deployment (Cycle 91+)
### Phase 6: Deployment & Documentation (Cycle 91-100)
**Specialist:** Agent-Ops + Agent-Documenter
**Duration:** 1-2 days (10 cycles)
**Key Deliverables:**
- User guides (getting started, onboarding, team management, troubleshooting)
- API documentation (all routes with examples)
- Developer setup guide
- Deployment checklist
- Production deployment
- Monitoring setup
- Release notes
- Lessons learned
**Blocker:** Marks Wave 1 complete
## Specialist Team Assignments
| Role | Name | Cycles | Duration | Start Date | Status |
| ------------ | -------------- | ------------------ | -------- | ------------------------ | ------ |
| Backend | Agent-Backend | 40 (11-30, 51-70) | 10 days | Day 1 | Ready |
| Frontend | Agent-Frontend | 20 (31-50) | 5-6 days | Day 3 | Ready |
| Quality | Agent-Quality | 10 (81-90) | 2-3 days | Day 8 | Ready |
| Design/Docs | Agent-Designer | 10 (41-50, 91-100) | 5-7 days | Day 1 design, Day 9 docs | Ready |
| Orchestrator | Agent-Director | 100 (1-100) | 10 days | Day 1 | Active |
## Critical Path Timeline
```
┌─────────────────────────────────────────────────────────────┐
│ DAY 1 (Cycle 1-10): Foundation & Ontology Validation │
│ ✅ COMPLETE │
└─────────────────────────────────────────────────────────────┘
↓ (unblocks everything)
┌─────────────────────────────────────────────────────────────┐
│ DAY 2-3 (Cycle 11-20): Backend Schema & Services │
│ Specialist: Agent-Backend │
│ Parallel: Design starts (Cycle 41-45) │
└─────────────────────────────────────────────────────────────┘
↓ (schema ready)
┌─────────────────────────────────────────────────────────────┐
│ DAY 3-5 (Cycle 21-30): Backend Mutations & Queries │
│ Specialist: Agent-Backend │
│ Parallel: Frontend starts (Cycle 31-50) │
│ Parallel: Design continues (Cycle 46-50) │
└─────────────────────────────────────────────────────────────┘
↓ (backend complete)
┌─────────────────────────────────────────────────────────────┐
│ DAY 6-7 (Cycle 51-70): API Routes & Email Integration │
│ Specialist: Agent-Backend │
│ Frontend: Almost ready, waiting for API routes │
└─────────────────────────────────────────────────────────────┘
↓ (APIs ready)
┌─────────────────────────────────────────────────────────────┐
│ DAY 7-8 (Cycle 71-80): Integration Testing │
│ Specialist: Agent-Integration │
│ Test: Frontend + Backend together │
└─────────────────────────────────────────────────────────────┘
↓ (integration working)
┌─────────────────────────────────────────────────────────────┐
│ DAY 8-9 (Cycle 81-90): Quality Testing & Audits │
│ Specialist: Agent-Quality │
│ Unit tests, Integration tests, E2E tests │
│ Security, Accessibility, Performance audits │
└─────────────────────────────────────────────────────────────┘
↓ (quality approved)
┌─────────────────────────────────────────────────────────────┐
│ DAY 10-12 (Cycle 91-100): Deploy & Document │
│ Specialist: Agent-Ops + Agent-Documenter │
│ Deploy to production, setup monitoring │
│ Create user guides, API docs, release notes │
└─────────────────────────────────────────────────────────────┘
↓ (all done)
WAVE 1 COMPLETE ✅
```
## Success Criteria
All of these must be met before Wave 1 closes:
### Functional ✅
- User can sign up (email + password + OAuth)
- Email verification working
- Profile form complete
- Workspace creation working
- Team invitations (send + accept)
- Wallet connection (optional)
- Skills tagging working
- Onboarding status tracked
- All events logged
### User Experience ✅
- 80%+ completion rate
- Average time < 15 minutes
- Mobile responsive (70%+ of desktop)
- WCAG 2.1 AA accessible
- No critical UI bugs
### Quality ✅
- 90%+ backend test coverage
- 85%+ frontend test coverage
- All integration tests passing
- All E2E tests passing
- Security audit passed
- Performance targets met
### Operations ✅
- Live in production
- Monitoring active
- Analytics tracking
- User guides published
- API docs published
## Key Decisions & Gateways
**Gate 1 (Cycle 10):** APPROVED ✅
- Decision: Is ontology mapping complete?
- Result: **YES** - All 6 dimensions perfectly aligned
- Action: Release all specialists
**Gate 2 (Cycle 30):**
- Decision: Is backend schema production-ready?
- Validation: All mutations + queries working, types generated
- Action: Unblock frontend API integration (Cycle 51)
**Gate 3 (Cycle 70):**
- Decision: Is API integration working end-to-end?
- Validation: Full signup → dashboard flow works
- Action: Unblock quality testing
**Gate 4 (Cycle 90):**
- Decision: Is quality acceptable for production?
- Validation: Tests pass, audits complete, no critical issues
- Action: Approve production deployment
**Gate 5 (Cycle 100):**
- Decision: Is Wave 1 complete?
- Validation: All success criteria met
- Action: Mark Wave 1 complete, release Wave 2 planning
## Parallel Execution Strategy (10-12 Days, Not 20+)
**Key Insight:** Backend (20 days alone) + Frontend (5-6 days alone) can overlap!
```
Timeline with Parallelization:
Day 1: Backend Cycle 11-15 + Design Cycle 41-45
Day 2: Backend Cycle 16-20 + Frontend Cycle 31-35
Day 3: Backend Cycle 21-25 + Frontend Cycle 36-40
Day 4: Backend Cycle 26-30 + Frontend Cycle 41-45
Day 5: API Routes Cycle 51-55 + Frontend Cycle 46-50
Day 6: API Routes Cycle 56-60 + Integration Cycle 71
Day 7: Email Cycle 61-65 + Integration Cycle 72-75
Day 8: Email Cycle 66-70 + Quality Cycle 81-85
Day 9: Quality Cycle 86-90 + Docs Cycle 91-95
Day 10: Deployment Cycle 96-100
Day 11: Monitoring + Go-Live
Day 12: Buffer for issues
Total: 10-12 calendar days (vs. 40 days if sequential!)
Speedup: 3.8x through parallelization
```
## Resources Needed
**Team Members:** 5
- 1 Backend specialist (confident with Convex + TypeScript)
- 1 Frontend specialist (Astro + React + TypeScript)
- 1 Quality specialist (testing + audits)
- 1 Design/Documentation specialist (UI/UX + technical writing)
- 1 Orchestrator (this agent!)
**Infrastructure:** Already in place ✅
- Convex Cloud (production)
- Cloudflare Pages (frontend hosting)
- Resend (email)
- Better Auth (authentication)
- Astro + React (frontend stack)
**Budget:** $0 (all tools already subscribed + included)
## What's Blocked Until Wave 1 Is Done
Wave 1 is a **critical path blocker** for everything else:
| Wave | Name | Blocked Until | Reason |
| ---- | ------------------ | ------------- | -------------------------------- |
| 2 | Monetization | Wave 1 done | Need creators first |
| 3 | AI Agents | Wave 1 done | Need authenticated users |
| 4 | API | Wave 1 done | Need API keys (requires creator) |
| 5 | E-commerce | Wave 1 done | Need workspace for products |
| 6 | Community | Wave 1 done | Need creators + teams |
| 7 | Advanced Analytics | Wave 1 done | Need user activity data |
**This makes Wave 1 the highest-priority work.**
## What's NOT in Wave 1 (Intentional)
These features are **intentionally scoped to Wave 2+:**
- **Monetization:** No Stripe, no products, no pricing
- **AI Agents:** No agent deployment, no clones
- **Advanced analytics:** No detailed dashboards
- **Advanced team permissions:** No granular controls
- **Content creation:** No editor, no publishing
- **Community features:** No forums, no messaging
- **Blockchain:** No token minting, no smart contracts
**Wave 1 is purely onboarding.** Everything else is Wave 2+.
## Next Immediate Steps
### For Agent-Backend (Start Now)
1. Read: `/wave1-onboarding-vision.md` (entity types + events)
2. Read: `/wave1-specialist-assignments.md` (your responsibilities)
3. Start: Cycle 11 (Extend creator entity type in schema.ts)
4. Goal: Schema ready by end of day
### For Agent-Frontend (Start Day 3)
1. Read: `/wave1-onboarding-vision.md` (onboarding flow)
2. Read: `/wave1-specialist-assignments.md` (your components)
3. Review: `/one/knowledge/ontology.md` (understand thing types)
4. Wait: Until backend schema is ready (day 2)
5. Start: Cycle 31 (SignupForm component)
6. Goal: Components built by end of week
### For Agent-Quality (Start Day 8)
1. Read: `/wave1-specialist-assignments.md` (test strategy)
2. Review: Completed backend code
3. Review: Completed frontend code
4. Start: Cycle 81 (Backend unit tests)
5. Goal: All tests passing by day 10
### For Agent-Designer (Start Now - Design, Day 9 - Docs)
1. Read: `/wave1-onboarding-vision.md` (flow diagram + personas)
2. Read: `/wave1-specialist-assignments.md` (deliverables)
3. Start: Design wireframes now (parallel work)
4. Start: Documentation on day 9
5. Goal: All design + docs complete by day 10
### For Agent-Director (Active Now - That's Me!)
1. ✅ Complete Phase 1 validation (done)
2. ✅ Generate 3 planning documents (done)
3. ➜ Monitor Cycle 11-30 (backend progress)
4. ➜ Validate Gate 2 at Cycle 30
5. ➜ Monitor all specialist progress daily
6. ➜ Resolve blockers immediately
7. ➜ Validate success at each gate
## File Locations
All planning documents are in `/one/things/plans/`:
1. **`wave1-onboarding-vision.md`** (7,500 words)
- Read this first for context
- Contains user personas + flow diagram + success metrics
- Share with stakeholders for approval
2. **`wave1-onboarding-100-cycles.md`** (12,000 words)
- Complete breakdown of all 100 cycles
- Each cycle has task, deliverable, dependencies, time estimate
- Reference throughout execution
3. **`wave1-specialist-assignments.md`** (10,000 words)
- Specialist role + responsibilities
- Detailed task breakdown for each specialist
- Success criteria + deliverables checklist
- Hand to each specialist
4. **`wave1-orchestration-summary.md`** (this file)
- High-level overview
- Timeline + resource summary
- Next steps + decision gates
- Reference for executive updates
## Executive Summary for Stakeholders
**What:** Creator Onboarding (Wave 1 - Critical Path)
**Why:** No one can use ONE platform without onboarding
**Timeline:** 10-12 calendar days (10 days of work × 5 people = 50 person-days effort, parallelized into 10-12 calendar days)
**Team:** 5 specialists (backend, frontend, quality, design, orchestrator)
**Cost:** $0 (existing infrastructure + tools)
**Status:** ✅ Ready to start immediately
**Success Criteria:**
- ✅ Creator can sign up in < 15 minutes
- ✅ 80%+ complete onboarding
- ✅ Mobile responsive, accessible, secure
- ✅ Live in production by day 12
**Blockers:** None - all prerequisites met
**Risk Level:** Low (straightforward CRUD + forms + email)
## How to Track Progress
**Daily (During Standup):**
- Each specialist: "What cycles did I complete? What's blocking me?"
- Director: "Any risks or dependencies?"
**Weekly (Friday):**
- Review actual vs. planned cycles
- Adjust timeline if needed
- Plan next week
**Gateways (at Cycle 10, 30, 70, 90, 100):**
- Director validates success criteria
- Team meeting to celebrate + plan next phase
## Estimated Velocity
**Based on ontology alignment + straightforward CRUD work:**
| Specialist | Cycles/Day | Days | Total Cycles |
| ----------- | -------------- | ---- | ---------------- |
| Backend | 4 | 10 | 40 |
| Frontend | 3.5 | 6 | 20 |
| Quality | 3.3 | 3 | 10 |
| Design/Docs | 2 | 5 | 10 |
**Confidence:** High
- Clear specifications
- Existing infrastructure
- Well-defined scope
- Skilled team
**Risks:** Low-medium
- Email delivery (common gotcha)
- Mobile responsiveness (timing)
- Rate limiting edge cases
## What Success Looks Like on Day 12
**Live metrics:**
- Homepage shows: "Sign up now"
- Signup form: Working, email + password + OAuth
- Email verification: Code sent within 30s, verified instantly
- Profile form: Name, avatar, bio, niche complete
- Workspace: Created with unique slug
- Team: Can invite members, they get email, can accept
- Wallet: Optional connect button (can be skipped)
- Dashboard: New creators see onboarding checklist
- Analytics: Funnel showing completion rates
- Monitoring: Errors tracked, performance good
**Team feeling:**
- "We just built the foundation for the entire platform"
- "Wave 2 is now unblocked"
- "Creators can now register and use ONE"
**Status:** ✅ Ready for Implementation
**Next Action:** Assign specialists and start Cycle 11
**Expected Completion:** 10-12 calendar days from start
**Wave 1 Success:** CERTAIN (all pieces aligned)