30 KiB
30 KiB
TekDek Master Project Plan
Document: Master Project Roadmap & Requirements
Version: 1.0
Created: 2026-04-11
Status: ACTIVE — Guides both Development Team and TekDek Management
Owner: Glytcht (Product/Client), ParzivalTD (TekDek Operations Manager)
Executive Summary
TekDek is a narrative-driven developer education platform with two parallel execution tracks:
| Track | Owner | Deliverable | Purpose |
|---|---|---|---|
| Development (Portal) | External/Dev Team | Article publishing platform, community, APIs | Content delivery, monetization, user engagement |
| Management (OpenClaw) | TekDek (ParzivalTD) | Persona roster, narrative engine, content monitoring | Character operations, storyline tracking, curation |
Critical: The two tracks are interdependent. Portal can't fully function without management defining personas and storylines. Management can't operate at scale without portal infrastructure.
This document specifies:
- What each team delivers, in what phase
- When they deliver (timeline)
- Dependencies between deliverables
- Success criteria for each phase
- Checkpoints where decisions must be made
Project Vision (Reference)
Core Thesis: Technical education + character-driven entertainment = sticky, differentiated community
Three Layers:
- Business: Multi-platform content aggregation, monetization, community
- Technical: Central hub (Stack Legion), persona agents, syndication
- Narrative: Character arcs, conflicts, drama = engagement driver
Replicable Template: Dev → DIY → Fitness → Finance
Phase Overview
Phase 0: Discovery & Planning (NOW - Week 4)
↓
Phase 1: Foundational Development (Week 5 - Week 12)
↓
Phase 2: MVP Launch (Week 13 - Week 16)
↓
Phase 3: Scale & Iteration (Week 17 - Week 24)
↓
Phase 4: Expansion (Week 25+)
Phase 0: Discovery & Planning (NOW - Week 4)
Purpose
Lock in product definition, persona prototypes, narrative framework, and team specifications before major development begins.
TekDek Management (OpenClaw) Deliverables
Strategy Documents (✅ DONE)
- TekDek-Strategy.md — Vision, layers, persona model, narrative engine
- Tool-Requirements.md — Critical path tools, build/buy decisions
- TekDek-Brainstorm-Reference.md — One-page quick reference
Persona Framework (IN PROGRESS)
- Brick-Profile.md — Prototype persona (rough, relatable, honest)
- Voice Guide Templates — Standardized persona documentation
- 4–9 Additional Persona Sketches — Quick profiles for wave 1 roster
Narrative Framework (PENDING)
- Narrative Arc Template — Standard structure for arcs
- Arc 1 Definition — First storyline (beats, characters, engagement hooks)
- Content Calendar Framework — How content ties to narrative beats
Decision Checkpoints (PENDING)
- Brick's Technical Specialty (backend? DevOps? Full-stack?)
- Initial Persona Roster (who are personas 2–10?)
- Primary Narrative Arc (what drives engagement in wave 1?)
- Revenue Model (membership tiers, course pricing, persona share)
- Launch Target Date (Q3? Q4 2026?)
Monitoring System Design (PENDING)
- Persona Roster System Spec (what data we track per persona)
- Narrative State Tracker Spec (how we measure character evolution)
- Content Monitor Spec (where did X publish, engagement, voice consistency)
- API Integration Points (where portal calls us)
Development Team Deliverables
Portal Architecture & Planning (ONGOING)
- Portal tech stack finalized
- Database schema (preliminary)
- API design (who calls what, in what format)
- Authentication/authorization design
- Content publishing workflow
- Community/gamification architecture
- Analytics requirements
Phase 0 Dev Deliverables:
- Technical requirements document (what portal must support)
- API contract draft (for management system integration)
- Database schema (draft, subject to change)
- Development timeline (realistic sprint breakdown)
Questions for Dev Team:
- What's the portal's tech stack?
- Can you provide an API surface for external systems (like OpenClaw) to query persona data and sync published content?
- What's your estimated MVP launch date?
- Do you need any character/persona data from us to start building?
Deliverables by Week
| Week | TekDek Management | Development | Checkpoint |
|---|---|---|---|
| Week 1 | Finalize Brick profile; plan first arc; sketch 5 personas | Portal architecture draft; API planning | Brick locked in? |
| Week 2–3 | Publish Brick articles (test voice); finalize curation workflow | Portal prototype/demo; schema draft | First content pieces published? |
| Week 4 | Persona roster system spec; monitoring system design | API draft; integration points defined | All decision checkpoints hit? |
Success Criteria for Phase 0
- ✅ Brick profile complete and tested (voice consistency across 2–3 platforms)
- ✅ 5 additional personas sketched and agreed upon
- ✅ First narrative arc detailed with content calendar
- ✅ Content curation workflow finalized
- ✅ Persona roster system spec designed (API-ready)
- ✅ Development team has clear technical requirements
- ✅ All major decisions made (personas, narrative, revenue, launch date)
Phase 1: Foundational Development (Week 5 - Week 12)
Purpose
Build core systems, test persona voice consistency, begin content production, establish the content/narrative feedback loop.
TekDek Management Deliverables
Persona System (Week 5–8)
- Build Persona Roster System in OpenClaw (database + interface)
- Store: Profile, voice guide, system prompt, relationships, narrative state
- Support: Versioning, history, character evolution tracking
- Onboard personas 2–3 (create detailed profiles, develop voices)
- Persona Agent Framework (test AI drafting in persona voices)
- Voice Consistency Testing (publish 2 articles per persona, gather feedback)
Narrative System (Week 6–10)
- Build Narrative Arc Tracker in OpenClaw
- Store: Arc timeline, beats, character involvement, content tie-ins
- Support: Status tracking, engagement metrics, arc performance
- Content Calendar (synchronize article publication with narrative beats)
- Storyline & Beat Planning Tool (template for planning future arcs)
- Arc 1 Launch (execute first storyline with Brick + persona 2)
Content Monitoring & Curation (Week 7–12)
- Build Content Monitor
- Track: Where did X publish, when, engagement, voice consistency
- Support: Sync with portal (when APIs ready)
- Finalize Curation Workflow
- Intake (persona generates draft)
- Review (check voice consistency, narrative fit, technical accuracy)
- Approve/Reject with feedback
- Schedule publication
- Integration Planning (define API calls to portal)
Content Production (Week 5–12)
- Brick: Publish 4–6 articles (tutorial series, voice consistency test)
- Persona 2: Publish 2–3 articles (test voice, establish expertise)
- Persona 3: Publish 1–2 articles (prototype additional voice)
- All content: Curation → approval → schedule → publish
Analytics & Tracking (Week 9–12)
- Narrative Arc 1 Performance Metrics
- Views, engagement, user retention
- Did the conflict/collaboration resonate?
- What drove traffic, what didn't?
- Persona Voice Consistency Feedback
- Does Brick's voice land across platforms?
- Which personas need voice refinement?
- Content-to-Arc Correlation
- Did content published during narrative beats drive engagement?
Development Team Deliverables
Portal MVP Build (Week 5–12)
- User authentication & authorization
- Article publishing interface (draft → publish workflow)
- Article display (on Stack Legion site)
- Tagging/categorization system
- Basic community features (comments, user profiles)
- Gamification skeleton (challenges, points tracking)
- Analytics hooks (track views, engagement, user behavior)
API Development (Week 8–12)
- Persona API (
GET /persona/{id}→ return profile, system prompt, voice guide) - Content sync API (
POST /content/published→ sync when articles go live) - Analytics API (
GET /analytics/article/{id}→ return engagement) - Narrative API (
GET /narrative/arc/{id}→ return arc beats, status) - API documentation & testing
Integration Readiness (Week 10–12)
- Test data flow: OpenClaw → Portal (personas, content, analytics)
- Error handling & retry logic
- Rate limiting & security
- Mock integration with management system
Deliverables by Week
| Week | TekDek Management | Development | Output/Milestone |
|---|---|---|---|
| Week 5 | Build persona roster; onboard personas 2–3; publish Brick article 1 | Portal auth, publishing interface | First article live |
| Week 6 | Narrative arc tracker; arc 1 planning; publish Brick article 2 | Community features skeleton | Arc structure locked |
| Week 7 | Content monitor; curation workflow finalized | Gamification foundation | Curation system tested |
| Week 8 | Persona agent prototyping; persona 2 articles; API integration planning | API design complete, begin implementation | Multiple voices tested |
| Week 9 | Analytics dashboard; arc 1 performance tracking | API endpoints 50% complete | Early metrics available |
| Week 10 | Voice consistency analysis; content calendar Q2; API integration testing | API complete, integration testing | Systems talk to each other |
| Week 11 | Gather feedback; refine personas/narratives; publish persona 3 | Portal polish, edge case handling | Feedback incorporated |
| Week 12 | Arc 1 retrospective; decide on personas 4–5; plan Arc 2 | Portal MVP ready for launch | Go/no-go for Phase 2 |
Success Criteria for Phase 1
- ✅ 3 personas fully onboarded with consistent voices (tested across platforms)
- ✅ 8–10 articles published (mix of Brick, persona 2, persona 3)
- ✅ Arc 1 live and driving engagement (measurable views, comments, user retention)
- ✅ Content monitor tracking all publications and engagement
- ✅ Persona roster system operational in OpenClaw
- ✅ Portal MVP publishing articles and showing basic community features
- ✅ APIs operational and tested (management ↔ portal integration)
- ✅ Early metrics show voice consistency resonates with readers
- ✅ Curation workflow proven (intake → review → approve → publish working smoothly)
- ✅ Development team and management team synchronized on technical approach
Phase 2: MVP Launch (Week 13 - Week 16)
Purpose
Launch public beta, establish community, prove engagement model (narrative + education), gather user feedback.
TekDek Management Deliverables
Persona Expansion (Week 13–16)
- Onboard personas 4–5 (bring them to same maturity as personas 1–3)
- Document consistency rules for each persona
- Lock in all persona relationships (allies, rivals, neutral)
Narrative Expansion (Week 13–16)
- Arc 1 conclusion (wrap up the conflict/collaboration)
- Arc 2 launch (new storyline with personas 2–4)
- Content calendar through end of Q2 (articles tied to narrative beats)
Content Production (Week 13–16)
- Publish 15–20 articles total (maintained across all active personas)
- Community engagement tracking (comments, discussions, user participation)
- SEO/trending alignment (capitalize on current tech trends)
Platform Integrations (Week 13–16)
- BookStack integration (if needed for persona knowledge bases)
- Gitea integration (if personas host code challenges on Gitea)
- Social media syncing (where personas independently publish)
Launch Coordination (Week 13–16)
- Marketing plan (how we announce Stack Legion launch)
- User onboarding flow (how new users discover content)
- Community moderation guidelines (how we manage discussions)
Development Team Deliverables
Portal Beta Launch (Week 13–16)
- Public facing site (Stack Legion live with articles, community, challenges)
- User registration & member tiers
- Challenge system (gamification live)
- Analytics dashboard (views, engagement, user behavior)
- Content moderation tools
- Mobile-responsive design
Performance & Scaling (Week 13–16)
- Load testing (can the site handle 1K+ concurrent users?)
- Database optimization (content queries, user queries)
- Caching strategy (for high-traffic content)
- CDN integration (if needed for global distribution)
API Maturity (Week 13–16)
- API versioning & backward compatibility
- Rate limiting & quotas
- Error responses & documentation
- Monitoring & alerting (are the APIs healthy?)
Deliverables by Week
| Week | TekDek Management | Development | Output |
|---|---|---|---|
| Week 13 | Arc 1 conclusions; personas 4–5 onboarding; marketing plan | Portal beta deployment; user registration live | Beta site live |
| Week 14 | Arc 2 launch; publish 3–4 articles; community moderation active | Challenge system; gamification; analytics | Users signing up |
| Week 15 | Community engagement metrics; SEO/trending alignment; content calendar Q3 | Performance optimization; load testing complete | First engagement data |
| Week 16 | Retrospective; success metrics; plan Phase 3 priorities | Beta feedback incorporated; go/no-go for public launch | Lessons documented |
Success Criteria for Phase 2
- ✅ Stack Legion MVP live with 5 personas, multiple articles, active community
- ✅ 500+ registered members, 100+ challenge participants
- ✅ Arc 2 live and generating engagement (measurable user retention)
- ✅ Site handles 1K+ concurrent users without degradation
- ✅ SEO foundation (searchable content, organic traffic trickling in)
- ✅ All APIs stable and documented
- ✅ Content quality remains high (curation workflow working)
- ✅ Narrative coherence maintained (users understand the storyline)
- ✅ Revenue model validated (at least 50% conversion to membership or course)
- ✅ Team feedback: "This is working, let's scale it"
Phase 3: Scale & Iteration (Week 17 - Week 24)
Purpose
Grow community, expand persona roster, launch multiple narrative arcs in parallel, prove replication template with second vertical (DIY/fitness/finance).
TekDek Management Deliverables
Full Persona Roster (Week 17–24)
- Onboard personas 6–10 (complete wave 1)
- Develop 3–5 personas for wave 2 (next vertical, e.g., DIY)
- Create persona templates & playbooks (reusable for future verticals)
Narrative Expansion (Week 17–24)
- 3–4 narrative arcs in parallel
- Seasonal themes (summer projects, Halloween code challenges, etc.)
- Community-driven narratives (user votes on conflict outcomes)
- Cross-persona collaborations (limited edition tutorials)
Content Production & Syndication (Week 17–24)
- 40–60 articles published across all personas
- Integration with persona independent platforms (YouTube syncing, blog feeds)
- Content recommendation engine (which articles connect to which narratives?)
- Guest contributions (invite external experts to write as guests)
Analytics & Growth (Week 17–24)
- Cohort analysis (which personas drive retention? growth?)
- Content performance (what topics resonate?)
- Narrative arc ROI (did this arc drive engagement?)
- SEO growth (target 10K+ monthly organic visitors)
Vertical 2 Planning (Week 17–24)
- Choose second vertical (DIY? Fitness? Finance?)
- Recruit 3–5 personas for vertical 2
- Adapt narrative model for new domain
- Plan launch (week 21+)
Development Team Deliverables
Platform Scaling (Week 17–24)
- Microservices architecture (if needed for scale)
- Database sharding (split data across instances)
- Cache layer optimization (Redis, etc.)
- Search indexing (Elasticsearch for full-text search across 1000+ articles)
Advanced Features (Week 17–24)
- Persona Portal MVP (personas self-publish, manage their section)
- Advanced gamification (leaderboards, achievements, cross-challenge tracking)
- Recommendation engine (suggest articles based on user interest)
- Analytics dashboard for personas (their traffic, engagement, growth)
Revenue Systems (Week 17–24)
- Course hosting (integrate with Udemy, Teachable, or custom)
- Membership tiers (free, basic, premium, VIP)
- Payment processing (Stripe, PayPal)
- Revenue sharing (pay personas from their content revenue)
- Merchandise/sponsorship integrations
API Expansion (Week 17–24)
- Persona Portal APIs (personas upload content, get analytics)
- Recommendation APIs (suggest articles based on user behavior)
- Revenue APIs (persona earnings, payments)
- Analytics APIs (detailed performance metrics)
Deliverables by Week
| Week | TekDek Management | Development | Output |
|---|---|---|---|
| Week 17 | Personas 6–10 onboarding; Arc 2 retrospective; Arc 3 planning | Microservices refactor begins; scaling architecture | Persona 6 live |
| Week 18–20 | Vertical 2 persona recruitment; 3 concurrent arcs live; 12+ articles published | Platform optimization; search indexing live; revenue system 50% | Multiple narratives active |
| Week 21 | Vertical 2 launch (DIY/fitness/finance); community growth tracking | Persona Portal beta; recommendation engine; revenue sharing | Second vertical goes live |
| Week 22 | Personas 6–10 all live; cross-vertical collaboration planning | Advanced gamification; analytics dashboards | 10 personas + 2 verticals |
| Week 23 | Content syndication live (pull from YouTube, blogs); SEO strategy | Course hosting; membership tiers; payment processing | Revenue streams active |
| Week 24 | Phase 3 retrospective; financial review; plan Phase 4 | Performance analysis; decision on Phase 4 priorities | Scaling validated |
Success Criteria for Phase 3
- ✅ 10,000+ active community members
- ✅ 10 personas across 2 verticals (Stack Legion Dev + DIY/Fitness/Finance)
- ✅ 150+ articles published, consistent 2K+ views per article
- ✅ 3–4 narrative arcs generating measurable engagement
- ✅ Monthly recurring revenue (MRR) from memberships + courses
- ✅ Platform handles 10K+ concurrent users
- ✅ SEO: 50K+ monthly organic visitors
- ✅ Persona Portal operational (personas self-manage content)
- ✅ Revenue sharing model working (personas earning)
- ✅ Replication template proven (second vertical launched successfully)
Phase 4: Expansion (Week 25+)
Purpose
Expand to 3–5 verticals, scale revenue, build moat through narrative depth, prepare for external partnerships.
TekDek Management Deliverables
Multi-Vertical Operations (Week 25+)
- 3–5 verticals live (Stack Legion Dev, DIY, Fitness, Finance, ?)
- 30–50 personas across all verticals
- 10–15 concurrent narrative arcs
- Specialized content calendars per vertical
Narrative Complexity (Week 25+)
- Cross-vertical storylines (dev personas collaborate with DIY personas, etc.)
- Annual narrative events (conflicts, resolutions, seasonal themes)
- User-driven narrative (community votes on story outcomes)
Monetization & Partnerships (Week 25+)
- Sponsorships (brands pay to appear in challenges, tutorials)
- Affiliate marketing (persona courses, tools, services)
- White-label opportunities (license the platform to other niches)
- API partnerships (external tools integrate with Stack Legion)
Development Team Deliverables
Enterprise-Grade Platform (Week 25+)
- Advanced analytics (cohort analysis, churn prediction, LTV)
- Internationalization (multi-language, multi-region support)
- White-label features (custom branding for partners)
- API marketplace (third-party integrations)
Decision Checkpoints (Critical Decisions)
Phase 0 (This Week – Week 4)
CHECKPOINT 1: Brick Finalization (Week 1)
- Decision: What is Brick's technical specialty?
- Why: Determines his first content, which templates his voice
- Action: Finalize Brick-Profile.md with specialty, origin story, relationships
- Blocker: Can't move forward without this
CHECKPOINT 2: Initial Persona Roster (Week 1–2)
- Decision: Who are personas 2–10?
- Why: Determines content calendar, narrative arc participants, expertise mix
- Action: Create detailed sketches for 5–9 personas
- Blocker: Can't plan arcs or content without roster
CHECKPOINT 3: First Narrative Arc (Week 2–3)
- Decision: What's Arc 1? (conflict? collaboration? learning journey?)
- Why: Determines content calendar, engagement hooks, which personas interact
- Action: Define Arc 1 with beats, timeline, characters, engagement hooks
- Blocker: Can't start Phase 1 content without arc definition
CHECKPOINT 4: Revenue Model (Week 3)
- Decision: Membership pricing? Course structure? Persona revenue share?
- Why: Informs what dev team builds (payment processing, dashboards)
- Action: Lock in revenue model specifics
- Blocker: Dev team needs this for Phase 1 planning
CHECKPOINT 5: Launch Target (Week 4)
- Decision: When is MVP launch? (Q3? Q4 2026?)
- Why: Informs sprint planning, resource allocation
- Action: Commit to a launch date, break into phases
- Blocker: Timeline drives all planning
Phase 1 (Week 5–12)
CHECKPOINT 6: Voice Consistency Validation (Week 8)
- Decision: Does Brick's voice actually work across platforms?
- Why: If not, we pivot before scaling
- Action: Analyze 2–3 Brick articles + social posts, gather reader feedback
- Blocker: Can't scale personas if voice doesn't work
CHECKPOINT 7: Arc 1 Engagement (Week 10)
- Decision: Is the narrative arc driving user engagement?
- Why: If not, we adjust narrative strategy
- Action: Review early metrics (views, comments, retention)
- Blocker: If arc isn't working, Phase 2 launch may be at risk
CHECKPOINT 8: Go/No-Go for Phase 2 (Week 12)
- Decision: Ready to launch MVP to public?
- Why: This is the major go/no-go moment
- Criteria:
- ✅ 3 personas with proven voice consistency
- ✅ 8–10 quality articles published
- ✅ Arc 1 showing engagement
- ✅ Portal MVP complete
- ✅ APIs operational
- Blocker: If any criterion fails, extend Phase 1
Phase 2 (Week 13–16)
CHECKPOINT 9: MVP Success Metrics (Week 16)
- Decision: Did MVP launch meet success criteria?
- Why: Informs Phase 3 scope (scale vs. pivot)
- Action: Analyze 500+ user feedback, engagement, revenue
- Blocker: If metrics are poor, reassess before scaling
Phase 3 (Week 17–24)
CHECKPOINT 10: Vertical 2 Launch Go/No-Go (Week 21)
- Decision: Is DIY/Fitness/Finance vertical ready to launch?
- Why: Critical validation that replication template works
- Action: Evaluate persona quality, content, arc planning
- Blocker: If template doesn't replicate well, scale differently
Dependency Map
Phase 0 → Phase 1 → Phase 2 → Phase 3 → Phase 4
↓ ↓ ↓ ↓ ↓
TekDek TekDek TekDek TekDek TekDek
Decisions Personas Content Expansion Scaling
↓ ↓ ↓ ↓ ↓
Dev Spec Dev Build Dev MVP Dev Scale Dev Partner
Critical Dependencies
| Blocker | Dependent | Risk |
|---|---|---|
| Brick profile not finalized | Can't publish first articles | Week 1 slip → cascade |
| First narrative arc undefined | Content calendar stalled | Creativity gap |
| Portal architecture delayed | APIs can't be designed | Integration stalled |
| Voice consistency fails (Week 8) | Can't scale personas | Entire narrative model at risk |
| Arc 1 engagement low (Week 10) | MVP launch risky | Community adoption may fail |
| APIs not operational (Week 12) | Portal + OpenClaw can't talk | Two separate systems |
Success Metrics & KPIs
Community Health
- Active users: 500 (Phase 2) → 5K (Phase 3) → 50K+ (Phase 4)
- Retention: 40%+ monthly active → 50%+ (Phase 3)
- Engagement: 2K+ views per article → 5K+ (Phase 3)
- Challenge participation: 10% of users → 30% (Phase 3)
Content & Narrative
- Articles published: 8–10 (Phase 1) → 15–20 (Phase 2) → 40–60 (Phase 3)
- Persona count: 3 (Phase 1) → 5 (Phase 2) → 10–50 (Phase 3–4)
- Narrative arc engagement: Comments/shares per arc beat
- Voice consistency: Reader perception (survey/feedback)
Business
- Monthly recurring revenue: $0 (Phase 1) → $5K (Phase 2) → $50K+ (Phase 3)
- Course enrollment: 50 (Phase 2) → 500 (Phase 3)
- Persona earnings: Transparent to each persona
- Cost per acquisition: < $10 per user (organic + community-driven)
Technical
- Site uptime: 99.5%+
- Page load time: < 2 seconds
- API response time: < 500ms
- Database query time: < 100ms
Risk Register & Mitigation
| Risk | Probability | Impact | Mitigation |
|---|---|---|---|
| Brick's voice doesn't resonate | Medium | High | Test early (week 5), adjust quickly |
| Narrative arc engagement is low | Medium | High | Have backup arc ready, pivot fast |
| Portal development slips | Medium | High | Weekly sync, clear dependencies |
| Persona burnout (can't maintain voice) | Low | Medium | Document everything, make AI assist |
| Community moderation crisis | Low | Medium | Clear guidelines, active moderation team |
| API integration complexity | Medium | Medium | Whiteboard early, test often |
| Personas 4–10 struggle with voice | Medium | Medium | Template from Brick, use AI drafting |
| SEO strategy fails | Low | Medium | Hire SEO consultant early (week 10+) |
Team Roles & Responsibilities
TekDek Management (Glytcht + ParzivalTD)
- Glytcht: Vision, decisions, content curation, final approval
- ParzivalTD: Operations, system design, tracking, coordination
Responsibilities:
- Define personas, voices, relationships
- Plan narrative arcs and storylines
- Approve all content (voice, accuracy, narrative fit)
- Coordinate with dev team on integration points
- Monitor engagement metrics and adjust
Development Team
- Tech Lead: Architecture, API design, system decisions
- Engineers: Build portal, APIs, infrastructure
- Ops/DevOps: Deployment, scaling, monitoring
Responsibilities:
- Build portal MVP with clear API contracts
- Ensure reliability and scalability
- Implement analytics and monitoring
- Support integration with OpenClaw management system
Success Requires
- Weekly sync: TekDek + Dev team (30 min)
- Clear spec: Management defines "what", dev defines "how"
- Early integration: APIs designed in Phase 0, tested in Phase 1
- Shared KPIs: Both teams aligned on success metrics
Open Questions for Dev Team
- Tech Stack: What's the portal built on? (Rails? Node? Django?)
- Database: PostgreSQL? MongoDB? What schema are you thinking?
- Timeline: What's your realistic MVP launch target?
- APIs: Can you design REST/GraphQL endpoints for persona data, content sync, analytics?
- Content workflow: Does the portal handle drafts → review → approval → publish?
- Gamification: Is challenge creation persona-authored or admin-created?
- Analytics: Can we hook into user behavior, content performance, revenue?
- Infrastructure: Are you hosting this yourselves or using cloud services?
- Scalability: What's the user ceiling before we need to scale?
- Monetization: How do you plan to handle memberships, courses, revenue sharing?
Open Questions for Glytcht
- Brick's specialty: What's his technical focus?
- Persona roster: Who are your 9 other personas?
- First arc: What conflict/collaboration kicks off the narrative?
- Revenue model: Membership pricing? Course prices? Persona share %?
- Launch date: Firm target or flexible?
- Curation load: How much time can you spend reviewing/approving content?
- Persona sourcing: Do you already know people, or recruit during Phase 1?
- Expansion timeline: When do you want to launch vertical 2?
Next Steps (This Week)
For Glytcht
- Finalize Brick's technical specialty
- Define initial 5–9 personas (quick sketches)
- Plan first narrative arc (beats, timeline, engagement hooks)
- Lock in revenue model basics
- Commit to launch date (Q3? Q4?)
- Set dev team sync (weekly, Tuesdays 2pm?)
For ParzivalTD (Me)
- Finalize Brick-Profile.md with specialty/origin/relationships
- Create Persona Template for personas 2–10
- Design Narrative Arc Template (reusable structure)
- Draft Content Curation Workflow (intake → approval → publish)
- Design Persona Roster System architecture (ready for portal integration)
- Schedule first dev team sync
For Development Team
- Review this Master Plan document
- Answer open questions above
- Propose Phase 0 deliverables on your end
- Design API contract (what we'll call, what you'll return)
- Commit to Phase 1 start date
Document Governance
Owner: Glytcht (product), ParzivalTD (operations)
Review Cycle: Weekly during Phase 0–2, bi-weekly Phase 3+
Update Authority: Glytcht (major), ParzivalTD (operational details)
Version Control: Git-tracked in /knowledge/ folder
Audience: Glytcht, Dev Team, TekDek Management
When to Update: After checkpoints, if timeline slips, if major decisions change
Closing
This is the roadmap. Both teams follow it. Glytcht owns decisions, I execute operations, dev team builds infrastructure.
The next 4 weeks (Phase 0) lock in everything needed for 12 weeks of confident execution.
If we hit Phase 1 success criteria and validate our approach, Phase 2 is a formality. If we don't, we learn fast and adjust.
Let's build this.