11 KiB
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):
- This file (PROJECT-OVERVIEW.md)
/Master-Plan-Quick-Checklist.md/TekDek-Brainstorm-Reference.md
Second Pass (1 hour):
/knowledge/TekDek-Strategy.md(sections: Executive Summary, Vision, Three Layers)/knowledge/TekDek-Master-Project-Plan.md(sections: Phase 0, Phase 1, Decision Checkpoints)
Deep Dive (2+ hours):
- Full
/knowledge/TekDek-Master-Project-Plan.md /knowledge/Tool-Requirements.md/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)
- Read
/Master-Plan-Quick-Checklist.md(5 min) - Decide on your 5 critical decisions (Decision 1–5)
- Notify ParzivalTD when ready
- Review
/knowledge/TekDek-Master-Project-Plan.mdfor full context - Schedule weekly sync with dev team (TBD time)
For ParzivalTD (Me)
- ✅ Create all strategy documents
- ✅ Create Master Project Plan
- ✅ Create this overview file
- 🔄 AWAITING: Your 5 decisions
- Then: Finalize Brick profile, create persona templates, design systems
For Development Team
- Review
/knowledge/TekDek-Master-Project-Plan.md - Answer open questions (tech stack, timeline, APIs)
- Propose Phase 0 deliverables on your end
- 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 |
| — | — | — |