MasteryMade · Execution Playbook
How 5 scattered workstreams collapse into one sequential domino chain. Each step builds the machine while serving the customer.
These look like separate projects. They're not. They're layers of the same system viewed from different angles.
| # | Workstream | What it actually is | Where it lives today |
|---|---|---|---|
| 1 | Jason's modular services plan | THE MAP — architecture spec for everything | plan.jasondmacdonald.com (16 pages, 12 PRDs) |
| 2 | RSS / intelligence dashboard | THE RADAR — signals filtered against goals | jasondmacdonald.com (briefs #47-51+, Neural Registry) |
| 3 | Universal ingest + lenses | THE ENGINE — how data flows and gets processed | Designed in PRD 3 + PRD 2. Not built yet. |
| 4 | MasteryOS extraction + clones | THE FACTORY — how experts get extracted and deployed | Skills in /mnt/skills/user/ (expert-*). Platform at betaapp.io. PRD 4 spec. |
| 5 | Samuel's Align360 | THE FIRST UNIT TEST — proves the factory works | E:\align360\ (local). align360.asapai.net. design.align360.io. betaapp.io. Claude Code CLI sessions. |
The reconciliation problem isn't about cross-linking pages. It's about execution order. The pages are documentation artifacts — they're useful but they're not the work. The work is: extract Samuel → prove the extraction pipeline → package as skill → deploy on betaapp.io → use the skill on next expert. Everything else (the map, the radar, the engine design) exists to guide and improve that loop.
One action that makes everything else easier or unnecessary:
Run PRD 4 Module 1 extraction on Samuel's existing material.
This single step:
Each step builds the machine AND serves Samuel. No step exists purely for architecture. If it doesn't produce a usable artifact, it's not on this list.
PARALLEL — Will + Sumit
Wiring for Impact assessment working. Phase 0 tools responding. 5 alpha users can access. This doesn't wait for the extraction pipeline — it uses the existing System Prompt v6.1 and knowledge files. Good enough for Wave 1.
Win condition: Samuel logs in and completes Wiring for Impact assessment. 5 users invited.
Touches: betaapp.io · PRD 11 (SILO 2 ops)
JASON — Forge or Claude session
Source material: 3 extraction transcripts + governance doc + System Prompt v6.1. Extract the FLC Wisdom Framework (5 layers + Tri-Filter + Clarity Path) as Module 1 structured JSON per PRD 4 Section 4.4. Validate: does the rubric match how Samuel actually thinks in the transcripts?
Win condition: JSON rubric that passes human review. Rubric identifies at least 3 named frameworks, 5+ decision logic patterns, clear priority hierarchy.
Touches: E:\align360\ source files · PRD 4 · Align360 reconciliation
What this creates: The Module 1 extractor skill — reusable on any expert. Store the extraction in Supabase expert_extractions table (or local first, migrate later).
JASON — sequential, each validates against Module 1
The System Prompt v6.1 already contains most of this in monolithic form. This step DECOMPOSES it into modular JSON per module. Not re-extracting — transforming format.
Win condition: All 8 modules as validated JSON. Forward pass coherence check passes. Each module traces back to source material.
What this creates: The decomposition skill — takes ANY monolithic expert system prompt and decomposes it into 8 modules. This is the scale multiplier.
JASON
Samuel's 14 background systems (Pathfinder, RhythmOS, Epistemic Drift Detection, etc.) ARE retrieval patterns. Convert to Module 9 routing rules: "When user asks about X → load Module Y, framework Z."
Win condition: Routing rules JSON. When tested against 10 sample queries, routes to correct framework 8/10 times.
What this creates: The meta-index (PRD 4 Section 4.9) — lazy-load ~500 tokens instead of loading all 36 stacks into context.
JASON — uses expert-clone-scorer + expert-test-extractor skills
Forward pass (modules cohere). Backward pass (traces to source). Ground truth pass (clone output matches Samuel's actual responses from transcripts).
Win condition: All 3 passes pass. If ground truth shows gaps, iterate Modules 2-8.
JASON + SUMIT
Replace monolithic System Prompt v6.1 with modular extraction. Meta-index drives retrieval. Clone quality improves because it loads relevant modules instead of everything. This is the upgrade from Wave 1 → Wave 2 quality.
Win condition: Samuel notices improvement. Clone responses more accurate, more "him."
JASON / FORGE
The Module 1-9 extraction steps become an automated skill. Input: entity_id + ingested content. Output: structured extraction per module + meta-index. Includes MANUAL.md + HC page.
Win condition: Run on a second expert's PUBLIC content (The WAY or Brain Muka). Produces reasonable Module 1 rubric without manual intervention.
What this creates: The Expert Factory — the core IP of MasteryMade. Every future expert goes through this skill.
AGENT SWARM / FORGE
Identify 5 competitors. Ingest public content. Run competitor lens. Produce positioning map + gap analysis. Give to Samuel as go-giver artifact.
Win condition: Competitor report that Samuel finds valuable. Proves the competitor analysis pipeline. Feeds content strategy.
AGENT SWARM
Use Module 2 (voice) + Module 4 (frameworks) + competitor gaps to generate content briefs. Apply Mastery Labs matrix. Generate first month's content calendar.
Win condition: 10 content pieces generated in Samuel's voice. Samuel approves at least 7/10 without edits.
JASON + SAMUEL
Wave 1 (Step 1) already running. Wave 2: 50-100 invite-only with validated extraction. Wave 3: public launch with content machine running.
| Artifact | Location | Role | Links to |
|---|---|---|---|
| Architecture index | plan.jasondmacdonald.com/index | Site map — start here | All PRDs, all reconciliation docs |
| Master Registry | plan.jasondmacdonald.com/master-registry | Root architecture doc | All 16 sections, all PRDs |
| 12 PRDs | plan.jasondmacdonald.com/prd-* | Universal system specs | ↑ Master Registry · ↔ each other |
| Align360 reconciliation | plan.jasondmacdonald.com/align360-reconciliation | Samuel-specific gap analysis | ↑ Master Registry · ↓ boarding pack, command center, betaapp.io |
| This playbook | plan.jasondmacdonald.com/execution-playbook | Sequenced execution plan | ↑ Master Registry · → all PRDs · → all Align360 artifacts |
| Boarding Pack | align360.asapai.net/boarding-pack | Extraction process workspace | ↑ plan reconciliation · → betaapp.io |
| Command Center | design.align360.io/command-center | Project dashboard | ↑ plan reconciliation · → boarding pack · → betaapp.io |
| betaapp.io | align360.betaapp.io | Live product (user-facing) | ↑ plan reconciliation |
| Local files | E:\align360\ (Claude Code CLI) | Source material + system prompt | → Steps 2-5 of this playbook |
| Daily Briefs | jasondmacdonald.com/brief-* | Intelligence radar | → knowledge-registry · tracks execution progress |
| Knowledge Registry | jasondmacdonald.com/knowledge-registry | Concept graph across all briefs | Updated after each brief · nodes track architecture concepts |
| Extraction skills | /mnt/skills/user/expert-* | Reusable pipeline skills | → PRD 4 · → PRD 12 (MANUAL.md needed) |
Every step in the sequence produces THREE things:
If a step only produces one of these three, it's the wrong step. If it produces all three, it's the domino.
MASTERYMADE · Execution Playbook · March 25, 2026
Dominia Facta. Build what compounds.