Master Lexicon & Full Pipeline Tracker

Document Primacy Hierarchy what governs what

When sources conflict, higher-ranked documents win. The execution playbook determines build order. The boarding pack determines Align360 scope. PRDs determine how to build. The swarm PRD describes the aspirational end-state.

Rank	Document	Location	Governs	Scope
1	Execution Playbook (10 steps)	plan/execution-playbook	Build sequence & priority	All workstreams
2	Boarding Pack (Samuel’s gates)	align360/boarding-pack	Product scope & requirements	Align360 only
3	PRD 4: Expert Extraction Pipeline	plan/prd-expert-extraction	Extraction architecture	All experts
4	Command Center	design.align360.io/command-center	Product truth (phases, tools, team)	Align360 only
5	Platform PRDs (3,5,6,7,8,9)	plan/index	Platform capabilities	MasteryOS (all products)
6	Swarm PRD (18 agents)	expert/agentic-boarding-prd	Aspirational end-state	Partner-facing vision

Key rule: Steps 1–6 in the execution playbook are Align360-specific. The boarding pack and command center are the product truth for these steps. Steps 7–10 are platform-level — the plan PRDs govern those. Do not conflate platform capabilities with Align360 MVP requirements.

Canonical Lexicon use these terms everywhere

Every term below has ONE canonical meaning. When writing skills, docs, CLAUDE.md, or code — use these definitions. Former/alternative names listed for search/migration.

Pipeline & Architecture

Canonical Term	Also Known As	Definition	Scope
Workstream	pipeline stage	One of 5 sequential meta-stages: MAP → RADAR → ENGINE → FACTORY → PRODUCT	All
MAP	plans, PRDs	Workstream 1: Planning documents, PRDs, architecture specs	Platform
RADAR	briefs, intel	Workstream 2: Intelligence gathering, daily briefs, signal engine, competitor analysis	Platform
ENGINE	ingest, pipeline	Workstream 3: Content ingestion, processing, embedding, annotation	Platform
FACTORY	extraction, skills	Workstream 4: Extraction pipeline, skill execution, Module 1–9 processing	All
PRODUCT	clone, OS	Workstream 5: Deployed expert clone (betaapp.io, agent, content)	Per-expert

Extraction System

Canonical Term	Also Known As	Definition	Scope
Module	content type, extraction unit	One of 9 extraction content types (Module 1: Thinking Structures through Module 9: Retrieval Patterns). Produces structured JSON.	FACTORY
Skill	agent, tool, SKILL.md	A Claude Code executable capability. Lives in `~/.claude/skills/[name]/SKILL.md`. One skill may serve multiple Modules.	FACTORY
Layer	level, L0–L4	Skill execution order in the recursive clone pipeline. L0 (recon) through L4 (orchestration).	FACTORY
Pass	phase, iteration	One of 4 extraction protocol stages: Pass 1 (Raw Extraction) → Pass 2 (Pattern Recognition) → Pass 3 (Rubric Building) → Pass 4 (Gap Analysis)	FACTORY
Swarm Agent	color agent, PRD agent	An aspirational autonomous agent from the Agentic Boarding PRD. Color-coded: PURPLE/GREEN/BLUE/YELLOW/RED. NOT operational — implemented as Skills.	Vision only
Three-Pass Validation	3-pass, validation protocol	Forward (coherence) + Backward (source tracing) + Ground Truth (vs. transcripts) validation. Distinct from the 4-Pass extraction protocol.	FACTORY

Product & Boarding

Canonical Term	Also Known As	Definition	Scope
Boarding Milestone	gate (boarding pack)	An onboarding checkpoint for a new expert: Milestone 1 (Brand Assets) → M2 (Extraction Interview) → M3 (Content Permissions) → M4 (Offer Approval). NOT the same as Data Gate.	Per-expert
Data Gate	gate (master registry)	A data scoping tier controlling what intelligence is available: Gate 1 (Operator) → G2 (JV Prospect) → G3 (Signed Expert) → G4 (Competitor). Determines what content is visible per PRD 2.	Platform
Phase	product phase	One of 5 Align360 product phases: Phase 0 (DesignSuite) through Phase 4 (LegacyLab). Contains tool stacks.	Per-expert
Stack	tool stack, tool	A single functional tool within a Phase. 36 total across 5 phases. Each stack has: purpose, inputs, framework, outputs, prompt template.	Per-expert
Background System	silent layer, background tool	One of 14 always-active systems (e.g., RhythmOS, Pathfinder, Epistemic Drift Detection). Runs without user invocation.	Per-expert
Wiring Type	redemptive gift, gift type	One of 9 personality/gifting types in Samuel’s framework. Used for assessment routing and personalization.	Align360
FLC Wisdom Framework	5 layers, wisdom layers	Samuel’s core IP: Integrity Core → Clarity Engine → Emotional Ethic → Capacity Engine → Learning Loop. Non-negotiable backbone.	Align360
Tri-Filter	decision gate	Every output passes: Truth + Clarity + Impact. Quality checkpoint on all generated content.	Align360

Infrastructure & Publishing

Canonical Term	Also Known As	Definition	Scope
HC Protocol	HyperContext	Publishing standard for web pages. Metadata in `<meta name="hc:*">` tags. Published via NowPage.	Platform
NowPage	publish, hc-publish	CLI publishing system. `node scripts/hc-publish.js` from `folio-saas`. Targets any HC domain.	Platform
Forge	VPS, server	Self-hosted VPS running Docker services (n8n, Supabase, cron, ingest). Runs ENGINE workstream.	Platform
MasteryBook	RAG, notebook	Team-accessible RAG-based Q&A. Synced via masterybook-sync skill. For team knowledge sharing.	Platform
betaapp.io	platform, app	The deployed Mastery OS instance. Next.js + Vercel. Where users access expert clones.	Product
Clone	expert OS, expert AI	The deployed AI coaching experience for a specific expert. Fed by Modules 1–9 extraction. NOT a copy — a recursive emulator.	Product

Team & Process

Canonical Term	Also Known As	Definition	Scope
Three-Artifact Rule	3-artifact	Every execution step must produce: (1) customer artifact, (2) reusable skill, (3) architecture validation. Steps failing this rule are eliminated.	All
Critical Domino	domino, first move	The single action that makes everything else cheaper, faster, or unnecessary. Currently: “Run Module 1 extraction on Samuel’s material.”	Current
Temporal Log	session log, changelog	Chronological record of discoveries, decisions, and state changes. Published to pipeline tracker. Enables session handoff.	All
MAP Change Queue	change queue, backlog	Changes discovered during builds that need to propagate back to planning documents. Batched, not one-off.	All

RETIRED TERMS (do not use):
• “Gate” alone — always specify “Boarding Milestone” or “Data Gate”
• “Agent” for skills — use “Skill” for Claude Code executables, “Swarm Agent” for PRD aspirational agents
• “MANUAL.md” — actual convention is SKILL.md. Master registry Section 12 needs update.
• “Tool” for extraction capabilities — use “Skill”. Reserve “Tool” / “Stack” for user-facing product tools (36 stacks).
• “Pipeline” alone — specify which: “Extraction Pipeline” (FACTORY) or “Ingest Pipeline” (ENGINE) or “5-Workstream Pipeline” (full)

Execution Sequence 10 steps — primacy #1

This is the canonical build order from the Execution Playbook. Steps 1–6 serve Align360 directly. Steps 7–10 platform the capabilities. Each step maps to PRD(s), Skill(s), and Boarding Milestone(s).

Ship Samuel’s betaapp.io (Wave 1)

Deploy v6.1 system prompt + knowledge files. 5 alpha users.

Owner: Will + Sumit PRD: 7 (experience) Milestone: M1–M2 Skills: none (manual deploy) Status: Platform live, Samuel pressing for access

Module 1 Extraction — FLC Wisdom Framework

Extract thinking structures from 3 transcripts + governance doc. Produce structured JSON rubric per PRD 4.

Owner: Jason PRD: 4 (Module 1) Milestone: M2 (complete) Skill needed: expert-framework-creator (L0.25) — UNBUILT CRITICAL DOMINO

Modules 2–8 Decomposition

Transform monolithic v6.1 into 7 modular JSON structures: Voice, CTA, IP, Sequences, Meta, Patterns, Templates.

Owner: Jason PRD: 4 (Modules 2–8) Skills: soul-extractor, voice-extractor*, framework-extractor*, resource-extractor, offer-extractor* * = needs expansion Depends on: Step 2 (Module 1 rubric validates all downstream)

Module 9 — Retrieval Routing Rules

Convert 14 background systems into routing logic: “user query → Module Y → Framework Z.” Meta-index ~500 tokens.

Owner: Jason PRD: 4 (Module 9) Skill: GAP — no skill exists for Module 9 Depends on: Step 3

Three-Pass Validation

Forward (coherence) + backward (source tracing) + ground truth (vs. transcripts) validation of all modules.

Owner: Jason PRD: 4 (validation) Skill needed: clone-tester (L3.5) — UNBUILT Depends on: Steps 2–4

Deploy to betaapp.io (Wave 2 Upgrade)

Replace v6.1 with modular extraction. Meta-index drives retrieval. Quality improvement via targeted module loading.

Owner: Jason + Sumit PRD: 7 (dynamic experience) Skills: clone-compiler (needs expansion) Depends on: Step 5

Align360 boundary: Steps 1–6 above are the Align360 deliverable. Everything below is platforming.

Package as Reusable Skill

Automate Module 1–9 pipeline. Input: entity ID + content. Output: extraction + meta-index. Test on second expert.

Owner: Jason/Forge PRD: 4 + 12 (skill manuals) Skills: boarding-orchestrator (expand) Depends on: Step 6

Competitor Intelligence

Identify 5 competitors, ingest public content, run competitor lens. Positioning map + gap analysis.

Owner: Swarm/Forge PRD: 5 (competitor intel) Skill: GAP — no competitor-intel skill exists Depends on: Step 6+ (optional parallel at Step 5)

Content Machine Activation

Use Voice (Mod 2) + IP (Mod 4) + gaps to generate content briefs. Apply marketing rubric.

Owner: Swarm PRD: 8 (content syndication) Skill: GAP — no content-gen skill exists Depends on: Steps 5, 8

Three-Wave Launch

Wave 1 (Step 1) running. Wave 2: 50–100 invite-only. Wave 3: public with content machine.

Owner: Jason + Samuel PRD: 9 (The Reveal) Depends on: Steps 1, 6, 9

Full Workstream Status all 5 tracked

Workstream 1

MAP

→

Workstream 2

RADAR

→

Workstream 3

ENGINE

→

Workstream 4

FACTORY

→

Workstream 5

PRODUCT

MAP (Plans & Architecture)

PRD	Title	Status	Needed for Align360?
PRD 1	Org Registry + MANUAL.md	Published, needs SKILL.md reconciliation	Yes (entity schema)
PRD 2	Data Gate Architecture + Suggest Engine	Published, terminology collision (Gate)	Yes (scoping tiers)
Master Registry	16-section system map	Published	Reference
Execution Playbook	10-step domino chain	Published — PRIMACY #1	Yes (build sequence)

RADAR (Intelligence & Signals)

Capability	PRD	Skill	Status	Exec Step
Expert recon (pre-boarding)	PRD 2 (Gate 2)	deep-research + expert-recon	Built & run on Samuel	Before Step 1
Competitor intelligence	PRD 5	No skill	GAP	Step 8
Marketing rubric scoring	PRD 5	No skill	GAP	Step 8
Signal engine + daily brief	PRD 6	No skill	Jason’s personal tool, not A360	N/A
Synthetic audience testing	PRD 5	No skill	GAP	Step 8+

Top-of-funnel intelligence for Align360: Expert recon is DONE (Samuel researched). Competitor intel is Step 8 — deferred until extraction pipeline is proven. Signal engine is NOT an Align360 feature.

ENGINE (Content Ingestion)

Capability	PRD	Implementation	Status	Exec Step
YouTube ingestion	PRD 3	Forge Docker service	Not deployed	Step 7+ (platform)
Podcast transcription	PRD 3	Whisper	Not deployed	Step 7+
Social media scraping	PRD 3	Platform APIs	Not deployed	Step 7+
Document processing	PRD 3	PDF/DOCX extraction	Manual (done for Samuel)	Step 7+
RSS polling	PRD 3	n8n + Forge	Not deployed	Step 7+
Meeting transcript ingestion	PRD 3	Tactiq/Fireflies webhook	Manual (3 transcripts loaded)	Step 7+

ENGINE for Align360: Samuel’s content was manually ingested (3 transcripts, governance doc, overview PDF, knowledge files). PRD 3’s automated ingest is platform infrastructure for FUTURE experts. Not blocking Align360.

FACTORY (Extraction Pipeline)

Skill	Layer	Module(s)	Status	Exec Step
deep-research	L0	RADAR feed	Built	Pre-1
expert-recon	L0	RADAR feed	Built	Pre-1
masterybook-sync	L0	Utility	Built	Pre-1
expert-framework-creator	L0.25	Mod 1 (primary)	UNBUILT — DOMINO	Step 2
demo-compiler	L0.5	Pre-deal artifact	UNBUILT	Step 7+ (JV sales)
rubric-builder	L1	Pass 3	Needs dual validation	Step 2–3
soul-extractor	L2	Mod 1 + 7	Built	Step 3
voice-extractor	L2	Mod 2	Needs +pattern-breaking	Step 3
framework-extractor	L2	Mod 4 + 5 + 6	Needs +micro-units	Step 3
resource-extractor	L2	Mod 8	Built	Step 3
offer-extractor	L2	Mod 3 (monetization)	UNBUILT	Step 3
gap-analyzer	L2.5	Pass 4	Built	Step 3
clone-compiler	L3	Mod 8 + deploy	Needs +user profile +offers	Step 6
lead-magnet-builder	L3	PRD 7	Built	Step 1
onboarding-builder	L3	PRD 7	Built	Step 1
clone-tester	L3.5	3-pass validation	UNBUILT	Step 5
design-system-extractor	Utility	GREEN	Built	Pre-1
boarding-orchestrator	L4	Orchestration	Needs 24-card + modes	Step 7

PRODUCT (Align360 / Samuel)

Module	Source Material	Extracted?	Structured JSON?	Exec Step
Mod 1: Thinking Structures	FLC Framework, Tri-Filter, Clarity Path	Partial (buried in v6.1)	No	Step 2
Mod 2: Voice & Style	Boarding pack voice spec	Yes	No	Step 3
Mod 3: CTA Psychology	Monetization guardrails, Laws of Babylon	Partial	No	Step 3
Mod 4: Embedded IP	36 stacks, 9 Wiring Types, frameworks	Yes	Partial	Step 3
Mod 5: Modularization	Phase 0–4 progression, stack sequencing	Yes	No	Step 3
Mod 6: Meta-Structures	5-phase architecture, onboarding flow	Yes	No	Step 3
Mod 7: Pattern Recognition	Wiring Types, RhythmOS, Decision Context	Yes	No	Step 3
Mod 8: Prompt Templates	Extraction transcripts	Raw material exists	No	Step 3
Mod 9: Retrieval Patterns	14 background systems	Yes (descriptive)	No	Step 4

Key finding: Content is gathered. The gap is structured JSON transformation, not research. The bottleneck is the unbuilt expert-framework-creator skill (Step 2 domino).

Cross-Taxonomy Map 3 systems → 1

Three documents describe the same extraction system with different vocabularies. Use this table when validating skill builds against all sources.

Source Document Authority

View	Document	Authority Level	Use For
Skills	Recursive Clone v2	Primary (build spec)	What to build, layer order, skill names
Modules	PRD 4	Primary (output spec)	JSON schemas, validation criteria, module definitions
Swarm	Agentic Boarding PRD	Reference only	Partner pitch, vision, color workflows

Swarm Agent ↔ Skill ↔ Module ↔ Exec Step

Swarm Agent(s)	Skill (canonical)	Module	Exec Step	Status
Chief of Staff	boarding-orchestrator	Orchestration	7	Needs expansion
PURPLE ×7	deep-research + expert-recon	RADAR feed	Pre-1	Built (2 skills = 7 agents)
GREEN	design-system-extractor	Utility	Pre-1	Built
BLUE: Transcript	soul-extractor	Mod 1 + 7	3	Built
BLUE: Document	framework-extractor	Mod 4 + 5 + 6	3	Needs +micro-units
BLUE: Content	resource-extractor	Mod 8	3	Built
—	voice-extractor	Mod 2	3	Needs +pattern-breaking
—	expert-framework-creator	Mod 1	2	DOMINO
PURPLE: Psychology	soul-extractor (partial)	Mod 3 (CTA)	3	Partial
—	offer-extractor	Mod 3 (monetization)	3	UNBUILT
—	rubric-builder	Pass 3	2–3	Needs dual validation
—	gap-analyzer	Pass 4	3	Built
Builder: SysPrompt	clone-compiler	Deploy	6	Needs expansion
Builder: Lead Magnet	lead-magnet-builder	PRD 7	1	Built
Builder: Onboarding	onboarding-builder	PRD 7	1	Built
Builder: Offer Page	no skill	PRD 9	10	GAP
—	clone-tester	Validation	5	UNBUILT
—	demo-compiler	Pre-deal	7+	UNBUILT
YELLOW	no skill	N/A	N/A	Deprioritized
RED	no skill	N/A	N/A	GoDaddy MCP exists
—	masterybook-sync	Utility	Pre-1	Built
—	no skill	Mod 9	4	GAP

Coverage Matrix PRDs vs. skills vs. steps

Every PRD mapped to: which execution step needs it, which skills implement it, and current status. Sorted by execution priority.

PRD	Title	Exec Step	Skills	A360 Priority	Status
4	Expert Extraction Pipeline	2–5	expert-framework-creator, soul/voice/framework/resource/offer-extractor, rubric-builder, gap-analyzer, clone-tester	CRITICAL	Pipeline spec done. Domino skill unbuilt.
7	Dynamic Experience Generation	1, 6	clone-compiler, lead-magnet-builder, onboarding-builder	HIGH	Wave 1 deployed (v6.1). Wave 2 needs modular extraction.
1	Org Registry + Entity Schema	Pre-1	boarding-orchestrator (workspace init)	Done for Samuel	Samuel workspace exists.
2	Data Gate Architecture	Pre-1	deep-research, expert-recon	Done for Samuel	Samuel at Gate 2 (prospect intel).
12	Batch SKILL.md Generation	7	boarding-orchestrator, skill-creator	Platform	Not started. Post-extraction.
5	Competitor Intel + Marketing Rubric	8	No skill	Step 8	PRD written. No implementation.
8	Content Machine + Syndication	9	No skill	Step 9	PRD written. No implementation.
3	Universal Content Ingestion	7+	No skill (Forge service)	Platform	Samuel’s content manually ingested.
9	The Reveal — JV Pipeline	10	No skill	Step 10	PRD written. No implementation.
6	Signal Engine + Daily Brief	N/A	No skill	Jason’s tool, not A360	PRD written. Forge cron needed.
10	Forge Session Logger	N/A	No skill (infra)	Platform infra	PRD written.
11	6-SILO Reconciliation	N/A	No skill (infra)	Platform infra	PRD written.

Answer to “does the tracker account for top-of-funnel intelligence?”
Expert recon (RADAR) is covered and complete for Samuel. Competitor intel (PRD 5) is Step 8 — tracked here but deferred. Signal engine (PRD 6) is Jason’s personal tool, not A360. Universal ingest (PRD 3) is platform infra — Samuel’s content was manually ingested. The tracker now covers all of these with clear deferral reasoning.

Temporal Log newest first

2026-03-26 | SESSION: master-lexicon-build

Master Lexicon + Full Pipeline Tracker Published

Built: Canonical lexicon with ~30 terms, retired term list, and primacy hierarchy
Expanded: Tracker now covers all 5 workstreams (was FACTORY-only)
Mapped: All 12 PRDs against execution playbook steps + skills + status
Resolved primacy: Execution Playbook #1 → Boarding Pack #2 → PRD 4 #3 → Command Center #4 → Platform PRDs #5 → Swarm PRD #6
Answered: Top-of-funnel intel = RADAR workstream. Expert recon complete for Samuel. Competitor intel = Step 8 (deferred). Signal engine = not A360.
Discovery: PRD 7 (Dynamic Experience) is the agent-first vision. Proof of concept IS Align360. Steps 1-6 deliver it progressively.
Discovery: Module 9 (Retrieval Patterns) has no skill AND no swarm agent. True gap — needs skill for Step 4.
Discovery: 3 PRDs have NO implementation path (PRDs 10, 11 = infra; PRD 6 = personal tool). Not blocking anything.

Second-order effects:

Canonical lexicon prevents terminology drift in all future skill builds, CLAUDE.md updates, and docs
Execution step mapping prevents scope creep (building platform features when Align360 needs extraction)
Clear deferral reasoning prevents “is this a gap or a choice?” confusion
Supersedes pipeline-reconciliation.html — this is now the canonical tracker

Execution Playbook Boarding Pack Command Center PRD 4 PRD 5 PRD 6 PRD 7

2026-03-26 | SESSION: full-reconciliation-review

Initial Pipeline Reconciliation — 6 Source Documents Reviewed

Three taxonomies (Swarm/Skills/Modules) identified and mapped
“Gates” terminology collision discovered → resolved: Boarding Milestone vs. Data Gate
expert.align360.io/index = 404. boarding-architecture = superseded.
No skill files modified since 2026-03-10 (spring break pause)
Vision shift: GUI → agent-first. Labs → implementation partner.

Original Pipeline Tracker

2026-03-25 | SESSION: will-derek-aaron-call

Team Call — Labs Pivot, GTM, Agent-First Vision

Labs deprioritized → implementation partner for MasteryOS
Aaron Swensen joining as implementation/content builder
Tony Gaskins meeting in ~1 month. Mid-April: dual operating systems.
Clone messaging: “10x monetization” not “own your IP”

2026-03-24 | SESSION: sumit-dev-standup

Dev Standup — Agent Branch, Samuel ETA

Samuel pressing for access. Cross-tenant login bug. Hidden admin plan needed.
Agent coding branch strategy. Claude Code doing all coding by mid-April.
Vision: A360 as AGENT, not structured UI.

2026-03-10 | SESSION: skill-build-sprint

14 Skills Built — Sprint Freeze

14 skills finalized. Samuel Layer 0 recon complete.
4 skills remaining. v2 architecture published.

Session Handoff Protocol updated

1. Read Order (new sessions)

#	File	Purpose
1	This page (master-lexicon.html)	Canonical terms, primacy, execution steps, full workstream status
2	`memory/MEMORY.md`	Project memory, team, architecture overview
3	`memory/reconciliation.md`	Compact reconciliation state for context window
4	Relevant SKILL.md for skill being built	Current skill spec
5	Execution Playbook	10-step sequence (if unsure what to build next)

2. Post-Build Checklist

Action	Where
Add temporal log entry	This page → #log
Update skill/module status	This page → #workstreams
Queue any MAP changes	pipeline-tracker → #change-queue
Update memory/reconciliation.md	Local memory file
Republish this page	plan.jasondmacdonald.com/master-lexicon
Use canonical terms from #lexicon	All outputs

3. Current Build Priority

#	Action	Exec Step	Why
1	Build expert-framework-creator (L0.25)	Step 2	Critical domino. Module 1. Everything cascades.
2	Run Module 1 on Samuel’s material	Step 2	Validates pipeline + produces customer artifact
3	Expand extractors for structured JSON	Step 3	Transforms gathered content into modular units
4	Build offer-extractor (L2)	Step 3	Covers Module 3 + monetization positioning
5	Build clone-tester (L3.5)	Step 5	Closes quality loop with 85%+ threshold
6	Build demo-compiler (L0.5)	Step 7+	Non-blocking, for Tony Gaskins JV meeting