255 lines
10 KiB
PHP
255 lines
10 KiB
PHP
<?php if (!defined('TEKDEK')) die('Direct access not permitted.'); ?>
|
||
|
||
<article class="page-content decisions-content">
|
||
<h1>Master Plan Quick Checklist</h1>
|
||
|
||
<p class="updated-date"><em>This Week (Phase 0 Decisions): 🔴 CRITICAL PATH</em></p>
|
||
<p class="guide-note"><em>Full Plan: See Master Project Plan in Projects section</em></p>
|
||
|
||
<section class="critical-decisions">
|
||
<h2>Your Decisions This Week (Glytcht)</h2>
|
||
|
||
<article class="decision decision-1">
|
||
<h3>🔴 Decision 1: Brick's Technical Specialty</h3>
|
||
<p><strong>Why</strong>: Templates his first articles, determines his voice in depth</p>
|
||
<p><strong>Options</strong>:</p>
|
||
<ul>
|
||
<li>Backend</li>
|
||
<li>DevOps / Infrastructure</li>
|
||
<li>Full-stack</li>
|
||
<li>Architecture</li>
|
||
<li>Database design</li>
|
||
<li>Other?</li>
|
||
</ul>
|
||
<p><strong>Action</strong>: Pick one, ParzivalTD will finalize his profile</p>
|
||
<p><strong>Deadline</strong>: TODAY if possible</p>
|
||
</article>
|
||
|
||
<article class="decision decision-2">
|
||
<h3>🔴 Decision 2: Initial Persona Roster (Personas 2–10)</h3>
|
||
<p><strong>Why</strong>: Determines content calendar, arc participants, expertise mix</p>
|
||
<p><strong>Options</strong>: 5–10 people (real people you know, or we recruit during Phase 1?)</p>
|
||
<p><strong>Action</strong>: Sketch out 5–9 personas (name, expertise, rough voice idea)</p>
|
||
<p><strong>Deadline</strong>: End of Week 1</p>
|
||
</article>
|
||
|
||
<article class="decision decision-3">
|
||
<h3>🔴 Decision 3: First Narrative Arc</h3>
|
||
<p><strong>Why</strong>: Drives all content scheduling and engagement</p>
|
||
<p><strong>Options</strong>:</p>
|
||
<ul>
|
||
<li>PHP vs Node debate (Brick + Frontend persona clash)</li>
|
||
<li>Learning journey (new persona builds in public)</li>
|
||
<li>Collaboration (multiple personas build something together)</li>
|
||
<li>Other?</li>
|
||
</ul>
|
||
<p><strong>Action</strong>: Pick arc, ParzivalTD will plan beats and content calendar</p>
|
||
<p><strong>Deadline</strong>: End of Week 2</p>
|
||
</article>
|
||
|
||
<article class="decision decision-4\">
|
||
<h3>🔴 Decision 4: Revenue Model</h3>
|
||
<p><strong>Why</strong>: Dev team needs this to build payment processing</p>
|
||
<p><strong>Options</strong>:</p>
|
||
<ul>
|
||
<li>Membership tiers (Free / $5/mo / $15/mo)</li>
|
||
<li>Courses ($29–$99 each)</li>
|
||
<li>Persona revenue share (70/30? 80/20?)</li>
|
||
<li>Sponsorships?</li>
|
||
</ul>
|
||
<p><strong>Action</strong>: Rough numbers, ParzivalTD will detail it</p>
|
||
<p><strong>Deadline</strong>: End of Week 3</p>
|
||
</article>
|
||
|
||
<article class="decision decision-5\">
|
||
<h3>🔴 Decision 5: Launch Target</h3>
|
||
<p><strong>Why</strong>: Everything else is scheduled around this</p>
|
||
<p><strong>Options</strong>:</p>
|
||
<ul>
|
||
<li>Q3 2026 (July–September)</li>
|
||
<li>Q4 2026 (October–December)</li>
|
||
<li>Q1 2027 (January–March)</li>
|
||
<li>Other?</li>
|
||
</ul>
|
||
<p><strong>Action</strong>: Commit to date, ParzivalTD will build sprint plan</p>
|
||
<p><strong>Deadline</strong>: End of Week 4</p>
|
||
</article>
|
||
</section>
|
||
|
||
<section class="deliverables\">
|
||
<h2>ParzivalTD's Deliverables This Week</h2>
|
||
<ul>
|
||
<li class="done\">✅ TekDek-Strategy.md</li>
|
||
<li class="done\">✅ Tool-Requirements.md</li>
|
||
<li class="done\">✅ Brick-Profile.md (stub)</li>
|
||
<li class="done\">✅ TekDek-Brainstorm-Reference.md</li>
|
||
<li class="done\">✅ TekDek-Master-Project-Plan.md</li>
|
||
<li class="pending\">[ ] Finalize Brick-Profile.md (pending Decision #1)</li>
|
||
<li class="pending\">[ ] Persona Template (for personas 2–10)</li>
|
||
<li class="pending\">[ ] Narrative Arc Template</li>
|
||
<li class="pending\">[ ] Content Curation Workflow doc</li>
|
||
<li class="pending\">[ ] Persona Roster System spec (design)</li>
|
||
</ul>
|
||
</section>
|
||
|
||
<section class="timeline\">
|
||
<h2>Phase 0 Timeline</h2>
|
||
<table class="timeline-table\">
|
||
<thead>
|
||
<tr>
|
||
<th>Week</th>
|
||
<th>Decision / Deliverable</th>
|
||
<th>Status</th>
|
||
</tr>
|
||
</thead>
|
||
<tbody>
|
||
<tr>
|
||
<td><strong>Week 1</strong></td>
|
||
<td>Decisions 1–2 locked, Brick finalized, 5 personas sketched</td>
|
||
<td class="current\">🔴 Now</td>
|
||
</tr>
|
||
<tr>
|
||
<td><strong>Week 2</strong></td>
|
||
<td>Decision 3 locked, Arc 1 planned, content calendar drafted</td>
|
||
<td class="pending\">⏳ Next</td>
|
||
</tr>
|
||
<tr>
|
||
<td><strong>Week 3</strong></td>
|
||
<td>Decision 4 locked, revenue model detailed</td>
|
||
<td class="pending\">⏳ Later</td>
|
||
</tr>
|
||
<tr>
|
||
<td><strong>Week 4</strong></td>
|
||
<td>Decision 5 locked, all templates + specs done, dev team sync</td>
|
||
<td class="pending\">⏳ Later</td>
|
||
</tr>
|
||
</tbody>
|
||
</table>
|
||
</section>
|
||
|
||
<section class="phase-overview\">
|
||
<h2>Phase Overview (Reference)</h2>
|
||
<table class="phase-reference\">
|
||
<thead>
|
||
<tr>
|
||
<th>Phase</th>
|
||
<th>Timeframe</th>
|
||
<th>Goal</th>
|
||
<th>Team Lead</th>
|
||
</tr>
|
||
</thead>
|
||
<tbody>
|
||
<tr>
|
||
<td><strong>Phase 0</strong></td>
|
||
<td>NOW – Week 4</td>
|
||
<td>Lock decisions, design systems</td>
|
||
<td>TekDek (Glytcht)</td>
|
||
</tr>
|
||
<tr>
|
||
<td><strong>Phase 1</strong></td>
|
||
<td>Week 5–12</td>
|
||
<td>Build personas, test narrative, publish content</td>
|
||
<td>TekDek + Dev</td>
|
||
</tr>
|
||
<tr>
|
||
<td><strong>Phase 2</strong></td>
|
||
<td>Week 13–16</td>
|
||
<td>MVP launch, public beta, validate model</td>
|
||
<td>Dev (Portal launch)</td>
|
||
</tr>
|
||
<tr>
|
||
<td><strong>Phase 3</strong></td>
|
||
<td>Week 17–24</td>
|
||
<td>Scale to 10 personas, 2 verticals</td>
|
||
<td>TekDek (narrative expansion)</td>
|
||
</tr>
|
||
<tr>
|
||
<td><strong>Phase 4</strong></td>
|
||
<td>Week 25+</td>
|
||
<td>3–5 verticals, 50+ personas, enterprise scale</td>
|
||
<td>Both teams</td>
|
||
</tr>
|
||
</tbody>
|
||
</table>
|
||
</section>
|
||
|
||
<section class="critical-factors\">
|
||
<h2>Critical Success Factors (Phase by Phase)</h2>
|
||
|
||
<article class="phase-factors\">
|
||
<h3>Phase 0 ✅ (This Week)</h3>
|
||
<ul>
|
||
<li>Decisions locked</li>
|
||
<li>Personas defined</li>
|
||
<li>Arc 1 planned</li>
|
||
<li>Dev team aligned</li>
|
||
</ul>
|
||
</article>
|
||
|
||
<article class="phase-factors\">
|
||
<h3>Phase 1 ✅ (Week 5–12)</h3>
|
||
<ul>
|
||
<li>Brick voice test (2–3 articles)</li>
|
||
<li>3 personas live</li>
|
||
<li>Arc 1 live with content tied to beats</li>
|
||
<li>APIs operational</li>
|
||
<li><strong>Go/No-Go for Phase 2</strong> (Week 12)</li>
|
||
</ul>
|
||
</article>
|
||
|
||
<article class="phase-factors\">
|
||
<h3>Phase 2 ✅ (Week 13–16)</h3>
|
||
<ul>
|
||
<li>Stack Legion MVP public</li>
|
||
<li>500+ users</li>
|
||
<li>Arc 1 generating engagement</li>
|
||
<li>Revenue streams working</li>
|
||
<li><strong>Go/No-Go for Phase 3</strong> (Week 16)</li>
|
||
</ul>
|
||
</article>
|
||
|
||
<article class="phase-factors\">
|
||
<h3>Phase 3 ✅ (Week 17–24)</h3>
|
||
<ul>
|
||
<li>10 personas across 2 verticals</li>
|
||
<li>Multiple arcs in parallel</li>
|
||
<li>10K+ monthly users</li>
|
||
<li>Replication template proven</li>
|
||
</ul>
|
||
</article>
|
||
|
||
<article class="phase-factors\">
|
||
<h3>Phase 4 (Week 25+)</h3>
|
||
<ul>
|
||
<li>3–5 verticals live</li>
|
||
<li>50+ personas</li>
|
||
<li>$50K+ monthly recurring revenue</li>
|
||
</ul>
|
||
</article>
|
||
</section>
|
||
|
||
<section class="questions-devteam\">
|
||
<h2>Questions for Dev Team (First Sync)</h2>
|
||
<ol>
|
||
<li>Tech stack? (Rails? Node? Django?)</li>
|
||
<li>Realistic MVP launch date?</li>
|
||
<li>Can you design APIs for persona data, content sync, analytics?</li>
|
||
<li>What's the user scaling limit before we need microservices?</li>
|
||
<li>Payment processing / revenue sharing capability?</li>
|
||
<li>How do we integrate management system (OpenClaw) with portal?</li>
|
||
</ol>
|
||
</section>
|
||
|
||
<section class="next-step\">
|
||
<h2>Next Step: Respond to Decisions</h2>
|
||
<p>Once you give Decisions 1–3 (Brick specialty, 5 personas, first arc), ParzivalTD can:</p>
|
||
<ol>
|
||
<li>Finalize all persona profiles</li>
|
||
<li>Plan content calendar through end of Q2</li>
|
||
<li>Design system architecture (what to build in OpenClaw)</li>
|
||
<li>Provide dev team with technical requirements</li>
|
||
</ol>
|
||
<p><strong>Then we're off to the races.</strong></p>
|
||
</section>
|
||
|
||
</article>
|