MasteryMade · Template

Template: Expert Boarding Pack

Clone this for each new expert extraction. Replace [EXPERT] and [DOMAIN] placeholders. Publish to [expert].asapai.net/boarding-pack.
Reference: PRD 4 · PRD 9 · Live example: Align360 boarding pack

1. Boarding milestone tracker

Visual checklist of 4 boarding milestones. Each must be cleared before full extraction begins.

Milestone	What's needed	Status
1: Brand assets	Logo, colors, fonts, tagline	☐
2: Extraction interviews	Minimum 2 recorded sessions (45+ min each). Governance doc if available.	☐
3: Content permissions	YouTube API access, email list, LinkedIn, podcast feed. Not required for MVP — required for content machine (PRD 8).	☐
4: Offer approval	Pricing set, formal partner sign-off, domain registered.	☐

2. Expert profile

Name:           [EXPERT NAME]
Company:        [COMPANY]
Tagline:        [TAGLINE]
Bio:            [2-3 sentences]
Core expertise: [bullet list]
Unique framework: [Primary framework name + brief description]
Target audience:  [Who they serve]
Brand voice:      [Tone, reading level, sentence length, what to never say]

3. IP inventory

3A: Product architecture

Enumerate all tools, frameworks, courses, programs. For each:

| # | Name | Description | Phase/Tier | Active at launch? |

Also list any background/invisible systems that govern behavior (Samuel had 14 of these).

3B: Core frameworks

Document the expert's primary methodology. This maps to PRD 4 Module 1 (thinking rubric).

Framework name:     [e.g., FLC Wisdom Framework]
Layers/steps:       [Sequential steps or layers]
Decision logic:     [How the expert decides what to do next]
Validation filter:  [How they know output is "done" / "good enough"]
Anti-patterns:      [What they actively guard against]
Governing values:   [Core values that shape decisions]

3C: Content assets

File	Location	Type	Module mapping
[System prompt]	[path]	AI system	All modules (monolithic — needs decomposition)
[Knowledge files]	[path]	Reference	Modules 4-6 (embedded IP, modularization, meta-structures)
[Interview transcripts]	[path]	Extraction source	Modules 1-3, 7-8 (thinking, voice, CTA, patterns, prompts)
[Governance doc]	[path]	Rules	Module 1 (thinking rubric), Module 3 (CTA guardrails)

3D: Partnerships

List active partnerships with revenue model, network value, and pricing.

4. PRD 4 module mapping

For each module, identify source material and extraction status. This becomes the reconciliation doc.

Module	Source material	Extracted?	Structured JSON?
1. Thinking rubric	[Primary framework]	☐	☐
2. Voice + style	[Voice description from profile]	☐	☐
3. CTA psychology	[Monetization guardrails, anti-patterns]	☐	☐
4. Embedded IP	[Named frameworks, tools, types]	☐	☐
5. Modularization	[Teaching sequences, progressions]	☐	☐
6. Meta-structures	[Program architecture, phase design]	☐	☐
7. Pattern recognition	[Diagnostics, assessments, typing systems]	☐	☐
8. Prompt templates	[Q&A pairs from transcripts]	☐	☐
9. Retrieval patterns	[Background systems, routing logic]	☐	☐

5. Build phase tracker

Phase	Description	Status	ETA
Extraction	Modules 1-9 structured JSON	☐
Validation	3-pass (forward, backward, ground truth)	☐
betaapp.io deploy	Clone on MasteryOS platform	☐
Competitor intel	5 competitors identified + analyzed	☐
Content machine	First month content calendar	☐
Wave 1	5 alpha users	☐
Wave 2	50-100 invite-only	☐
Wave 3	Public launch	☐

6. Pricing + monetization

Primary tier:     $[X]/year
Premium tier:     $[X]/year
Individual tools: $[X]-[X]/mo
Program pricing:  [if applicable]
Referral model:   [if applicable]
Monetization guardrails: [What the expert will NOT do — no shame, no urgency, etc.]

7. Onboarding flow

Step 1: [Lead magnet / assessment — free, email capture]
Step 2: [Results delivery — gated behind signup]
Step 3: [Account creation]
Step 4: [Discovery questions — personalize experience]
Step 5: [Platform entry with recommendations]
Step 6: [Phase progression — non-linear allowed]

8. LLM context block

Machine-readable summary for any AI assistant working on this expert's extraction. Copy into system prompts or project context files.

## [EXPERT] PROJECT CONTEXT BLOCK
PROJECT: [Expert Name] — Expert OS Clone on MasteryOS
EXPERT: [Full name, company]
PLATFORM: MasteryOS (betaapp.io deployment)
DOMAIN: [expert domain]
BRAND: colors, fonts, logo, tagline
VOICE: style, tone, reading level, never-do list
FRAMEWORK: [Primary framework name + structure]
PRODUCT: phases, stacks, active at launch
KEY_FILES: [paths to system prompt, knowledge files, transcripts]
BUILD_STATUS: [current milestone, next milestone]
ONBOARDING_FLOW: [numbered steps]
## END CONTEXT BLOCK

Usage