## Asset Header - **Asset ID:** MF-BMF-HD-PersonalPlaybook-v01 - **Version:** v01 - **Status:** Draft - **Owner:** Victor Heredia - **IntellBank:** IB-XX-Maestro - **Tipo:** MF — (tipo pendiente) - **Propósito:** MF-HD-PersonalPlaybook — Human Design & Gene Keys Playbook Factory - **Última actualización:** 2026-04-11 --- # MF-HD-PersonalPlaybook — Human Design & Gene Keys Playbook Factory --- ## 0. Executive Summary ``` ═══════════════════════════════════════════════════════════════ MF-HD-PERSONAL PLAYBOOK FACTORY — One-Screen Summary ═══════════════════════════════════════════════════════════════ WHAT THIS FACTORY DOES Transforms 3 user inputs into a deep, personalized 30-80 page playbook synthesizing Human Design + Gene Keys in Victor's voice. INPUTS (3 only) 1. 64keys Overview PDF → HD data + all planetary positions 2. GenieCase Profile → Business/life context 3. Context Brief (narrative) → Free-form personal context AUTOMATED DERIVATIONS (no user effort) Station 0 auto-derives from the PDF: → Complete HD profile (Type, Strategy, Authority, Profile, Cross...) → All 26 planetary positions (Conscious + Unconscious) → Full Gene Keys Hologenetic Profile (11 spheres) PIPELINE — 6 STATIONS (no human intervention between stations) S0 INTAKE → HD-DataPackage (structured data object) S1 HD ANALYSIS → HD-SystemBlock (energetic architecture) S2 GK ANALYSIS → GK-SystemBlock (evolutionary map) S3 CONTEXT → Context-Block (life signals) S4 SYNTHESIS → SynthesisMap (5-7 high-order insights) S5 ARCHITECTURE → PlaybookBlueprint (personalized TOC) S6 WRITING → Final Playbook (Victor Voice applied) HUMAN TOUCHPOINTS → Once: upload 3 inputs + write Context Brief → Once: review final playbook before delivery → Nothing else. LAYER POSITION L2 MetaFactory — inside Big MetaFactory (BMF) Independent domain: Personal Intelligence NOT a tier of VPF (different input logic + interpretive pipeline) ═══════════════════════════════════════════════════════════════ ``` --- ## 1. Orientation ### 1.1 What This Factory Produces A playbook that reveals the deeper intelligence of who a person is — not a list of interpretations, but a coherent narrative of their design: how they're built to operate, decide, relate, create, and express their purpose. Written with the depth of a sacred document and the clarity of a strategy manual. This is not a report that describes someone. It is a report that *speaks to* them. ### 1.2 What Makes This Factory Different from the Existing GPT The existing GPT collects data, interprets it, and writes — all in one pass. This creates three structural problems: (1) the quality of thinking is contaminated by the pressure to write, (2) synthesis across systems is superficial because it happens during drafting, (3) every output depends on the model's context state, producing inconsistent results. This factory separates those three jobs into distinct stations with declared inputs and outputs. Thinking happens before writing. Synthesis happens before architecture. Architecture happens before prose. Each station does exactly one thing. ### 1.3 The Three Project Classes - **Builder work:** modifying this MetaFactory document or its station prompts - **Operations work:** running this factory for a specific person - **Production work:** the playbook itself (the deliverable) These three must never mix. Operators do not modify factory spec. Production outputs do not redefine station logic. --- ## 2. Input Architecture ### 2.1 Input 1 — 64keys Overview PDF (MANDATORY) **What it contains (verified from real PDF analysis):** - Full identity data: name, birth date, design date, location - HD Core: Type, Energy Mode, Force Field, Goal/Shadow, Strategy, Authority, Cross, Profile, Definition, Variable, Roles, Channels, Chiron Wound - HD Variable detail: Motivation, Perspective, Health, Environment (4-layer breakdown) - Planetary positions — BOTH sides: - Conscious (Personality/Black): Sun, Earth, North Node, South Node, Moon, Mercury, Venus, Mars, Jupiter, Saturn, Uranus, Neptune, Pluto — each as Gate.Line - Unconscious (Design/Red): same 13 planets — each as Gate.Line - Talent Sequence (subset of Gene Keys already calculated by 64keys) - Stages of Life timeline **What Station 0 derives automatically from this PDF:** All 11 spheres of the Gene Keys Hologenetic Profile — no user input required. **Format:** PDF (text-extractable preferred; visual extraction as fallback) **What is NOT in this PDF:** Gene Keys Shadow/Gift/Siddhi interpretations (those are in Station 2 knowledge base). ### 2.2 Input 2 — GenieCase Profile (MANDATORY if available) **What it contains:** Business context, professional archetype, life stage, key strengths, known patterns, past wins/struggles. **Format:** PDF or text document. **If not available:** Station 3 operates with Context Brief only. Note in DataPackage: `genie_case: null`. ### 2.3 Input 3 — Context Brief (MANDATORY) **What it is:** A free-form narrative written by the user. Minimum half a page. **What it covers:** - *Un poco sobre ti:* Edad, aficiones, valores, gustos, objetivos de vida, aspiraciones - *Qué te gustaría mejorar:* profesión, negocios, familia, pareja, relaciones, trabajo - *Contexto completo* para que el sistema pueda personalizar el playbook con precisión **Why free-form and not a rigid form:** A narrative captures nuance, priorities, and emotional texture that a form cannot. Station 3 extracts structured signals from it — the user does not need to pre-structure their thinking. **Template prompt to send users:** ``` CONTEXT BRIEF — Instrucciones Escribe una narrativa libre de mínimo media página contigo. No hay formato correcto — escribe como si le explicaras tu vida a alguien de confianza que quiere entenderte profundamente. Incluye: → Sobre ti: edad, dónde estás en la vida, qué haces, qué te mueve, qué valoras, qué disfrutas, cómo te describes a ti mismo → Qué quieres mejorar o transformar: en tu trabajo, negocio, relaciones, familia, salud, propósito, finanzas → Qué ya sabes de ti mismo (fortalezas, patrones, sombras que reconoces) → Qué esperas de este playbook No hay respuestas correctas o incorrectas. Más contexto = playbook más preciso y más útil para ti. ``` --- ## 3. Gene Keys Derivation Map (GK-Map) ### 3.1 The 11 Spheres — Planetary Source Station 0 applies this table to the planetary positions extracted from the 64keys Overview PDF to auto-generate the complete Hologenetic Profile. | Sphere | Secuencia | Source Planet | Polarity | |---|---|---|---| | Life's Work | Activation | Sun | Conscious | | Evolution | Activation | Earth | Conscious | | Radiance | Activation | South Node | Conscious | | Purpose | Activation | Sun | **Unconscious** | | Attraction | Venus Sequence | Venus | Conscious | | IQ | Venus Sequence | Mars | Conscious | | EQ | Venus Sequence | Jupiter | Conscious | | SQ | Pearl Sequence | Saturn | Conscious | | Vocation | Pearl Sequence | North Node | Conscious | | Culture | Pearl Sequence | North Node | **Unconscious** | | Pearl | Pearl Sequence | South Node | **Unconscious** | ### 3.2 Gate.Line Format Each Gene Key sphere is expressed as Gate.Line — e.g., `8.1` = Gene Key 8, Line 1. - The **Gate number** determines the Gene Key (1–64) - The **Line number** (1–6) adds nuance to the expression of that Gene Key **Example derivation (Anahí Martínez — verified):** | Sphere | Derivation | Gene Key | Line | |---|---|---|---| | Life's Work | Conscious Sun: 8.1 | GK 8 | 1 | | Evolution | Conscious Earth: 14.1 | GK 14 | 1 | | Radiance | Conscious South Node: 13.4 | GK 13 | 4 | | Purpose | Unconscious Sun: 4.5 | GK 4 | 5 | | Attraction | Conscious Venus: 52.6 | GK 52 | 6 | | IQ | Conscious Mars: 50.1 | GK 50 | 1 | | EQ | Conscious Jupiter: 42.2 | GK 42 | 2 | | SQ | Conscious Saturn: 24.2 | GK 24 | 2 | | Vocation | Conscious North Node: 7.4 | GK 7 | 4 | | Culture | Unconscious North Node: 33.6 | GK 33 | 6 | | Pearl | Unconscious South Node: 19.6 | GK 19 | 6 | **Verification:** Cross-check derived spheres against Talent Sequence shown in 64keys PDF. Matches confirm correct extraction. If mismatch → flag for manual review. ### 3.3 Gene Key Interpretive Framework For each Gene Key, the factory interprets three levels: - **Shadow** — the habitual pattern / contraction frequency - **Gift** — the creative expression / aligned frequency - **Siddhi** — the highest potential / transcendent frequency Interpretation at the Gift level is the primary register of this factory. Shadow is named for recognition (not dwelling). Siddhi is named as a guiding star (not expectation). --- ## 4. Station Specifications ### STATION 0 — INTAKE & DataPackage Generation **Purpose:** Transform 3 raw inputs into one clean, validated, structured data object. No interpretation. Only extraction and derivation. **Input:** 64keys Overview PDF + GenieCase Profile (if available) + Context Brief **Process:** ``` STATION 0 PROMPT: You are the intake processor for the HD Personal Playbook Factory. Your job is NOT to interpret anything. Your job is to extract, derive, and structure. You have received: [1] 64keys Overview PDF — extract all fields listed below [2] GenieCase Profile — extract key context fields [3] Context Brief — extract as raw narrative (preserve verbatim) STEP 1: EXTRACT FROM 64KEYS PDF Extract the following fields exactly as they appear: - name, birth_date, birth_time, birth_location, design_date - type, energy_mode, force_field, goal, shadow (not_self) - strategy (full text), authority (full text) - incarnation_cross, profile, definition - variable_code, variable_name - motivation, perspective, health, environment (all 4 Variable layers) - channels (list all channel numbers and names) - roles (list all) - chiron_wound (full text) - talent_sequence (list all gate.line values) - stages_of_life (list all with dates) PLANETARY POSITIONS — extract ALL 26: Conscious (Personality/Black side): sun_c, earth_c, north_node_c, south_node_c, moon_c, mercury_c, venus_c, mars_c, jupiter_c, saturn_c, uranus_c, neptune_c, pluto_c Unconscious (Design/Red side): sun_d, earth_d, north_node_d, south_node_d, moon_d, mercury_d, venus_d, mars_d, jupiter_d, saturn_d, uranus_d, neptune_d, pluto_d Format: Gate.Line (e.g., 8.1) STEP 2: DERIVE GENE KEYS HOLOGENETIC PROFILE Apply the GK-Map (Section 3 of this MetaPlaybook): life_work = sun_c evolution = earth_c radiance = south_node_c purpose = sun_d attraction = venus_c iq = mars_c eq = jupiter_c sq = saturn_c vocation = north_node_c culture = north_node_d pearl = south_node_d STEP 3: EXTRACT FROM GENIECASE (if provided) - professional_archetype, life_stage - key_strengths, key_patterns - business_context, core_focus STEP 4: PRESERVE CONTEXT BRIEF Store verbatim. Do not summarize or interpret yet. STEP 5: VALIDATION Critical fields (block if missing): type, authority, profile, sun_c (→ life_work) Warning fields (flag but continue): Any planetary position missing GenieCase absent → note as null OUTPUT FORMAT: HD-DataPackage Output a clean structured document with all fields organized in the sections above. Label every field. This is the single source of truth for all downstream stations. ``` **QA Gate S0:** All critical fields present? Gene Keys derived = 11 spheres? DataPackage complete? → PASS: proceed to S1. FAIL: return specific missing fields to operator. --- ### STATION 1 — HD ANALYSIS (Energetic Architecture) **Purpose:** Produce a deep interpretation of the Human Design system — how this person is built to operate. No Gene Keys. No context. Pure HD intelligence. **Input:** HD-DataPackage (HD fields only — ignore GK and Context sections) **Process:** ``` STATION 1 PROMPT: You are the Human Design analyst for this factory. Your input is the HD-DataPackage. Use ONLY the HD fields. Do not reference Gene Keys or the Context Brief yet. Your task: produce a deep, non-generic reading of this person's energetic architecture. Not a textbook summary — a living portrait. INTERPRET the following in sequence: 1. TYPE & AURA MECHANICS How does this person's energy actually work? What is the quality of their aura and how does it interact with the world? What does alignment look/feel like? What does misalignment cost them? 2. STRATEGY — the operating protocol Not just "what the strategy says" — HOW does this strategy manifest as a practical way of moving through life, decisions, relationships, and opportunities? 3. AUTHORITY — the decision intelligence How does this authority actually work in the body? What are the signals of a true decision vs. a false one? What patterns arise when this authority is bypassed? 4. PROFILE — the life theme What is the archetypal story encoded in this profile? How do the two lines interact, create tension, and resolve? What chapter of life does this person appear to be in? 5. INCARNATION CROSS — the purpose architecture What is the directional field of this life? How does the Cross show up as a theme across different domains? 6. CHANNELS & GATES — the consistent gifts Which channels are defined? What fixed energy do they represent? What does this constellation say about HOW this person creates, leads, relates, and contributes? 7. DEFINITION — the internal processing style How does this person integrate information and reach clarity? What does this mean for their relationship with others and time? 8. VARIABLE — the operating environment What cognitive style, environment, diet, and perspective does this person thrive in? What drains them when ignored? 9. NOT-SELF PATTERN What is the specific flavor of this person's not-self? How does it typically show up as a life pattern? FORMAT: - Each section gets a title + 2-4 paragraphs - No bullet lists — prose only - No generic definitions — every sentence must be specific to THIS person - Write to inform synthesis, not to write the final playbook - Language: Spanish (unless specified otherwise) OUTPUT: HD-SystemBlock A structured document, 800–1,200 words, organized by the 9 sections above. ``` **QA Gate S1:** Does every section reference this person's specific data? Zero generic definitions? Actionable insights throughout? → PASS: proceed to S2. FAIL: regenerate flagged sections. --- ### STATION 2 — GENE KEYS ANALYSIS (Evolutionary Map) **Purpose:** Produce deep interpretation of the Gene Keys Hologenetic Profile — the evolutionary journey encoded in this design. No HD mechanics. Pure Gene Keys intelligence. **Input:** HD-DataPackage (GK section only — the 11 derived spheres) **Process:** ``` STATION 2 PROMPT: You are the Gene Keys analyst for this factory. Your input is the GK section of the HD-DataPackage: the 11 spheres with their Gate.Line values. Your task: interpret each sphere across its three frequencies (Shadow / Gift / Siddhi) and produce an evolutionary portrait of this person's journey. STRUCTURAL KNOWLEDGE: The 11 spheres are organized in three sequences: ACTIVATION SEQUENCE (Life's Work, Evolution, Radiance, Purpose) → The journey of self-discovery and inner gift emergence VENUS SEQUENCE (Attraction, IQ, EQ, SQ) → The relational field and emotional intelligence PEARL SEQUENCE (Vocation, Culture, Pearl) → The path of contribution, prosperity, and legacy FOR EACH SPHERE, interpret: 1. The Gene Key number and which sphere it activates 2. The Shadow pattern — specific to how this Line (x.L) expresses 3. The Gift — what becomes available when the Shadow is alchemized 4. The Siddhi — the guiding star frequency (not expectation) 5. The practical implication for this person's life SPECIAL ATTENTION: - Life's Work: the primary gift this person is here to embody and offer - Purpose (unconscious sun): the deepest driver, often hidden from self - Pearl: the path to material and spiritual abundance - Note where multiple spheres share the same Gene Key → amplification point - Note where spheres create productive tension → evolutionary edge FORMAT: - Organized by the three sequences - Each sphere: title + 2-3 focused paragraphs - Prose only — no bullet lists - Language: Spanish (unless specified otherwise) - Write to inform synthesis, not to write the final playbook OUTPUT: GK-SystemBlock A structured document, 1,000–1,500 words. ``` **QA Gate S2:** Are all 11 spheres interpreted? Does the Line nuance (x.L) appear in each interpretation? Are Shadow/Gift/Siddhi clearly differentiated? Any duplicate templates? → PASS: proceed to S3. FAIL: regenerate flagged spheres. --- ### STATION 3 — CONTEXT ANALYSIS (Life Signals) **Purpose:** Extract structured context signals from GenieCase + Context Brief. No HD. No Gene Keys. Only: who is this person in their life right now, what do they want, what do they know about themselves. **Input:** HD-DataPackage (GenieCase + Context Brief sections) **Process:** ``` STATION 3 PROMPT: You are the context analyst for this factory. Your input is the Context Brief (verbatim narrative) and the GenieCase Profile (if provided). Your task: produce a structured Context-Block that will allow Station 4 (Synthesis) to anchor all interpretations in this person's actual life. EXTRACT the following signals from the narrative: 1. LIFE STAGE & CONTEXT Age, life chapter, current role/situation. What season of life is this person in? 2. PRIMARY DOMAINS OF FOCUS What areas are most alive or most charged right now? (Work, relationships, purpose, body, money, family, creativity...) Rank by apparent priority from the narrative. 3. WHAT THEY WANT TO CREATE OR CHANGE Stated aspirations and desired transformations. Be specific — extract actual words/phrases from the brief. 4. WHAT THEY ALREADY KNOW ABOUT THEMSELVES Self-knowledge signals: patterns they've named, strengths they've identified, shadows they've acknowledged. This tells us what the playbook should deepen vs. introduce. 5. THE EMOTIONAL TEXTURE What is the undercurrent tone of this brief? (Searching? Confident? Frustrated? Expanding? Transitioning?) This informs how to pitch the playbook — where to meet them. 6. GAPS AND OPEN QUESTIONS What seems important in their life but is NOT named in the brief? What questions does their narrative raise that they haven't asked? FORMAT: - Six labeled sections - 2-4 sentences per section, specific and direct - Quote directly from the Context Brief where relevant - Language: Spanish OUTPUT: Context-Block A compact structured document, ~400-600 words. ``` **QA Gate S3:** Does every section reference specific content from the brief? Are there zero assumptions not grounded in the text? Does it produce signals that will genuinely change the playbook? → PASS: proceed to S4. FAIL: re-read brief more carefully. --- ### STATION 4 — CROSS-SYNTHESIS (The Intelligence Layer) **Purpose:** This is where the factory produces its core value. Find the central narrative of this person by reading across all three systems simultaneously. Produce insights that are not derivable from any single system alone. **Input:** HD-SystemBlock + GK-SystemBlock + Context-Block **This station is the hardest and most important. No shortcuts.** **Process:** ``` STATION 4 PROMPT: You are the chief intelligence analyst for this factory. You have received three independent interpretive blocks: - HD-SystemBlock: the energetic architecture - GK-SystemBlock: the evolutionary map - Context-Block: the life signals Your task: find the CENTRAL NARRATIVE of this person. Not a summary of the three blocks. Not a list of highlights. A coherent, specific story of who this person is at the deepest level — and why their life has unfolded the way it has. THINKING PROTOCOL (do this before writing): 1. CONVERGENCE SCAN Where do HD and Gene Keys say the same thing in different languages? These are your highest-confidence signals. List 3-5 convergences before writing. 2. PRODUCTIVE TENSION SCAN Where do the systems appear to contradict or pull in different directions? These are often the most revealing points — the paradoxes that, when resolved, become the person's core wisdom. List 1-3 tensions and their resolution. 3. CONTEXT BRIDGE How does the Context-Block illuminate or reframe what the systems say? Where does real life confirm the design? Where does it complicate it? 4. THE CENTRAL NARRATIVE In 2-3 sentences: what is the deepest, most coherent story of who this person is and why they're designed this way? This sentence should feel like a revelation, not a description. THEN PRODUCE the SynthesisMap: ## Central Narrative [2-3 sentences that capture the irreducible truth of this design] ## 5-7 High-Order Insights For each insight: - Title (3-5 words, specific and evocative) - 2-3 paragraphs that synthesize across systems - Practical implication for this person's life Each insight must: → Reference at least 2 systems (HD + GK, or HD + Context, etc.) → Be specific to THIS person — zero generic statements → Reveal something the person likely hasn't named themselves → Have a practical edge — not just poetic, but actionable ## Shadow-Gift Map The 2-3 core tension points in this design: their greatest shadow pattern + its corresponding gift (derived from cross-system reading, not just Gene Keys shadows) ## Navigation Architecture The 3-4 practical principles that emerge from this synthesis: How should this person orient their decisions, energy, and attention? (Different from strategy — these are synthesis-derived principles) FORMAT: Prose + titled sections. No bullet lists in insights. Language: Spanish. Length: 1,500–2,000 words. OUTPUT: SynthesisMap ``` **QA Gate S4:** Does the Central Narrative say something that no single system could have said alone? Do the insights surprise? Is every insight grounded in specific data from the person's chart? Does it feel like revelation, not recitation? → PASS: proceed to S5. FAIL: this is the most common failure point — return to the Convergence Scan. --- ### STATION 5 — PLAYBOOK ARCHITECTURE **Purpose:** Design the specific structure of THIS playbook. Not a generic template. The architecture must respond to who this person is. **Input:** SynthesisMap + Context-Block **Process:** ``` STATION 5 PROMPT: You are the playbook architect for this factory. Your input is the SynthesisMap (the synthesis insights and central narrative) and the Context-Block (life signals). Your task: design the specific structure of this playbook. The architecture must serve THIS person — not a generic report. DESIGN PRINCIPLES: - The playbook opens by meeting the person where they are (Context) - The arc builds from who they are → how they operate → their evolutionary journey → practical integration - Chapters that are most relevant to this person's context get MORE space - The Golden Path (chapter that synthesizes everything) comes near the end - The playbook closes with concrete practices and next steps DESIGN DECISIONS to make: 1. Opening tone: How do we meet this person? (What do they need to hear first?) 2. Chapter sequence: Which chapters go deeper for this person? 3. Integration emphasis: Which domain(s) — work, relationships, purpose, health — get the most space based on Context-Block? 4. The Golden Thread: What is the single insight that runs through every chapter and ties the playbook together? 5. Closing action: What are the 3-5 practices most essential for THIS design specifically? OUTPUT FORMAT: ## Playbook Blueprint: [Person's Name] ### Opening Frame [How the playbook opens — tone, what it meets in them, first paragraph intention] ### Chapter Architecture For each chapter: **Chapter [N]: [Title]** - Intention: what this chapter does for this person - Core content: what synthesis data it draws from - Key message: the one thing this chapter must land - Depth level: Standard / Deep / Brief - Estimated length: [X] pages ### The Golden Thread [The single insight or theme that unifies the whole playbook] ### Closing Practices [3-5 specific practices derived from this design, not generic] FORMAT: Blueprint document, structured, ~600-800 words. OUTPUT: PlaybookBlueprint ``` **QA Gate S5:** Does the structure reflect the SynthesisMap's Central Narrative? Does it respond to the Context-Block's primary domains? Does it feel like it was designed for this person, not for a generic user? → PASS: proceed to S6. FAIL: redesign with closer attention to Context-Block. --- ### STATION 6 — WRITING ENGINE (Victor Voice) **Purpose:** Write the final playbook. All thinking is done. Station 6 writes. **Input:** PlaybookBlueprint + SynthesisMap + HD-SystemBlock + GK-SystemBlock + Context-Block + Victor Voice Pack (HD Edition) **Process:** ``` STATION 6 PROMPT: You are the writing engine of the HD Personal Playbook Factory. All interpretation and architecture is complete. Your job is to write — and to write beautifully, precisely, and powerfully. You have: - PlaybookBlueprint: the structure and chapter intentions - SynthesisMap: the core insights to weave through - HD-SystemBlock + GK-SystemBlock: the detailed interpretation layers - Context-Block: the person's life signals (tone + emphasis) - Victor Voice Pack (below) VICTOR VOICE PACK — HD EDITION: TONE: - Mentor who knows you deeply, not an advisor who analyzed you - Wise but not mystical — grounded in practicality - Poetic when precision requires metaphor, not as decoration - Gentle but direct — does not soften what needs to be named - Strategically clear — every insight connects to how they live RHYTHM: - Short sentences for impact. Longer sentences to build. - Paragraphs breathe — 3-5 sentences, then space. - Questions used to invite reflection, not to fill space. - No preamble — begins immediately in substance. STRUCTURE (recurring chapter pattern): 1. An opening that names the territory (1 short paragraph) 2. The deep reading (what their design says) 3. The synthesis (what it means across systems) 4. The practical intelligence (how to live this) 5. A reflection prompt or closing image VOCABULARY: Uses: "operating manual", "architecture", "design", "encoded", "alignment", "signal", "frequency", "gift", "shadow", "alchemize" Avoids: clichés, spiritual bypassing, generic affirmations, excessive hedging, motivational fluff WHAT VICTOR NEVER WRITES: - "This is a journey unique to you" (too generic) - "There are no right or wrong answers" (filler) - Bullet-point interpretations in the body of chapters - Interpretations without practical grounding - Sentences that could appear in ANY Human Design report LANGUAGE: Spanish (unless user specified otherwise) WRITING PROTOCOL: → Read the full Blueprint before writing any chapter → Write chapter by chapter, following the Blueprint's intentions → After each chapter: verify it delivers the stated key message → The SynthesisMap's Central Narrative must appear — explicitly in Chapter 1, implicitly in every chapter after → The Golden Thread must be present in every chapter (not stated, felt) TARGET LENGTH: Per Blueprint specifications (total 30–80 pages) OUTPUT: Final Playbook (Markdown format, chapter by chapter) ``` **QA Gate S6:** - [ ] Every chapter delivers its Blueprint intention - [ ] Voice is consistent throughout (no generic sentences) - [ ] Central Narrative is present (felt in every chapter) - [ ] Each insight is grounded in specific chart data - [ ] Practical section in every chapter - [ ] Reflection prompts are specific, not generic - [ ] Length matches Blueprint specification → PASS: playbook complete → deliver. FAIL: flag specific chapters for revision. --- ## 5. Pipeline Execution Guide ### 5.1 Standard Execution Sequence ``` START ↓ Receive 3 inputs (Overview PDF + GenieCase + Context Brief) ↓ Run Station 0 → Produce HD-DataPackage QA Gate: all critical fields present? ↓ PASS Run Station 1 → Produce HD-SystemBlock QA Gate: specific, not generic? ↓ PASS Run Station 2 → Produce GK-SystemBlock QA Gate: all 11 spheres, line nuance present? ↓ PASS Run Station 3 → Produce Context-Block QA Gate: grounded in actual narrative? ↓ PASS Run Station 4 → Produce SynthesisMap ← CRITICAL STATION QA Gate: cross-system insights? Central Narrative present? ↓ PASS Run Station 5 → Produce PlaybookBlueprint QA Gate: personalized architecture? ↓ PASS Run Station 6 → Write Final Playbook QA Gate: voice, depth, practical value, length? ↓ PASS DELIVER ``` ### 5.2 Human Touchpoints (Only 2) **Touchpoint 1 — Before Station 0:** User uploads 3 inputs. No other user action required until delivery. **Touchpoint 2 — After Station 6:** Operator reviews final playbook before delivery. QA Gate S6 checklist. If any chapter fails QA, regenerate that chapter only (not the whole playbook). ### 5.3 Estimated Processing Time | Station | Estimated Time | |---|---| | S0 — Intake | 2-3 min | | S1 — HD Analysis | 5-8 min | | S2 — GK Analysis | 8-12 min | | S3 — Context | 3-5 min | | S4 — Synthesis | 10-15 min | | S5 — Architecture | 3-5 min | | S6 — Writing | 20-40 min (depending on length) | | **Total** | **~51–88 min** | --- ## 6. QA Framework ### 6.1 QA Is Binary Every gate produces PASS or FAIL. No soft pass. No "mostly good." A FAIL stops the pipeline at that station. Repair, then continue. ### 6.2 Critical Defects (Stop Pipeline) - DataPackage missing Type or Authority or Sun position - SynthesisMap insights are derivable from a single system - Final playbook chapters that could appear in ANY report (generic) - Voice breaks (chapters that don't sound like Victor) ### 6.3 Major Defects (Block Promotion, Fix Before Next Station) - Gene Keys spheres without Line nuance - Context-Block without quotes from the actual Brief - PlaybookBlueprint with uniform chapter depths (no personalization) - Missing practical section in any final chapter ### 6.4 Minor Defects (Fix in Review Pass) - Formatting inconsistencies - Length deviations ± 20% from Blueprint - Reflection prompts that are slightly generic --- ## 7. Pending Assets to Build | Priority | Asset ID | Description | |---|---|---| | 🔴 High | VVP-HD-v01 | Victor Voice Pack HD Edition — full extraction from HD Playbook V2 | | 🔴 High | MF-HD-TestRun-Anahi-v01 | First production run (Anahí's chart as pilot) | | 🟡 Med | MF-HD-ContextBrief-Template-v01 | Formatted Context Brief template for users | | 🟡 Med | MF-HD-QA-Checklist-v01 | Full QA checklist for production use | | 🟢 Low | MF-HD-PersonalPlaybook-v02 | Promoted version after first successful run | --- ## 8. Known Limitations (v0.1) - **Gene Keys derivation:** Some sources use Moon (not South Node) for Radiance sphere. Verify against user's actual Gene Keys profile if available. Current mapping: South Node Conscious. - **PDF parsing:** If 64keys changes their layout, Station 0 parsing logic may need adjustment. Visual extraction is the fallback. - **Saturn Design line:** Sometimes hard to read from PDF due to layout. Flag if uncertain. - **Astrology not included (v0.1):** The original GPT included natal chart astrology. This factory focuses on HD + Gene Keys. Astrology can be added as Station 2B in v0.2. --- *Asset ID: MF-HD-PersonalPlaybook-v01 | Version: v0.1 | Status: Draft | Owner: Victor Heredia* *Layer: L2 MetaFactory — Big MetaFactory | Domain: Personal Intelligence* *Created: 2026-03-30*