Phase 0: Complete strategy docs, project overview, status tracker, memory update
This commit is contained in:
OpenClaw
20
MEMORY.md
20
MEMORY.md
@@ -12,7 +12,25 @@
|
|||||||
- Responsibilities: persona guidance, brand/marketing, software dev, project management
|
- Responsibilities: persona guidance, brand/marketing, software dev, project management
|
||||||
|
|
||||||
## Known Projects
|
## Known Projects
|
||||||
- Persona Portal (publishing platform for personas) — early concept stage
|
- **Stack Legion Dev** — article-based developer education platform (external dev team building)
|
||||||
|
- **Persona Portal** — publishing/management platform for personas (in development)
|
||||||
|
- **OpenClaw Management Layer** — persona roster, narrative tracking, content monitoring (our side)
|
||||||
|
|
||||||
|
## Key Architecture Decisions
|
||||||
|
- OpenClaw = Character engine (persona agents, voice guides, narrative state)
|
||||||
|
- Portal = Content delivery (articles, community, monetization)
|
||||||
|
- Two teams: TekDek Management (Glytcht + ParzivalTD) and Development Team (same Glytcht, different hat)
|
||||||
|
- We are the client/stakeholder defining requirements for the dev team
|
||||||
|
|
||||||
|
## Files Map
|
||||||
|
- `/knowledge/TekDek-Master-Project-Plan.md` — Full execution roadmap (THE source of truth)
|
||||||
|
- `/knowledge/TekDek-Strategy.md` — Vision and model
|
||||||
|
- `/knowledge/Tool-Requirements.md` — What to build
|
||||||
|
- `/knowledge/personas/Brick-Profile.md` — First persona prototype
|
||||||
|
- `/PROJECT-OVERVIEW.md` — File guide and navigation
|
||||||
|
- `/PROJECT-STATUS.md` — Current phase status
|
||||||
|
- `/Master-Plan-Quick-Checklist.md` — Decision checklist for Glytcht
|
||||||
|
- `/TekDek-Brainstorm-Reference.md` — Quick reference
|
||||||
|
|
||||||
## TekDek Overview (Detailed)
|
## TekDek Overview (Detailed)
|
||||||
|
|
||||||
|
|||||||
185
Master-Plan-Quick-Checklist.md
Normal file
185
Master-Plan-Quick-Checklist.md
Normal file
@@ -0,0 +1,185 @@
|
|||||||
|
# TekDek Master Plan — Quick Checklist
|
||||||
|
|
||||||
|
**This Week (Phase 0 Decisions)**: 🔴 CRITICAL PATH
|
||||||
|
**Full Plan**: See `/knowledge/TekDek-Master-Project-Plan.md`
|
||||||
|
|
||||||
|
---
|
||||||
|
|
||||||
|
## YOUR DECISIONS THIS WEEK (Glytcht)
|
||||||
|
|
||||||
|
### 🔴 DECISION 1: Brick's Technical Specialty
|
||||||
|
**Why**: Templates his first articles, determines his voice in depth
|
||||||
|
**Options**: Backend? DevOps? Full-stack? Architecture? Database design?
|
||||||
|
**Action**: Pick one, I'll finalize his profile
|
||||||
|
**Deadline**: TODAY if possible
|
||||||
|
|
||||||
|
### 🔴 DECISION 2: Initial Persona Roster (Personas 2–10)
|
||||||
|
**Why**: Determines content calendar, arc participants, expertise mix
|
||||||
|
**Options**: 5–10 people (real people you know, or we recruit during Phase 1?)
|
||||||
|
**Action**: Sketch out 5–9 personas (name, expertise, rough voice idea)
|
||||||
|
**Deadline**: End of Week 1
|
||||||
|
|
||||||
|
### 🔴 DECISION 3: First Narrative Arc
|
||||||
|
**Why**: Drives all content scheduling and engagement
|
||||||
|
**Options**:
|
||||||
|
- PHP vs Node debate (Brick + Frontend persona clash)
|
||||||
|
- Learning journey (new persona builds in public)
|
||||||
|
- Collaboration (multiple personas build something together)
|
||||||
|
- Other?
|
||||||
|
**Action**: Pick arc, I'll plan beats and content calendar
|
||||||
|
**Deadline**: End of Week 2
|
||||||
|
|
||||||
|
### 🔴 DECISION 4: Revenue Model
|
||||||
|
**Why**: Dev team needs this to build payment processing
|
||||||
|
**Options**:
|
||||||
|
- Membership tiers (Free / $5/mo / $15/mo)
|
||||||
|
- Courses ($29–$99 each)
|
||||||
|
- Persona revenue share (70/30? 80/20?)
|
||||||
|
- Sponsorships?
|
||||||
|
**Action**: Rough numbers, I'll detail it
|
||||||
|
**Deadline**: End of Week 3
|
||||||
|
|
||||||
|
### 🔴 DECISION 5: Launch Target
|
||||||
|
**Why**: Everything else is scheduled around this
|
||||||
|
**Options**: Q3 2026? Q4 2026? Early 2027?
|
||||||
|
**Action**: Commit to date, I'll build sprint plan
|
||||||
|
**Deadline**: End of Week 4
|
||||||
|
|
||||||
|
---
|
||||||
|
|
||||||
|
## MY DELIVERABLES THIS WEEK (ParzivalTD)
|
||||||
|
|
||||||
|
- [x] TekDek-Strategy.md ✅
|
||||||
|
- [x] Tool-Requirements.md ✅
|
||||||
|
- [x] Brick-Profile.md (stub) ✅
|
||||||
|
- [x] TekDek-Brainstorm-Reference.md ✅
|
||||||
|
- [x] **TekDek-Master-Project-Plan.md** ✅ (THIS DOCUMENT)
|
||||||
|
- [ ] Finalize Brick-Profile.md (pending your decision #1)
|
||||||
|
- [ ] Persona Template (for personas 2–10)
|
||||||
|
- [ ] Narrative Arc Template
|
||||||
|
- [ ] Content Curation Workflow doc
|
||||||
|
- [ ] Persona Roster System spec (design)
|
||||||
|
|
||||||
|
---
|
||||||
|
|
||||||
|
## PHASE 0 TIMELINE
|
||||||
|
|
||||||
|
```
|
||||||
|
Week 1: Decisions 1–2 locked, Brick finalized, 5 personas sketched
|
||||||
|
Week 2: Decision 3 locked, Arc 1 planned, content calendar drafted
|
||||||
|
Week 3: Decision 4 locked, revenue model detailed
|
||||||
|
Week 4: Decision 5 locked, all templates + specs done, dev team sync
|
||||||
|
```
|
||||||
|
|
||||||
|
---
|
||||||
|
|
||||||
|
## PHASE OVERVIEW (REFERENCE)
|
||||||
|
|
||||||
|
| Phase | Timeframe | Goal | Team Lead |
|
||||||
|
|-------|-----------|------|-----------|
|
||||||
|
| **Phase 0** | NOW - Week 4 | Lock decisions, design systems | TekDek (Glytcht) |
|
||||||
|
| **Phase 1** | Week 5–12 | Build personas, test narrative, publish content | TekDek + Dev |
|
||||||
|
| **Phase 2** | Week 13–16 | MVP launch, public beta, validate model | Dev (Portal launch) |
|
||||||
|
| **Phase 3** | Week 17–24 | Scale to 10 personas, 2 verticals | TekDek (narrative expansion) |
|
||||||
|
| **Phase 4** | Week 25+ | 3–5 verticals, 50+ personas, enterprise scale | Both teams |
|
||||||
|
|
||||||
|
---
|
||||||
|
|
||||||
|
## CRITICAL SUCCESS FACTORS (PHASE BY PHASE)
|
||||||
|
|
||||||
|
### Phase 0 ✅ (This Week)
|
||||||
|
- Decisions locked
|
||||||
|
- Personas defined
|
||||||
|
- Arc 1 planned
|
||||||
|
- Dev team aligned
|
||||||
|
|
||||||
|
### Phase 1 ✅ (Week 5–12)
|
||||||
|
- Brick voice test (2–3 articles) ✅
|
||||||
|
- 3 personas live ✅
|
||||||
|
- Arc 1 live with content tied to beats ✅
|
||||||
|
- APIs operational ✅
|
||||||
|
- **Go/No-Go for Phase 2** (Week 12) ✅
|
||||||
|
|
||||||
|
### Phase 2 ✅ (Week 13–16)
|
||||||
|
- Stack Legion MVP public ✅
|
||||||
|
- 500+ users ✅
|
||||||
|
- Arc 1 generating engagement ✅
|
||||||
|
- Revenue streams working ✅
|
||||||
|
- **Go/No-Go for Phase 3** (Week 16) ✅
|
||||||
|
|
||||||
|
### Phase 3 ✅ (Week 17–24)
|
||||||
|
- 10 personas across 2 verticals ✅
|
||||||
|
- Multiple arcs in parallel ✅
|
||||||
|
- 10K+ monthly users ✅
|
||||||
|
- Replication template proven ✅
|
||||||
|
|
||||||
|
### Phase 4 (Week 25+)
|
||||||
|
- Scale to 3–5 verticals ✅
|
||||||
|
- 50+ personas ✅
|
||||||
|
- $50K+ MRR ✅
|
||||||
|
|
||||||
|
---
|
||||||
|
|
||||||
|
## QUESTIONS FOR DEV TEAM (FIRST SYNC)
|
||||||
|
|
||||||
|
1. Tech stack? (Rails? Node? Django?)
|
||||||
|
2. Realistic MVP launch date?
|
||||||
|
3. Can you design APIs for persona data, content sync, analytics?
|
||||||
|
4. What's the user scaling limit before we need microservices?
|
||||||
|
5. Payment processing / revenue sharing capability?
|
||||||
|
6. How do we integrate management system (OpenClaw) with portal?
|
||||||
|
|
||||||
|
---
|
||||||
|
|
||||||
|
## WEEKLY SYNC SCHEDULE (STARTING WEEK 1)
|
||||||
|
|
||||||
|
**TekDek (Glytcht + ParzivalTD) + Dev Team**
|
||||||
|
**When**: [TIME TBD]
|
||||||
|
**Duration**: 30 min
|
||||||
|
**Agenda**:
|
||||||
|
- Blockers
|
||||||
|
- Phase 0 checkpoint (week 1–4)
|
||||||
|
- Next week's deliverables
|
||||||
|
- Dependency updates
|
||||||
|
|
||||||
|
---
|
||||||
|
|
||||||
|
## NEXT STEP: RESPOND TO DECISIONS
|
||||||
|
|
||||||
|
Once you give me Decisions 1–3 (Brick specialty, 5 personas, first arc), I can:
|
||||||
|
1. Finalize all persona profiles
|
||||||
|
2. Plan content calendar through end of Q2
|
||||||
|
3. Design system architecture (what to build in OpenClaw)
|
||||||
|
4. Provide dev team with technical requirements
|
||||||
|
|
||||||
|
**Then we're off to the races.**
|
||||||
|
|
||||||
|
---
|
||||||
|
|
||||||
|
## FILES TO REVIEW
|
||||||
|
|
||||||
|
**Full Strategy**:
|
||||||
|
- `/knowledge/TekDek-Strategy.md` — Vision, layers, models
|
||||||
|
- `/knowledge/Tool-Requirements.md` — What to build
|
||||||
|
- `/knowledge/personas/Brick-Profile.md` — First persona (template)
|
||||||
|
- `/TekDek-Brainstorm-Reference.md` — Quick brain dump
|
||||||
|
|
||||||
|
**Master Execution**:
|
||||||
|
- `/knowledge/TekDek-Master-Project-Plan.md` — THIS. Read it.
|
||||||
|
|
||||||
|
**Session Log**:
|
||||||
|
- `/memory/2026-04-11-extended.md` — What we did today
|
||||||
|
|
||||||
|
---
|
||||||
|
|
||||||
|
## DECISION LOG
|
||||||
|
|
||||||
|
```
|
||||||
|
[ ] 1. Brick's specialty — PENDING
|
||||||
|
[ ] 2. Initial persona roster (5–9 people) — PENDING
|
||||||
|
[ ] 3. First narrative arc — PENDING
|
||||||
|
[ ] 4. Revenue model — PENDING
|
||||||
|
[ ] 5. Launch target date — PENDING
|
||||||
|
```
|
||||||
|
|
||||||
|
Once filled, we move to execution.
|
||||||
375
PROJECT-OVERVIEW.md
Normal file
375
PROJECT-OVERVIEW.md
Normal file
@@ -0,0 +1,375 @@
|
|||||||
|
# TekDek Project Overview & File Guide
|
||||||
|
|
||||||
|
**Last Updated**: 2026-04-11
|
||||||
|
**Status**: Phase 0 (Planning & Discovery)
|
||||||
|
**Owner**: Glytcht (Product/Client), ParzivalTD (Operations)
|
||||||
|
|
||||||
|
---
|
||||||
|
|
||||||
|
## What Is This?
|
||||||
|
|
||||||
|
This document maps the entire TekDek project strategy, files, and current status in one place. Use this to:
|
||||||
|
- Understand the project structure
|
||||||
|
- Find specific documents
|
||||||
|
- Track progress across phases
|
||||||
|
- Coordinate between teams
|
||||||
|
|
||||||
|
---
|
||||||
|
|
||||||
|
## Project Structure at a Glance
|
||||||
|
|
||||||
|
```
|
||||||
|
TekDek
|
||||||
|
├── Strategy Documents (What we're building)
|
||||||
|
├── Persona System (Who they are)
|
||||||
|
├── Narrative Engine (How we tell the story)
|
||||||
|
├── Content & Curation (What gets published)
|
||||||
|
├── Project Management (Timeline, phases, status)
|
||||||
|
└── Monitoring & Tracking (Where are we now?)
|
||||||
|
```
|
||||||
|
|
||||||
|
---
|
||||||
|
|
||||||
|
## Core Files by Purpose
|
||||||
|
|
||||||
|
### 📋 STRATEGY & VISION
|
||||||
|
|
||||||
|
**File**: `/knowledge/TekDek-Strategy.md` (7.3KB)
|
||||||
|
**Purpose**: Full vision statement, three layers, persona model, narrative engine
|
||||||
|
**Read when**: You want to understand the "why" and overall approach
|
||||||
|
**Key sections**:
|
||||||
|
- Executive summary
|
||||||
|
- The three layers (business, technical, narrative)
|
||||||
|
- Persona model details
|
||||||
|
- Narrative engine explanation
|
||||||
|
- Phase breakdown
|
||||||
|
- Success metrics
|
||||||
|
|
||||||
|
**File**: `/TekDek-Brainstorm-Reference.md` (6.8KB)
|
||||||
|
**Purpose**: One-page quick reference for fast decision-making
|
||||||
|
**Read when**: You need to make a quick decision or brief someone
|
||||||
|
**Key sections**:
|
||||||
|
- TL;DR
|
||||||
|
- Model overview
|
||||||
|
- Critical path (next 30 days)
|
||||||
|
- Persona roster sketches
|
||||||
|
- Narrative arc ideas
|
||||||
|
- Open questions
|
||||||
|
|
||||||
|
### 🎯 MASTER PROJECT PLAN
|
||||||
|
|
||||||
|
**File**: `/knowledge/TekDek-Master-Project-Plan.md` (30.3KB) 🔴 **START HERE**
|
||||||
|
**Purpose**: Complete roadmap for both TekDek Management and Development Team
|
||||||
|
**Read when**: You want to understand the full execution plan
|
||||||
|
**Key sections**:
|
||||||
|
- Phase overview (0–4, with timelines)
|
||||||
|
- Phase 0 deliverables (this week/month)
|
||||||
|
- Phase 1 deliverables (content, personas, narrative)
|
||||||
|
- Phase 2 deliverables (MVP launch)
|
||||||
|
- Phase 3 deliverables (scale & expansion)
|
||||||
|
- Phase 4 deliverables (multi-vertical)
|
||||||
|
- Decision checkpoints (when you must decide)
|
||||||
|
- Success criteria per phase
|
||||||
|
- Risk register & mitigation
|
||||||
|
- Open questions for dev team & you
|
||||||
|
|
||||||
|
**File**: `/Master-Plan-Quick-Checklist.md` (5.4KB)
|
||||||
|
**Purpose**: Your decision checklist for Phase 0
|
||||||
|
**Read when**: You need to know what decisions to make this week
|
||||||
|
**Key sections**:
|
||||||
|
- 5 critical decisions (Brick specialty, personas, arc, revenue, launch date)
|
||||||
|
- My deliverables this week
|
||||||
|
- Phase timeline
|
||||||
|
- Critical success factors
|
||||||
|
|
||||||
|
### 👥 PERSONA SYSTEM
|
||||||
|
|
||||||
|
**File**: `/knowledge/Tool-Requirements.md` (7.9KB)
|
||||||
|
**Section**: "Persona Management System"
|
||||||
|
**Purpose**: Spec for how we store, track, and manage personas
|
||||||
|
**What it defines**: Persona profile data model, voice guides, relationships, content history
|
||||||
|
|
||||||
|
**File**: `/knowledge/personas/Brick-Profile.md` (7KB)
|
||||||
|
**Purpose**: First persona prototype (template for personas 2–10)
|
||||||
|
**Read when**: You want to understand persona structure and voice consistency
|
||||||
|
**Key sections**:
|
||||||
|
- Profile (name, expertise, elevator pitch)
|
||||||
|
- Voice & tone guide (directness, vulnerability, authority, mentorship)
|
||||||
|
- Consistency rules (across blog, social, video, GitHub, Stack Legion)
|
||||||
|
- Consistency checklist (pre-publish review)
|
||||||
|
- Relationships (allies, rivals, neutral)
|
||||||
|
- Content log (where has he published)
|
||||||
|
- Character arc & evolution
|
||||||
|
- Agent configuration (for AI drafting)
|
||||||
|
|
||||||
|
### 📖 NARRATIVE SYSTEM
|
||||||
|
|
||||||
|
**File**: `/knowledge/Tool-Requirements.md` (7.9KB)
|
||||||
|
**Section**: "Storyline & Narrative Planning Tool"
|
||||||
|
**Purpose**: Spec for how we plan, track, and execute narrative arcs
|
||||||
|
**What it defines**: Arc timeline, beats, character involvement, content tie-ins, engagement hooks
|
||||||
|
|
||||||
|
**File**: [PENDING — Create during Phase 0]
|
||||||
|
**Name**: `Narrative-Arc-Template.md`
|
||||||
|
**Purpose**: Standard template for planning all narrative arcs
|
||||||
|
**Will include**: Arc structure, beat planning, content calendar tie-in, engagement hooks
|
||||||
|
|
||||||
|
### 🛠️ TOOLS & INFRASTRUCTURE
|
||||||
|
|
||||||
|
**File**: `/knowledge/Tool-Requirements.md` (7.9KB) 🔴 **KEY DOCUMENT**
|
||||||
|
**Purpose**: Complete spec of what tools we need to build/buy
|
||||||
|
**Read when**: You want to understand what systems support the strategy
|
||||||
|
**Key sections**:
|
||||||
|
- Persona Management System
|
||||||
|
- Storyline & Narrative Planning Tool
|
||||||
|
- Content Curation & Approval System
|
||||||
|
- Persona Agent Framework
|
||||||
|
- Content Syndication System
|
||||||
|
- Persona Portal (external dev)
|
||||||
|
- Community & Gamification (external dev)
|
||||||
|
- Analytics & Growth Dashboard
|
||||||
|
|
||||||
|
---
|
||||||
|
|
||||||
|
## Project Status & Tracking
|
||||||
|
|
||||||
|
### 📊 Current Phase: Phase 0 (Discovery & Planning)
|
||||||
|
|
||||||
|
**Timeline**: Now — Week 4 (through end of week)
|
||||||
|
**Goal**: Lock decisions, design systems, prepare for Phase 1
|
||||||
|
|
||||||
|
**Status**:
|
||||||
|
- ✅ Strategy documented
|
||||||
|
- ✅ Master project plan created
|
||||||
|
- 🔴 PENDING: Your 5 critical decisions
|
||||||
|
|
||||||
|
**File**: [See Master-Plan-Quick-Checklist.md above]
|
||||||
|
|
||||||
|
### 🗓️ Phase Timeline
|
||||||
|
|
||||||
|
| Phase | Dates | Goal | Status |
|
||||||
|
|-------|-------|------|--------|
|
||||||
|
| **Phase 0** | Now–Week 4 | Decisions & design | 🟡 IN PROGRESS |
|
||||||
|
| **Phase 1** | Week 5–12 | Build & test | 🔲 NOT STARTED |
|
||||||
|
| **Phase 2** | Week 13–16 | MVP launch | 🔲 NOT STARTED |
|
||||||
|
| **Phase 3** | Week 17–24 | Scale | 🔲 NOT STARTED |
|
||||||
|
| **Phase 4** | Week 25+ | Expand | 🔲 PLANNED |
|
||||||
|
|
||||||
|
### 📈 Success Metrics
|
||||||
|
|
||||||
|
**Phase 0** (End of this month):
|
||||||
|
- ✅ All 5 critical decisions made
|
||||||
|
- ✅ 5–9 personas defined
|
||||||
|
- ✅ First narrative arc planned
|
||||||
|
- ✅ Content curation workflow finalized
|
||||||
|
- ✅ Persona roster system designed
|
||||||
|
- ✅ Dev team has clear spec
|
||||||
|
|
||||||
|
**Phase 1** (Week 5–12):
|
||||||
|
- 3 personas with proven voice consistency
|
||||||
|
- 8–10 quality articles published
|
||||||
|
- Arc 1 live and engaging users
|
||||||
|
- Portal MVP complete
|
||||||
|
- APIs operational
|
||||||
|
|
||||||
|
**Phase 2** (Week 13–16):
|
||||||
|
- Stack Legion MVP public
|
||||||
|
- 500+ registered users
|
||||||
|
- Revenue generating
|
||||||
|
|
||||||
|
---
|
||||||
|
|
||||||
|
## Decision Log
|
||||||
|
|
||||||
|
### 🔴 DECISIONS NEEDED (THIS WEEK)
|
||||||
|
|
||||||
|
**Decision 1: Brick's Technical Specialty**
|
||||||
|
- [ ] Backend
|
||||||
|
- [ ] DevOps/Infrastructure
|
||||||
|
- [ ] Full-stack
|
||||||
|
- [ ] Architecture
|
||||||
|
- [ ] Database design
|
||||||
|
- [ ] Other: ________
|
||||||
|
|
||||||
|
**Decision 2: Initial Persona Roster (Personas 2–10)**
|
||||||
|
- [ ] Persona 2: ________ (Expertise: ________)
|
||||||
|
- [ ] Persona 3: ________ (Expertise: ________)
|
||||||
|
- [ ] Persona 4: ________ (Expertise: ________)
|
||||||
|
- [ ] Persona 5: ________ (Expertise: ________)
|
||||||
|
- [ ] Persona 6: ________ (Expertise: ________)
|
||||||
|
- [ ] ... (5–9 total)
|
||||||
|
|
||||||
|
**Decision 3: First Narrative Arc**
|
||||||
|
- [ ] Type: Conflict? Collaboration? Learning journey? Other?
|
||||||
|
- [ ] Characters: Which personas?
|
||||||
|
- [ ] Timeline: 3 months? 6 months?
|
||||||
|
- [ ] Engagement hook: What draws users in?
|
||||||
|
|
||||||
|
**Decision 4: Revenue Model**
|
||||||
|
- [ ] Membership pricing (Free / $X/mo)
|
||||||
|
- [ ] Course pricing ($X each)
|
||||||
|
- [ ] Persona revenue share (X% / Y%)
|
||||||
|
- [ ] Sponsorships / Other
|
||||||
|
|
||||||
|
**Decision 5: Launch Target**
|
||||||
|
- [ ] Q3 2026 (July–Sept)
|
||||||
|
- [ ] Q4 2026 (Oct–Dec)
|
||||||
|
- [ ] Q1 2027 (Jan–Mar)
|
||||||
|
- [ ] Other: ________
|
||||||
|
|
||||||
|
---
|
||||||
|
|
||||||
|
## Where Everything Lives
|
||||||
|
|
||||||
|
```
|
||||||
|
Workspace Root: /data/.openclaw/workspace/
|
||||||
|
|
||||||
|
├── PROJECT-OVERVIEW.md (THIS FILE)
|
||||||
|
├── Master-Plan-Quick-Checklist.md
|
||||||
|
├── TekDek-Brainstorm-Reference.md
|
||||||
|
│
|
||||||
|
├── /knowledge/
|
||||||
|
│ ├── TekDek-Strategy.md (FULL VISION)
|
||||||
|
│ ├── TekDek-Master-Project-Plan.md (FULL ROADMAP)
|
||||||
|
│ ├── Tool-Requirements.md (SPECS)
|
||||||
|
│ │
|
||||||
|
│ └── /personas/
|
||||||
|
│ ├── Brick-Profile.md (FIRST PERSONA)
|
||||||
|
│ ├── Persona-Template.md (FOR PERSONAS 2–10)
|
||||||
|
│ └── [Persona profiles as we create them]
|
||||||
|
│
|
||||||
|
├── /memory/
|
||||||
|
│ ├── 2026-04-11.md (DAILY LOG - BOOTSTRAP)
|
||||||
|
│ └── 2026-04-11-extended.md (FULL SESSION LOG)
|
||||||
|
│
|
||||||
|
├── MEMORY.md (LONG-TERM MEMORY)
|
||||||
|
├── SOUL.md (PARZIVAL'S IDENTITY)
|
||||||
|
├── IDENTITY.md (PROJECT IDENTITY)
|
||||||
|
├── USER.md (GLYTCHT PROFILE)
|
||||||
|
│
|
||||||
|
├── /skills/
|
||||||
|
│ ├── qmd/ (KNOWLEDGE BASE SEARCH)
|
||||||
|
│ ├── self-improving/ (AGENT LEARNING)
|
||||||
|
│ ├── bookstack/ (WIKI INTEGRATION)
|
||||||
|
│ └── gitea/ (GIT INTEGRATION)
|
||||||
|
│
|
||||||
|
└── [Other files...]
|
||||||
|
```
|
||||||
|
|
||||||
|
### Quick Navigation
|
||||||
|
|
||||||
|
**"I want to understand the full strategy"**
|
||||||
|
→ Start: `/knowledge/TekDek-Strategy.md` (15 min read)
|
||||||
|
|
||||||
|
**"I want to understand the execution plan"**
|
||||||
|
→ Start: `/knowledge/TekDek-Master-Project-Plan.md` (30 min read)
|
||||||
|
|
||||||
|
**"I need to make a decision"**
|
||||||
|
→ Start: `/Master-Plan-Quick-Checklist.md` (5 min read)
|
||||||
|
|
||||||
|
**"I want to see today's session notes"**
|
||||||
|
→ `/memory/2026-04-11-extended.md`
|
||||||
|
|
||||||
|
**"I want to understand the persona system"**
|
||||||
|
→ Start: `/knowledge/personas/Brick-Profile.md` (template)
|
||||||
|
|
||||||
|
**"I want to see what tools we need"**
|
||||||
|
→ `/knowledge/Tool-Requirements.md` (section: "Critical Path Tools")
|
||||||
|
|
||||||
|
---
|
||||||
|
|
||||||
|
## How to Review Files
|
||||||
|
|
||||||
|
### Recommended Reading Order
|
||||||
|
|
||||||
|
**First Pass** (30 minutes):
|
||||||
|
1. This file (PROJECT-OVERVIEW.md)
|
||||||
|
2. `/Master-Plan-Quick-Checklist.md`
|
||||||
|
3. `/TekDek-Brainstorm-Reference.md`
|
||||||
|
|
||||||
|
**Second Pass** (1 hour):
|
||||||
|
1. `/knowledge/TekDek-Strategy.md` (sections: Executive Summary, Vision, Three Layers)
|
||||||
|
2. `/knowledge/TekDek-Master-Project-Plan.md` (sections: Phase 0, Phase 1, Decision Checkpoints)
|
||||||
|
|
||||||
|
**Deep Dive** (2+ hours):
|
||||||
|
1. Full `/knowledge/TekDek-Master-Project-Plan.md`
|
||||||
|
2. `/knowledge/Tool-Requirements.md`
|
||||||
|
3. `/knowledge/personas/Brick-Profile.md`
|
||||||
|
|
||||||
|
### How to Use These Files
|
||||||
|
|
||||||
|
**For Decision-Making**:
|
||||||
|
- Read `/Master-Plan-Quick-Checklist.md`
|
||||||
|
- Make your 5 decisions
|
||||||
|
- Update the DECISION LOG (this file)
|
||||||
|
- Notify ParzivalTD
|
||||||
|
|
||||||
|
**For Phase Planning**:
|
||||||
|
- Go to `/knowledge/TekDek-Master-Project-Plan.md`
|
||||||
|
- Find your phase (Phase 0, 1, 2, etc.)
|
||||||
|
- Review deliverables, timeline, success criteria
|
||||||
|
- Coordinate with ParzivalTD on blockers
|
||||||
|
|
||||||
|
**For Progress Tracking**:
|
||||||
|
- Check `/memory/` for daily/session logs
|
||||||
|
- Review DECISION LOG (this file)
|
||||||
|
- Track phase status above
|
||||||
|
|
||||||
|
---
|
||||||
|
|
||||||
|
## Next Steps
|
||||||
|
|
||||||
|
### For Glytcht (You)
|
||||||
|
|
||||||
|
1. **Read** `/Master-Plan-Quick-Checklist.md` (5 min)
|
||||||
|
2. **Decide** on your 5 critical decisions (Decision 1–5)
|
||||||
|
3. **Notify** ParzivalTD when ready
|
||||||
|
4. **Review** `/knowledge/TekDek-Master-Project-Plan.md` for full context
|
||||||
|
5. **Schedule** weekly sync with dev team (TBD time)
|
||||||
|
|
||||||
|
### For ParzivalTD (Me)
|
||||||
|
|
||||||
|
1. ✅ Create all strategy documents
|
||||||
|
2. ✅ Create Master Project Plan
|
||||||
|
3. ✅ Create this overview file
|
||||||
|
4. 🔄 AWAITING: Your 5 decisions
|
||||||
|
5. Then: Finalize Brick profile, create persona templates, design systems
|
||||||
|
|
||||||
|
### For Development Team
|
||||||
|
|
||||||
|
1. Review `/knowledge/TekDek-Master-Project-Plan.md`
|
||||||
|
2. Answer open questions (tech stack, timeline, APIs)
|
||||||
|
3. Propose Phase 0 deliverables on your end
|
||||||
|
4. Schedule first sync with TekDek team
|
||||||
|
|
||||||
|
---
|
||||||
|
|
||||||
|
## File Maintenance
|
||||||
|
|
||||||
|
**This document** is your north star. Update it as:
|
||||||
|
- Decisions are made → Update DECISION LOG
|
||||||
|
- Phases complete → Update PROJECT STATUS
|
||||||
|
- New files are created → Update WHERE EVERYTHING LIVES
|
||||||
|
- New deliverables → Update by phase sections
|
||||||
|
|
||||||
|
**Commit frequency**: After major updates (decisions, phase completion)
|
||||||
|
**Review frequency**: Weekly during Phase 0–2, bi-weekly Phase 3+
|
||||||
|
|
||||||
|
---
|
||||||
|
|
||||||
|
## Questions?
|
||||||
|
|
||||||
|
Refer to:
|
||||||
|
- **"What do I decide?"** → `/Master-Plan-Quick-Checklist.md`
|
||||||
|
- **"When do I decide it?"** → `/knowledge/TekDek-Master-Project-Plan.md` → Decision Checkpoints
|
||||||
|
- **"How does this work?"** → `/knowledge/TekDek-Strategy.md`
|
||||||
|
- **"What gets built?"** → `/knowledge/Tool-Requirements.md`
|
||||||
|
|
||||||
|
---
|
||||||
|
|
||||||
|
## Document Version History
|
||||||
|
|
||||||
|
| Version | Date | Changes |
|
||||||
|
|---------|------|---------|
|
||||||
|
| 1.0 | 2026-04-11 | Initial creation, Phase 0 planning |
|
||||||
|
| — | — | — |
|
||||||
52
PROJECT-STATUS.md
Normal file
52
PROJECT-STATUS.md
Normal file
@@ -0,0 +1,52 @@
|
|||||||
|
# TekDek Project Status
|
||||||
|
|
||||||
|
**Current Phase**: Phase 0 — Discovery & Planning
|
||||||
|
**Last Updated**: 2026-04-11
|
||||||
|
**Next Review**: End of Week 1
|
||||||
|
|
||||||
|
---
|
||||||
|
|
||||||
|
## Phase 0 Progress
|
||||||
|
|
||||||
|
### Documents Created ✅
|
||||||
|
- [x] TekDek-Strategy.md — Vision & model
|
||||||
|
- [x] Tool-Requirements.md — What to build
|
||||||
|
- [x] TekDek-Master-Project-Plan.md — Full execution roadmap
|
||||||
|
- [x] Master-Plan-Quick-Checklist.md — Decision checklist
|
||||||
|
- [x] TekDek-Brainstorm-Reference.md — Quick reference
|
||||||
|
- [x] PROJECT-OVERVIEW.md — File guide & navigation
|
||||||
|
- [x] PROJECT-STATUS.md — This file
|
||||||
|
- [x] Brick-Profile.md — First persona prototype
|
||||||
|
|
||||||
|
### Decisions Pending 🔴
|
||||||
|
- [ ] Brick's technical specialty
|
||||||
|
- [ ] Initial persona roster (5–9 personas)
|
||||||
|
- [ ] First narrative arc
|
||||||
|
- [ ] Revenue model
|
||||||
|
- [ ] Launch target date
|
||||||
|
|
||||||
|
### Templates Pending 🔄
|
||||||
|
- [ ] Persona Template (for personas 2–10)
|
||||||
|
- [ ] Narrative Arc Template
|
||||||
|
- [ ] Content Curation Workflow
|
||||||
|
|
||||||
|
### Infrastructure ✅
|
||||||
|
- [x] OpenClaw bootstrapped (ParzivalTD identity)
|
||||||
|
- [x] Discord connected and paired
|
||||||
|
- [x] Knowledge base (qmd) installed and indexed
|
||||||
|
- [x] Self-improving agent configured
|
||||||
|
- [x] Skills installed (clawhub, bookstack, gitea, qmd, self-improving)
|
||||||
|
- [x] Default model: Kimi-k2.5
|
||||||
|
- [x] Heartbeat: 3h interval, GPT-4.5-mini
|
||||||
|
- [x] Session memory enabled
|
||||||
|
|
||||||
|
### Blockers
|
||||||
|
- None — awaiting Glytcht's 5 critical decisions to proceed
|
||||||
|
|
||||||
|
---
|
||||||
|
|
||||||
|
## What's Next
|
||||||
|
|
||||||
|
**Glytcht**: Make 5 decisions (see Master-Plan-Quick-Checklist.md)
|
||||||
|
**ParzivalTD**: Once decisions are in, finalize personas, plan arcs, design systems
|
||||||
|
**Dev Team**: Review Master Project Plan, answer open questions
|
||||||
693
knowledge/TekDek-Master-Project-Plan.md
Normal file
693
knowledge/TekDek-Master-Project-Plan.md
Normal file
@@ -0,0 +1,693 @@
|
|||||||
|
# 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**:
|
||||||
|
1. **Business**: Multi-platform content aggregation, monetization, community
|
||||||
|
2. **Technical**: Central hub (Stack Legion), persona agents, syndication
|
||||||
|
3. **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)
|
||||||
|
- [x] TekDek-Strategy.md — Vision, layers, persona model, narrative engine
|
||||||
|
- [x] Tool-Requirements.md — Critical path tools, build/buy decisions
|
||||||
|
- [x] TekDek-Brainstorm-Reference.md — One-page quick reference
|
||||||
|
|
||||||
|
**Persona Framework** (IN PROGRESS)
|
||||||
|
- [x] 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**:
|
||||||
|
1. What's the portal's tech stack?
|
||||||
|
2. Can you provide an API surface for external systems (like OpenClaw) to query persona data and sync published content?
|
||||||
|
3. What's your estimated MVP launch date?
|
||||||
|
4. 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
|
||||||
|
|
||||||
|
1. **Tech Stack**: What's the portal built on? (Rails? Node? Django?)
|
||||||
|
2. **Database**: PostgreSQL? MongoDB? What schema are you thinking?
|
||||||
|
3. **Timeline**: What's your realistic MVP launch target?
|
||||||
|
4. **APIs**: Can you design REST/GraphQL endpoints for persona data, content sync, analytics?
|
||||||
|
5. **Content workflow**: Does the portal handle drafts → review → approval → publish?
|
||||||
|
6. **Gamification**: Is challenge creation persona-authored or admin-created?
|
||||||
|
7. **Analytics**: Can we hook into user behavior, content performance, revenue?
|
||||||
|
8. **Infrastructure**: Are you hosting this yourselves or using cloud services?
|
||||||
|
9. **Scalability**: What's the user ceiling before we need to scale?
|
||||||
|
10. **Monetization**: How do you plan to handle memberships, courses, revenue sharing?
|
||||||
|
|
||||||
|
---
|
||||||
|
|
||||||
|
## Open Questions for Glytcht
|
||||||
|
|
||||||
|
1. **Brick's specialty**: What's his technical focus?
|
||||||
|
2. **Persona roster**: Who are your 9 other personas?
|
||||||
|
3. **First arc**: What conflict/collaboration kicks off the narrative?
|
||||||
|
4. **Revenue model**: Membership pricing? Course prices? Persona share %?
|
||||||
|
5. **Launch date**: Firm target or flexible?
|
||||||
|
6. **Curation load**: How much time can you spend reviewing/approving content?
|
||||||
|
7. **Persona sourcing**: Do you already know people, or recruit during Phase 1?
|
||||||
|
8. **Expansion timeline**: When do you want to launch vertical 2?
|
||||||
|
|
||||||
|
---
|
||||||
|
|
||||||
|
## Next Steps (This Week)
|
||||||
|
|
||||||
|
### For Glytcht
|
||||||
|
1. [ ] Finalize Brick's technical specialty
|
||||||
|
2. [ ] Define initial 5–9 personas (quick sketches)
|
||||||
|
3. [ ] Plan first narrative arc (beats, timeline, engagement hooks)
|
||||||
|
4. [ ] Lock in revenue model basics
|
||||||
|
5. [ ] Commit to launch date (Q3? Q4?)
|
||||||
|
6. [ ] Set dev team sync (weekly, Tuesdays 2pm?)
|
||||||
|
|
||||||
|
### For ParzivalTD (Me)
|
||||||
|
1. [ ] Finalize Brick-Profile.md with specialty/origin/relationships
|
||||||
|
2. [ ] Create Persona Template for personas 2–10
|
||||||
|
3. [ ] Design Narrative Arc Template (reusable structure)
|
||||||
|
4. [ ] Draft Content Curation Workflow (intake → approval → publish)
|
||||||
|
5. [ ] Design Persona Roster System architecture (ready for portal integration)
|
||||||
|
6. [ ] Schedule first dev team sync
|
||||||
|
|
||||||
|
### For Development Team
|
||||||
|
1. [ ] Review this Master Plan document
|
||||||
|
2. [ ] Answer open questions above
|
||||||
|
3. [ ] Propose Phase 0 deliverables on your end
|
||||||
|
4. [ ] Design API contract (what we'll call, what you'll return)
|
||||||
|
5. [ ] 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.
|
||||||
Reference in New Issue
Block a user