MasteryMade · Reconciliation
How the Align360 build maps to the universal intelligence architecture. What's aligned, what's a vocabulary collision, and what the lower-order PRDs need to address.
March 25, 2026 · v2 (corrected)
Align360 (Samuel Ngu) is the first JV partner being deployed through the MasteryMade system. The align360 build artifacts — boarding pack, command center, design system, Wiring for Impact prototype, betaapp.io deployment — represent the PLAN → BUILD → RECURSIVE REVIEW → UPDATE → MAKE SKILL TO DUPLICATE pipeline in action. Samuel is the test case for flushing out every piece of the universal architecture.
The align360 pages at align360.asapai.net and design.align360.io are Jason's working documents for the expert extraction process — not user-facing product docs. The user-facing product lives at align360.betaapp.io.
| Align360 Artifact | Registry PRD | Status | Notes |
|---|---|---|---|
| Boarding Pack (8-section spec) | PRD 4 (Expert Extraction) + PRD 9 (The Reveal pipeline) | In Process | The boarding pack IS the extraction process documentation. Contains raw gathered IP (transcripts, knowledge files, governance doc). The structured 9-module extraction (PRD 4) is the NEXT step — converting this gathered material into modular, validated, JSON-structured output. |
| IP Inventory (36 stacks + 14 background) | PRD 4 Module 4 (Embedded IP) + Module 5 (Modularization) + Module 6 (Meta-Structures) | Gathered | Comprehensive catalog exists. Needs conversion from list format to structured Module 4/5/6 JSON with retrieval pointers (Module 9). The 14 background systems map to Module 9 retrieval patterns. |
| FLC Wisdom Framework + Tri-Filter | PRD 4 Module 1 (Thinking Structures / RUBRIC) | Buried | The Module 1 rubric likely EXISTS in the extraction transcripts and governance doc — FLC 5-layer framework IS the thinking rubric. Needs to be explicitly extracted as structured JSON and validated. May already be partially captured in System Prompt v6.1 but in monolithic form, not modular. |
| 9 Wiring Types + 5 Orientations | PRD 4 Module 4 (Embedded IP) + Module 7 (Pattern Recognition) | Gathered | Well-documented in boarding pack. The typing system IS Module 7 diagnostic patterns (how the expert assesses users). Career mappings per type are Module 5 (modularization — teaching progressions per wiring type). |
| Brand Voice spec ("pastoral but direct, 8th grade...") | PRD 4 Module 2 (Voice and Style) | Documented | Clear voice rules in boarding pack. Needs conversion to Module 2 JSON structure with sentence patterns, signature phrases, emphasis techniques. |
| System Prompt v6.1 | PRD 4 (all modules, monolithic) | Needs decomposition | The system prompt contains extraction output from multiple modules but in a single monolithic file. The PRD 4 pipeline would decompose this into separate module outputs with individual validation. The decomposed version becomes the meta-index (PRD 4 Section 4.9). |
| Knowledge Files Part 1 + 2 | PRD 3 (Universal Ingest) → PRD 4 (Extraction input) | Ingested | These are the raw ingested content that the extraction pipeline processes. In the universal architecture, they'd be stored as content records in Supabase (PRD 3 schema) tagged Gate 3. |
| Wiring for Impact assessment (design.align360.io) | PRD 7 (Dynamic Experience) onboarding flow + PRD 9 Phase 3 (pre-pitch asset) | Prototype | Frontend example built as a possible lead magnet idea. Not connected to backend. When the architecture is ready, this becomes the onboarding flow entry point described in PRD 7 Section 7.3 — the 3-5 discovery questions that route users to the right framework path. |
| betaapp.io deployment | PRD 11 (6-SILO) SILO 1-6 + PRD 9 Phase 6 (Deploy) | Building | Live at align360.betaapp.io. Static sidebar architecture (current MasteryOS). Stays as-is for now. Future iterations move toward PRD 7 agent-first dynamic experience — but that's future vision, not immediate action. |
| Command Center (design.align360.io) | PRD 1 (Org Registry) pattern | Aligned | The command center IS a registry dashboard for Align360 specifically. The universal org registry (PRD 1) is the portfolio-level version of this same pattern. |
| Pricing ($178/$298 annual) | PRD 9 Phase 6 (Deploy + Launch) + PRD 11 SILO 2 (Strategic Operations) | Set | Pricing locked. Monetization guardrails documented. Referral flywheel designed. Stripe integration in progress (Sumit team). |
| Partnerships (B3lieve, YM, Africa) | Not directly in PRDs | Separate track | These are Samuel's existing partnerships. They inform content strategy and audience segmentation but don't map to specific PRD architecture. May feed PRD 8 (Content Machine) for partner-specific content streams. |
The boarding pack uses "Gate 1-4" for onboarding milestones (brand assets, extraction interview, content permissions, offer approval). The master registry uses "Gate 1-4" for data scoping (Jason/operator, prospect, signed JV, competitor). These are two completely different systems using the same word.
| Boarding Pack "Gate" | What it actually is | Registry equivalent |
|---|---|---|
| Gate 1: Brand Assets | Onboarding milestone — logo, colors, fonts collected | Boarding Milestone 1 (rename to avoid collision) |
| Gate 2: Extraction Interview | Onboarding milestone — transcripts gathered | Boarding Milestone 2 |
| Gate 3: Content Permissions | Onboarding milestone — API access, email list, LinkedIn | Boarding Milestone 3 (also: this is when Gate 3 data scoping activates — expert shares private content) |
| Gate 4: Offer Approval | Onboarding milestone — pricing set, partner sign-off | Boarding Milestone 4 |
Action: Rename boarding pack gates to "Boarding Milestones" in next update. Reserve "Gate 1-4" for the data scoping architecture exclusively.
The PURPLE/GREEN/BLUE/YELLOW/RED workflow labels in the boarding pack are Athio-specific boarding process tracks. They describe parallel work happening during the onboarding. They don't map to the master registry vocabulary. Decision: keep them as internal Athio process labels for now. If they cause confusion, replace with descriptive names (Positioning Research, Brand Identity, Content Extraction, Network Mapping, Infrastructure).
The boarding pack is not "done and misaligned." It's mid-process. The plan → build → recursive review → update → make skill to duplicate pipeline is IN PROGRESS. Samuel's IP has been gathered (transcripts, governance doc, knowledge files, system prompt). The structured 9-module extraction (PRD 4) is the next step — not a missed step.
The FLC Wisdom Framework IS the Module 1 rubric — it's likely buried in the extraction transcripts and the System Prompt v6.1. It needs to be explicitly pulled out as structured JSON and validated, not re-extracted from scratch.
The goal is: once we flush out the extraction process on Samuel, we productize it as a reusable skill that duplicates for every future expert. Samuel is the test case for building the machine, not just a customer to serve.
| PRD 4 Module | Align360 source material | Extracted? | In structured JSON? |
|---|---|---|---|
| 1. Thinking Structures (RUBRIC) | FLC Wisdom Framework, Tri-Filter, Clarity Path, 7 Governing Values | Partially — in System Prompt v6.1 | No — monolithic prompt, not modular JSON |
| 2. Voice and Style | "Pastoral but direct, 8th grade, 12-18 word sentences, warm not sentimental" | Yes — in boarding pack | No — descriptive text, not Module 2 JSON |
| 3. CTA Psychology | Monetization guardrails, anti-patterns ("Laws of Babylon") | Partially | No |
| 4. Embedded IP | 36 stacks, 9 Wiring Types, 5 Orientations, named frameworks | Yes — comprehensive in boarding pack | Partially — tables exist but not in Module 4 JSON |
| 5. Modularization | Phase 0-4 progression, stack sequencing, prerequisite chains | Yes — in product architecture | No — list format, not Module 5 JSON |
| 6. Meta-Structures | 5-phase architecture, onboarding flow, Pathfinder routing | Yes — in boarding pack | No |
| 7. Pattern Recognition | 9 Wiring Types as diagnostic, RhythmOS (energy states), Decision Context Engine | Yes — in background systems | No — descriptive, not Module 7 diagnostic JSON |
| 8. Prompt Templates | Extraction transcripts contain real expert responses | Raw material exists | No — needs Q&A pair extraction |
| 9. Retrieval Patterns | 14 background systems define when/how content surfaces (Pathfinder, Prompt Logic, Cross-Phase Intelligence) | Yes — well-documented | No — descriptive, not Module 9 routing JSON |
Key finding: Most module content EXISTS in the boarding pack and system prompt — it's gathered and documented. The gap is converting from descriptive text / monolithic prompt into structured, modular, JSON-formatted extraction output per PRD 4 spec. This is a transformation task, not a research task. The raw material is rich.
Jason's correction: the 12 PRDs describe the universal system. The Align360-specific implementation details should emerge as the PRDs get drilled into lower-order levels. Here's what each PRD needs to include for Align360 specifically:
| PRD | Align360-specific detail needed |
|---|---|
| PRD 1: Org Registry | Register Samuel as entity (type=expert, gate=3, pipeline_stage=building). Register Align360 stacks as services. Create contracts between extraction pipeline and betaapp.io deployment. |
| PRD 2: Gates | Samuel's content currently in Gate 3 (signed, private docs shared). His competitors not yet identified — Gate 4 entities need creation. Content permissions (boarding milestone 3) partially block some Gate 3 ingestion (YouTube API, LinkedIn). |
| PRD 3: Ingest | Align360 test case: ingest 3 extraction transcripts + governance doc + overview PDF + system prompt + knowledge files. Future: ingest Samuel's YouTube (if/when Gate 3 content permissions granted). Research Service: run on Samuel's niche to identify competitors. |
| PRD 4: Extraction | Primary test case. Run Module 1 on existing material — FLC Wisdom Framework should emerge as rubric. Decompose System Prompt v6.1 into Modules 2-8. The 14 background systems are Module 9. The 36 stacks are Modules 4-6. Three-pass validation against actual Samuel responses from transcripts. |
| PRD 5: Competitor Intel | Identify top 5 competitors in values-based career coaching / alignment coaching space. Ingest their public content. Position Samuel relative to landscape. This doubles as a go-giver artifact for Samuel AND proves the competitor analysis pipeline. |
| PRD 6: Signal Engine | Not directly Align360-related. Jason's personal intelligence layer. But the brief engine may surface Align360-relevant articles that feed the content strategy. |
| PRD 7: Dynamic Experience | Future state for Align360. Current static sidebar stays. Next iteration: Wiring for Impact assessment as onboarding entry → agent routes user to relevant Phase 0 tools based on wiring type. The 14 background systems become the context engine behaviors. |
| PRD 8: Content Machine | Generate content briefs for Samuel's niche using his voice (Module 2) + frameworks (Module 4) + competitor gaps (PRD 5). Mastery Labs matrix applied to Align360. |
| PRD 9: The Reveal | Align360 was the first prospect through the pipeline. Phases 1-3 mostly complete (research, pre-pitch assets, boarding pack). Phase 5 (Gate 3 transition) happened — Samuel shared private docs. Phase 6 (deploy) in progress at betaapp.io. Three-wave launch template should be applied. |
| PRD 10: Session Logger | All Align360 extraction sessions should be logged. Historical sessions (the 3 extraction interviews) need to be ingested into the session archive. |
| PRD 11: 6-SILO | Align360 is deployed on current MasteryOS codebase (SILOs 1-6). Contracts for SILO 1 ↔ extraction pipeline (PRD 4) need to reference Align360's specific knowledge files and system prompt. |
| PRD 12: MANUAL.md Batch | The expert extraction skills (expert-research, expert-doc-processor, etc.) that were used on Align360 get MANUAL.md generated. Lessons learned from the Align360 extraction feed into the failure modes section of each manual. |
Jason's note: The universal content intelligence skill — which handles BOTH expert analysis AND competitor analysis using the same ingestion pipeline with different lenses — was a key design decision in this session. It's captured in PRD 3 (universal ingest) + PRD 4 (expert extraction lens) + PRD 5 (competitor intel lens). The lower-order PRD details should specify how this single skill applies to Align360 specifically: ingest Samuel's content through the expert lens, ingest his competitors through the competitor lens, same pipeline, different output.
This is the "plan → build → recursive review → make skill to duplicate" cycle. Build it once for Samuel. Review what worked. Update. Package as a reusable skill. Deploy on next expert.
| # | Action | Owner | Depends on |
|---|---|---|---|
| 1 | Ship Samuel's betaapp.io — Wiring for Impact + Phase 0 tools working for Wave 1 (5 users) | Will + Sumit | Nothing — do it now |
| 2 | Run PRD 4 Module 1 on Samuel's existing material — extract FLC Wisdom Framework as structured rubric JSON | Jason / Forge | PRD 4 spec (published) |
| 3 | Identify 5 competitors in Samuel's niche, create Gate 4 entities | Jason / agent swarm | PRD 1 entities table |
| 4 | Decompose System Prompt v6.1 into Module 2-8 structured outputs | Jason / extraction agent | Module 1 rubric validated (#2) |
| 5 | Rename boarding pack "Gates" to "Boarding Milestones" — eliminate vocabulary collision | Jason | Nothing |
| 6 | Run competitor content ingestion on identified competitors | Agent swarm / Forge | PRD 3 ingest service + #3 |
The meta-play: Every action above builds the machine while serving the customer. Module 1 extraction on Samuel teaches us how to automate Module 1 extraction. Competitor analysis on Samuel's niche teaches us how to automate competitor analysis. The skill to duplicate emerges from the doing, not from additional planning.
MASTERYMADE · Align360 Reconciliation · March 25, 2026
Dominia Facta. Build what compounds.