# TekDek Quick Reference Brainstorm

**Last Updated**: 2026-04-11  
**Purpose**: One-page overview for fast iteration and decision-making  
**Full Docs**: See `/knowledge/` folder for detailed strategy

---

## TL;DR: What Is TekDek?

**Narrative-driven dev education platform** where personas are characters, content is a storyline, and the community watches (and learns from) the drama.

| Layer | What | Purpose |
|-------|------|---------|
| **Business** | Multi-platform content aggregation | Track where personas publish, monetize |
| **Technical** | Stack Legion site + persona agents | Deliver education at scale |
| **Narrative** | Character arcs, conflicts, drama | Keep audiences engaged and invested |

---

## The Model (Replicable Across Industries)

**Stack Legion Dev (now)** → **DIY/Fitness/Finance (later)**

Core: Personas + Storylines + Multi-platform Publishing

---

## Key Numbers / Status

- **Personas planned**: 5–10 for MVP
- **Personas active**: 1 (Brick, in development)
- **Narrative arcs planned**: TBD
- **Stack Legion dev status**: External team (in progress)
- **Launch target**: Q3 2026 (estimated)

---

## Critical Path (Next 30 Days)

### Week 1
- [ ] Finalize Brick profile (expertise, relationships, origin story)
- [ ] Create first narrative arc (3–6 months, key beats)
- [ ] Draft 3–5 additional persona profiles (quick sketches)

### Week 2–3
- [ ] Publish 2–3 Brick articles/posts (test voice consistency)
- [ ] Gather feedback (does the voice land?)
- [ ] Finalize content curation workflow

### Week 4
- [ ] Plan second persona (choose from roster sketches)
- [ ] Begin persona agent prototyping
- [ ] Document lessons from Brick

---

## Persona Roster (First Wave Sketches)

### ✅ Brick
- **Expertise**: [TBD with Glytcht]
- **Voice**: Rough, gruff, honest
- **Status**: Prototype, active development

### 🔄 [Persona 2]
- **Name**: [TBD]
- **Expertise**: [e.g., Frontend/React]
- **Voice**: [e.g., Teaching-focused, optimistic]
- **Status**: Concept

### 🔄 [Persona 3]
- **Name**: [TBD]
- **Expertise**: [e.g., DevOps/Cloud]
- **Voice**: [e.g., Technical, pragmatic]
- **Status**: Concept

### 🔄 [Persona 4]
- **Name**: [TBD]
- **Expertise**: [e.g., Full-stack, building in public]
- **Voice**: [e.g., Entrepreneurial, conversational]
- **Status**: Concept

### 🔄 [Persona 5]
- **Name**: [TBD]
- **Expertise**: [e.g., Design/UX for devs]
- **Voice**: [e.g., Approachable, visual]
- **Status**: Concept

---

## Narrative Arc Ideas (Brainstorm)

### Arc 1: [The PHP vs Node Debate]
- **Duration**: 3 months
- **Characters**: Brick + [Frontend persona]
- **Beats**: 
  - Week 1: They disagree on a blog post
  - Week 4: Each writes a "why I'm right" article
  - Week 8: Community takes sides, challenges emerge
  - Week 12: They collaborate on a comparison, find common ground
- **Engagement**: Forum debates, code challenges, "which do you prefer" polls
- **SEO play**: "PHP vs Node" trending

### Arc 2: [The Learning Journey]
- **Duration**: 6 months
- **Characters**: [New persona learning in public]
- **Beats**: Monthly tutorials documenting real learning
- **Engagement**: Community offers help, feedback, mentorship
- **Educational value**: Shows vulnerability, demystifies expert journey

### Arc 3: [The Collaboration]
- **Duration**: 3 months
- **Characters**: [Multiple personas] building something together
- **Engagement**: Community follows the build, participates in decisions
- **Educational value**: Real-world project workflow

---

## SEO & Growth Hooks

### Trending Topics (Align Storylines)
- New framework releases (React 19, Next.js updates, etc.)
- Industry events (conferences, keynotes)
- Common dev pain points (database choices, deployment, testing)

### Content Gaps (What's Missing?)
- Tutorials that bridge opinionated perspectives
- Learning journey documentation (from beginner to expert)
- Real-world failure case studies
- Inter-persona collaborations (rare, high-value)

### Engagement Levers
- **Conflict**: "Here's why [Persona A] is wrong about X"
- **Collaboration**: "We built X together, here's how we disagreed"
- **Learning**: "I failed at Y, here's what I learned"
- **Community**: "We asked the community, here's what they said"

---

## Tool Checklist (What We Need)

### MVP (Must Have)
- [x] Persona management (docs + knowledge base)
- [x] Narrative planning (docs + spreadsheet)
- [ ] Content curation workflow (form + approval)
- [ ] Voice guide (per persona)
- [ ] Content log (where did X publish?)

### Phase 2 (Nice-to-Have)
- [ ] Persona agent framework (AI content generation)
- [ ] Content syndication (pull from independent platforms)
- [ ] Analytics dashboard (engagement per persona)

### External (Stack Legion Team)
- [ ] Persona Portal
- [ ] Community & gamification
- [ ] Analytics integration

---

## Open Questions for Glytcht

1. **Brick's specialty**: Backend? DevOps? Full-stack? Something else?
2. **Brick's origin**: Why did he start teaching? What's his story?
3. **Roster diversity**: What expertise areas matter most for launch?
4. **Conflicts**: Any natural rivalries between personas you envision?
5. **Collaborations**: Any planned partnerships or team-ups?
6. **Timeline**: Are we targeting Q3 for launch, or flexible?
7. **Revenue**: Membership tiers? Course pricing? Revenue share with personas?
8. **Budget**: Tools we should buy vs. build?

---

## Decisions Made

- ✅ Multi-platform content model (personas own their channels)
- ✅ Narrative-driven engagement (drama + education)
- ✅ Human-curated content (quality + authenticity)
- ✅ Replicable template (DIY/fitness/finance later)
- ✅ Stack Legion as central hub (external dev, we manage personalities)

---

## Decisions Pending

- 🔲 Brick's expertise/specialty
- 🔲 Exact persona roster (who are the other 4–9?)
- 🔲 First narrative arc details
- 🔲 Revenue model specifics (membership pricing, course costs)
- 🔲 Launch date / MVP definition
- 🔲 Build vs. buy decisions on tools

---

## Metrics to Track

### Community Health
- Active member base
- Challenge participation
- Cross-persona collaboration

### Narrative Health
- Persona storyline engagement (shares, comments)
- User investment in characters
- Viewer retention

### Business Health
- Monthly recurring revenue
- Course enrollment
- Traffic growth

---

## Key Insight

> The narrative engine IS the moat. 
> Any platform can deliver tutorials. 
> TekDek delivers tutorials as part of a story people care about.

That's what makes it defensible, replicable, and engaging.

---

## Next Session

Be ready to discuss:
1. Brick's profile (expertise, origin)
2. Initial persona roster (quick 5-person sketch)
3. First narrative arc (beats, engagement hooks)
4. Content curation workflow (how we vet before publish)
5. Timeline & milestones
