{
  "package_name": "Governed Capability Formation Family",
  "source_package_version": "consolidation v0.1 plus AI Capability Discipline v0.9",
  "prompt_pack_version": "v1.1-mainline-white-corrected",
  "generated_at": "2026-06-18T12:37:42Z",
  "design_authority_summary": {
    "white_family": "Mainline White — Structured Expressive — pure white, medium density, moderate panelization, elevated editorial rhythm, medium-high contrast and connector emphasis, selective #EB1700 accents, black body text, neutral gray structure.",
    "dark_family": "Dark Expressive Editorial — premium keynote-style, deeper contrast, more atmosphere, but still explanatory and enterprise credible.",
    "visible_text_rule": "Only the visible_text corpus may appear in rendered image output."
  },
  "slides": [
    {
      "slide_id": "GCF-01",
      "title": "AI Capability Playbook",
      "narrative_role": "opening thesis",
      "objective": "Introduce the family as a coherent stack, not a pile of documents.",
      "visible_text": [
        "AI Capability Playbook",
        "One problem space.",
        "Multiple layers of discipline.",
        "Doctrine, commitment, implementation, and evaluation work together."
      ],
      "white_render_prompt": "Create a sharp 16:9 editorial explainer slide.\n\n    Use Mainline White — Structured Expressive.\n\nThe background must be pure #FFFFFF white, flat, uniform, and brand-clean. Do not add any background tint, wash, gradient, vignette, paper texture, studio falloff, atmospheric shading, or non-white field treatment.\n\nThis must look like a premium enterprise editorial explainer and consulting-grade teaching artifact, not a poster, not a fake dashboard, not a template box farm, and not a cinematic hero graphic.\n\nVisual system:\n- pure white background only\n- bold red headline in #EB1700 or black headline with selective #EB1700 emphasis\n- black body text\n- neutral gray structure and dividers\n- flat white cards with thin neutral-gray borders\n- stronger internal hierarchy inside the most important cards\n- slightly abstract explanatory diagrams\n- integrated note cards and editorial bands\n- medium density, not sparse\n- moderate panelization, not over-boxed\n- elevated editorial rhythm with varied card scale and visual pacing\n- medium-high contrast emphasis\n- medium-high connector emphasis only where it explains the story\n- selective red accents where they improve emphasis, rhythm, or conceptual contrast\n- moderate asymmetry and right-side emphasis when the newer, stronger, or more important idea belongs there\n- strong semantic coupling between nearby text and supporting visual elements\n- strict clean-footer behavior without visible reserve markers\n\nWhite-mode visual posture:\n- graphically impressive\n- structured expressive\n- boardroom-safe\n- meaning-first\n- visually memorable without chaos\n- less conservative than a plain consulting template\n- never decorative for its own sake\n\n    Narrative objective:\n    Introduce the family as a coherent stack, not a pile of documents.\n\n    Visual explanation to depict:\n    stack or systems map showing multiple layers working together to form governed capability\n\n    Layout requirements:\n    hero title with a clean stack relationship map\n\n    Composition rules:\n    - anchor the title close to the top edge with minimal empty space above it\n    - keep title and subtitle compactly stacked in a tight top title zone\n    - use one dominant explanatory architecture across the middle\n    - vary card sizes and visual weight based on conceptual importance\n    - use integrated note cards attached directly to the regions they explain\n    - use slightly abstract diagrams, hinge shapes, control bands, routing paths, or lifecycle flows only when they clarify the meaning\n    - avoid equal-weight box grids unless the story truly requires equality\n    - make the most important concept visually dominant\n    - preserve clean margins and a clean footer without showing any reserve-space marker\n    - use white space actively, but do not make the slide timid or visually empty\n\n    Visible text discipline:\nAll visible text in the image must be exactly and only the text listed in the Visible text section. Do not add any words. Do not invent labels. Do not paraphrase. Do not shorten. Do not duplicate. Do not render prompt instructions, technical markers, file names, source names, safe-zone notes, or scaffolding.\n\n    Visible text:\n    AI Capability Playbook\nOne problem space.\nMultiple layers of discipline.\nDoctrine, commitment, implementation, and evaluation work together.\n\n    Extra art direction:\n    Make it feel like a serious framework family, not a random document pile.\n\n    Avoid:\n    any non-white background, background tint, gradients in the white field, cinematic poster behavior, giant hero machinery, glossy UI, fake dashboards, stock people, robots, decorative data centers, random circuit boards, over-panelization, red everywhere, helper labels, prompt scaffolding, watermarks, and text gibberish.\n\n    Priority order:\n1. exact visible text fidelity\n2. thesis clarity and teaching story\n3. Mainline White or Dark Expressive family discipline\n4. semantic coupling between text and graphic structure\n5. premium enterprise credibility\n6. visual impressiveness without clutter",
      "dark_render_prompt": "Create a sharp 16:9 dark-mode editorial explainer slide.\n\n    Use Dark Expressive Editorial.\n\nThe background must be deep graphite, charcoal, or near-black with controlled gradients only when they help depth and focus. Use crisp white typography, restrained luminous #EB1700 accents, muted cool-gray structure, and high-contrast dark cards or panels.\n\nThis dark branch may be more cinematic and keynote-style than the white branch, but it must remain explanatory, premium, legible, and enterprise credible.\n\nDark-mode visual posture:\n- forceful but not chaotic\n- more atmospheric than white\n- stronger contrast between unstable and governed states\n- no neon overload\n- no glossy control-room UI\n- no cyberpunk wallpaper\n- no detached spectacle\n- no fake dashboards\n- no random energy ribbons without meaning\n- no product-board drift unless the slide is explicitly about product architecture\n\n    Narrative objective:\n    Introduce the family as a coherent stack, not a pile of documents.\n\n    Visual explanation to depict:\n    stack or systems map showing multiple layers working together to form governed capability\n\n    Layout requirements:\n    hero title with a clean stack relationship map\n\n    Composition rules:\n    - anchor the title close to the top edge with minimal dead space above it\n    - preserve the same teaching story as the white version\n    - create stronger contrast between unstable, naive, fragmented, or risky regions and governed, structured, reliable regions\n    - use a visually memorable central architecture, transformation path, control-plane flow, or lifecycle structure\n    - make the most important concept visually dominant\n    - allow more atmosphere, glow, depth, and motion than the white version only where it improves explanation\n    - keep text readable from a screen-share distance\n    - keep the slide premium and controlled, not chaotic\n\n    Visible text discipline:\nAll visible text in the image must be exactly and only the text listed in the Visible text section. Do not add any words. Do not invent labels. Do not paraphrase. Do not shorten. Do not duplicate. Do not render prompt instructions, technical markers, file names, source names, safe-zone notes, or scaffolding.\n\n    Visible text:\n    AI Capability Playbook\nOne problem space.\nMultiple layers of discipline.\nDoctrine, commitment, implementation, and evaluation work together.\n\n    Extra art direction:\n    Make it feel like a serious framework family, not a random document pile.\n\n    Avoid:\n    neon overload, sci-fi wallpaper, fake command-center UI, glossy dashboard panels, stock people, robots, random holograms, decorative circuitry, unreadable microtext, vendor logos, watermarks, prompt scaffolding, and visual chaos.\n\n    Priority order:\n1. exact visible text fidelity\n2. thesis clarity and teaching story\n3. Dark Expressive family discipline\n4. semantic coupling between text and graphic structure\n5. premium enterprise credibility\n6. visual impressiveness without clutter"
    },
    {
      "slide_id": "GCF-02",
      "title": "These are not competing frameworks. They are a stack.",
      "narrative_role": "family positioning",
      "objective": "End confusion about overlap and show complementarity.",
      "visible_text": [
        "These are not competing frameworks. They are a stack.",
        "Use each package at the right altitude.",
        "Shared primitives keep the family aligned."
      ],
      "white_render_prompt": "Create a sharp 16:9 editorial explainer slide.\n\n    Use Mainline White — Structured Expressive.\n\nThe background must be pure #FFFFFF white, flat, uniform, and brand-clean. Do not add any background tint, wash, gradient, vignette, paper texture, studio falloff, atmospheric shading, or non-white field treatment.\n\nThis must look like a premium enterprise editorial explainer and consulting-grade teaching artifact, not a poster, not a fake dashboard, not a template box farm, and not a cinematic hero graphic.\n\nVisual system:\n- pure white background only\n- bold red headline in #EB1700 or black headline with selective #EB1700 emphasis\n- black body text\n- neutral gray structure and dividers\n- flat white cards with thin neutral-gray borders\n- stronger internal hierarchy inside the most important cards\n- slightly abstract explanatory diagrams\n- integrated note cards and editorial bands\n- medium density, not sparse\n- moderate panelization, not over-boxed\n- elevated editorial rhythm with varied card scale and visual pacing\n- medium-high contrast emphasis\n- medium-high connector emphasis only where it explains the story\n- selective red accents where they improve emphasis, rhythm, or conceptual contrast\n- moderate asymmetry and right-side emphasis when the newer, stronger, or more important idea belongs there\n- strong semantic coupling between nearby text and supporting visual elements\n- strict clean-footer behavior without visible reserve markers\n\nWhite-mode visual posture:\n- graphically impressive\n- structured expressive\n- boardroom-safe\n- meaning-first\n- visually memorable without chaos\n- less conservative than a plain consulting template\n- never decorative for its own sake\n\n    Narrative objective:\n    End confusion about overlap and show complementarity.\n\n    Visual explanation to depict:\n    altitude map or layered stack showing complementarity and shared core primitives\n\n    Layout requirements:\n    clear family relationship diagram with altitude labels\n\n    Composition rules:\n    - anchor the title close to the top edge with minimal empty space above it\n    - keep title and subtitle compactly stacked in a tight top title zone\n    - use one dominant explanatory architecture across the middle\n    - vary card sizes and visual weight based on conceptual importance\n    - use integrated note cards attached directly to the regions they explain\n    - use slightly abstract diagrams, hinge shapes, control bands, routing paths, or lifecycle flows only when they clarify the meaning\n    - avoid equal-weight box grids unless the story truly requires equality\n    - make the most important concept visually dominant\n    - preserve clean margins and a clean footer without showing any reserve-space marker\n    - use white space actively, but do not make the slide timid or visually empty\n\n    Visible text discipline:\nAll visible text in the image must be exactly and only the text listed in the Visible text section. Do not add any words. Do not invent labels. Do not paraphrase. Do not shorten. Do not duplicate. Do not render prompt instructions, technical markers, file names, source names, safe-zone notes, or scaffolding.\n\n    Visible text:\n    These are not competing frameworks. They are a stack.\nUse each package at the right altitude.\nShared primitives keep the family aligned.\n\n    Extra art direction:\n    Use the visual to kill ambiguity.\n\n    Avoid:\n    any non-white background, background tint, gradients in the white field, cinematic poster behavior, giant hero machinery, glossy UI, fake dashboards, stock people, robots, decorative data centers, random circuit boards, over-panelization, red everywhere, helper labels, prompt scaffolding, watermarks, and text gibberish.\n\n    Priority order:\n1. exact visible text fidelity\n2. thesis clarity and teaching story\n3. Mainline White or Dark Expressive family discipline\n4. semantic coupling between text and graphic structure\n5. premium enterprise credibility\n6. visual impressiveness without clutter",
      "dark_render_prompt": "Create a sharp 16:9 dark-mode editorial explainer slide.\n\n    Use Dark Expressive Editorial.\n\nThe background must be deep graphite, charcoal, or near-black with controlled gradients only when they help depth and focus. Use crisp white typography, restrained luminous #EB1700 accents, muted cool-gray structure, and high-contrast dark cards or panels.\n\nThis dark branch may be more cinematic and keynote-style than the white branch, but it must remain explanatory, premium, legible, and enterprise credible.\n\nDark-mode visual posture:\n- forceful but not chaotic\n- more atmospheric than white\n- stronger contrast between unstable and governed states\n- no neon overload\n- no glossy control-room UI\n- no cyberpunk wallpaper\n- no detached spectacle\n- no fake dashboards\n- no random energy ribbons without meaning\n- no product-board drift unless the slide is explicitly about product architecture\n\n    Narrative objective:\n    End confusion about overlap and show complementarity.\n\n    Visual explanation to depict:\n    altitude map or layered stack showing complementarity and shared core primitives\n\n    Layout requirements:\n    clear family relationship diagram with altitude labels\n\n    Composition rules:\n    - anchor the title close to the top edge with minimal dead space above it\n    - preserve the same teaching story as the white version\n    - create stronger contrast between unstable, naive, fragmented, or risky regions and governed, structured, reliable regions\n    - use a visually memorable central architecture, transformation path, control-plane flow, or lifecycle structure\n    - make the most important concept visually dominant\n    - allow more atmosphere, glow, depth, and motion than the white version only where it improves explanation\n    - keep text readable from a screen-share distance\n    - keep the slide premium and controlled, not chaotic\n\n    Visible text discipline:\nAll visible text in the image must be exactly and only the text listed in the Visible text section. Do not add any words. Do not invent labels. Do not paraphrase. Do not shorten. Do not duplicate. Do not render prompt instructions, technical markers, file names, source names, safe-zone notes, or scaffolding.\n\n    Visible text:\n    These are not competing frameworks. They are a stack.\nUse each package at the right altitude.\nShared primitives keep the family aligned.\n\n    Extra art direction:\n    Use the visual to kill ambiguity.\n\n    Avoid:\n    neon overload, sci-fi wallpaper, fake command-center UI, glossy dashboard panels, stock people, robots, random holograms, decorative circuitry, unreadable microtext, vendor logos, watermarks, prompt scaffolding, and visual chaos.\n\n    Priority order:\n1. exact visible text fidelity\n2. thesis clarity and teaching story\n3. Dark Expressive family discipline\n4. semantic coupling between text and graphic structure\n5. premium enterprise credibility\n6. visual impressiveness without clutter"
    },
    {
      "slide_id": "GCF-03",
      "title": "Doctrine, commitment, implementation, and evaluation",
      "narrative_role": "stack anatomy",
      "objective": "Show the four main functional layers in simple terms.",
      "visible_text": [
        "Doctrine, commitment, implementation, and evaluation",
        "Doctrine teaches the discipline.",
        "Commitment governs scarce build capacity.",
        "Implementation proves the pattern in a real use case.",
        "Evaluation tests readiness and credibility."
      ],
      "white_render_prompt": "Create a sharp 16:9 editorial explainer slide.\n\n    Use Mainline White — Structured Expressive.\n\nThe background must be pure #FFFFFF white, flat, uniform, and brand-clean. Do not add any background tint, wash, gradient, vignette, paper texture, studio falloff, atmospheric shading, or non-white field treatment.\n\nThis must look like a premium enterprise editorial explainer and consulting-grade teaching artifact, not a poster, not a fake dashboard, not a template box farm, and not a cinematic hero graphic.\n\nVisual system:\n- pure white background only\n- bold red headline in #EB1700 or black headline with selective #EB1700 emphasis\n- black body text\n- neutral gray structure and dividers\n- flat white cards with thin neutral-gray borders\n- stronger internal hierarchy inside the most important cards\n- slightly abstract explanatory diagrams\n- integrated note cards and editorial bands\n- medium density, not sparse\n- moderate panelization, not over-boxed\n- elevated editorial rhythm with varied card scale and visual pacing\n- medium-high contrast emphasis\n- medium-high connector emphasis only where it explains the story\n- selective red accents where they improve emphasis, rhythm, or conceptual contrast\n- moderate asymmetry and right-side emphasis when the newer, stronger, or more important idea belongs there\n- strong semantic coupling between nearby text and supporting visual elements\n- strict clean-footer behavior without visible reserve markers\n\nWhite-mode visual posture:\n- graphically impressive\n- structured expressive\n- boardroom-safe\n- meaning-first\n- visually memorable without chaos\n- less conservative than a plain consulting template\n- never decorative for its own sake\n\n    Narrative objective:\n    Show the four main functional layers in simple terms.\n\n    Visual explanation to depict:\n    four-layer stack with concise explanation for each layer\n\n    Layout requirements:\n    clean four-tier explainer\n\n    Composition rules:\n    - anchor the title close to the top edge with minimal empty space above it\n    - keep title and subtitle compactly stacked in a tight top title zone\n    - use one dominant explanatory architecture across the middle\n    - vary card sizes and visual weight based on conceptual importance\n    - use integrated note cards attached directly to the regions they explain\n    - use slightly abstract diagrams, hinge shapes, control bands, routing paths, or lifecycle flows only when they clarify the meaning\n    - avoid equal-weight box grids unless the story truly requires equality\n    - make the most important concept visually dominant\n    - preserve clean margins and a clean footer without showing any reserve-space marker\n    - use white space actively, but do not make the slide timid or visually empty\n\n    Visible text discipline:\nAll visible text in the image must be exactly and only the text listed in the Visible text section. Do not add any words. Do not invent labels. Do not paraphrase. Do not shorten. Do not duplicate. Do not render prompt instructions, technical markers, file names, source names, safe-zone notes, or scaffolding.\n\n    Visible text:\n    Doctrine, commitment, implementation, and evaluation\nDoctrine teaches the discipline.\nCommitment governs scarce build capacity.\nImplementation proves the pattern in a real use case.\nEvaluation tests readiness and credibility.\n\n    Extra art direction:\n    Simple and memorable.\n\n    Avoid:\n    any non-white background, background tint, gradients in the white field, cinematic poster behavior, giant hero machinery, glossy UI, fake dashboards, stock people, robots, decorative data centers, random circuit boards, over-panelization, red everywhere, helper labels, prompt scaffolding, watermarks, and text gibberish.\n\n    Priority order:\n1. exact visible text fidelity\n2. thesis clarity and teaching story\n3. Mainline White or Dark Expressive family discipline\n4. semantic coupling between text and graphic structure\n5. premium enterprise credibility\n6. visual impressiveness without clutter",
      "dark_render_prompt": "Create a sharp 16:9 dark-mode editorial explainer slide.\n\n    Use Dark Expressive Editorial.\n\nThe background must be deep graphite, charcoal, or near-black with controlled gradients only when they help depth and focus. Use crisp white typography, restrained luminous #EB1700 accents, muted cool-gray structure, and high-contrast dark cards or panels.\n\nThis dark branch may be more cinematic and keynote-style than the white branch, but it must remain explanatory, premium, legible, and enterprise credible.\n\nDark-mode visual posture:\n- forceful but not chaotic\n- more atmospheric than white\n- stronger contrast between unstable and governed states\n- no neon overload\n- no glossy control-room UI\n- no cyberpunk wallpaper\n- no detached spectacle\n- no fake dashboards\n- no random energy ribbons without meaning\n- no product-board drift unless the slide is explicitly about product architecture\n\n    Narrative objective:\n    Show the four main functional layers in simple terms.\n\n    Visual explanation to depict:\n    four-layer stack with concise explanation for each layer\n\n    Layout requirements:\n    clean four-tier explainer\n\n    Composition rules:\n    - anchor the title close to the top edge with minimal dead space above it\n    - preserve the same teaching story as the white version\n    - create stronger contrast between unstable, naive, fragmented, or risky regions and governed, structured, reliable regions\n    - use a visually memorable central architecture, transformation path, control-plane flow, or lifecycle structure\n    - make the most important concept visually dominant\n    - allow more atmosphere, glow, depth, and motion than the white version only where it improves explanation\n    - keep text readable from a screen-share distance\n    - keep the slide premium and controlled, not chaotic\n\n    Visible text discipline:\nAll visible text in the image must be exactly and only the text listed in the Visible text section. Do not add any words. Do not invent labels. Do not paraphrase. Do not shorten. Do not duplicate. Do not render prompt instructions, technical markers, file names, source names, safe-zone notes, or scaffolding.\n\n    Visible text:\n    Doctrine, commitment, implementation, and evaluation\nDoctrine teaches the discipline.\nCommitment governs scarce build capacity.\nImplementation proves the pattern in a real use case.\nEvaluation tests readiness and credibility.\n\n    Extra art direction:\n    Simple and memorable.\n\n    Avoid:\n    neon overload, sci-fi wallpaper, fake command-center UI, glossy dashboard panels, stock people, robots, random holograms, decorative circuitry, unreadable microtext, vendor logos, watermarks, prompt scaffolding, and visual chaos.\n\n    Priority order:\n1. exact visible text fidelity\n2. thesis clarity and teaching story\n3. Dark Expressive family discipline\n4. semantic coupling between text and graphic structure\n5. premium enterprise credibility\n6. visual impressiveness without clutter"
    },
    {
      "slide_id": "GCF-04",
      "title": "AI Capability Discipline is the doctrine layer.",
      "narrative_role": "package positioning",
      "objective": "Position AICD clearly inside the family.",
      "visible_text": [
        "AI Capability Discipline is the doctrine layer.",
        "It resets the mental model.",
        "It teaches capability formation, routing, source authority, eval validity, and maintenance."
      ],
      "white_render_prompt": "Create a sharp 16:9 editorial explainer slide.\n\n    Use Mainline White — Structured Expressive.\n\nThe background must be pure #FFFFFF white, flat, uniform, and brand-clean. Do not add any background tint, wash, gradient, vignette, paper texture, studio falloff, atmospheric shading, or non-white field treatment.\n\nThis must look like a premium enterprise editorial explainer and consulting-grade teaching artifact, not a poster, not a fake dashboard, not a template box farm, and not a cinematic hero graphic.\n\nVisual system:\n- pure white background only\n- bold red headline in #EB1700 or black headline with selective #EB1700 emphasis\n- black body text\n- neutral gray structure and dividers\n- flat white cards with thin neutral-gray borders\n- stronger internal hierarchy inside the most important cards\n- slightly abstract explanatory diagrams\n- integrated note cards and editorial bands\n- medium density, not sparse\n- moderate panelization, not over-boxed\n- elevated editorial rhythm with varied card scale and visual pacing\n- medium-high contrast emphasis\n- medium-high connector emphasis only where it explains the story\n- selective red accents where they improve emphasis, rhythm, or conceptual contrast\n- moderate asymmetry and right-side emphasis when the newer, stronger, or more important idea belongs there\n- strong semantic coupling between nearby text and supporting visual elements\n- strict clean-footer behavior without visible reserve markers\n\nWhite-mode visual posture:\n- graphically impressive\n- structured expressive\n- boardroom-safe\n- meaning-first\n- visually memorable without chaos\n- less conservative than a plain consulting template\n- never decorative for its own sake\n\n    Narrative objective:\n    Position AICD clearly inside the family.\n\n    Visual explanation to depict:\n    AICD highlighted as the doctrine layer feeding the rest of the family\n\n    Layout requirements:\n    single-layer spotlight within the broader family map\n\n    Composition rules:\n    - anchor the title close to the top edge with minimal empty space above it\n    - keep title and subtitle compactly stacked in a tight top title zone\n    - use one dominant explanatory architecture across the middle\n    - vary card sizes and visual weight based on conceptual importance\n    - use integrated note cards attached directly to the regions they explain\n    - use slightly abstract diagrams, hinge shapes, control bands, routing paths, or lifecycle flows only when they clarify the meaning\n    - avoid equal-weight box grids unless the story truly requires equality\n    - make the most important concept visually dominant\n    - preserve clean margins and a clean footer without showing any reserve-space marker\n    - use white space actively, but do not make the slide timid or visually empty\n\n    Visible text discipline:\nAll visible text in the image must be exactly and only the text listed in the Visible text section. Do not add any words. Do not invent labels. Do not paraphrase. Do not shorten. Do not duplicate. Do not render prompt instructions, technical markers, file names, source names, safe-zone notes, or scaffolding.\n\n    Visible text:\n    AI Capability Discipline is the doctrine layer.\nIt resets the mental model.\nIt teaches capability formation, routing, source authority, eval validity, and maintenance.\n\n    Extra art direction:\n    Make it foundational.\n\n    Avoid:\n    any non-white background, background tint, gradients in the white field, cinematic poster behavior, giant hero machinery, glossy UI, fake dashboards, stock people, robots, decorative data centers, random circuit boards, over-panelization, red everywhere, helper labels, prompt scaffolding, watermarks, and text gibberish.\n\n    Priority order:\n1. exact visible text fidelity\n2. thesis clarity and teaching story\n3. Mainline White or Dark Expressive family discipline\n4. semantic coupling between text and graphic structure\n5. premium enterprise credibility\n6. visual impressiveness without clutter",
      "dark_render_prompt": "Create a sharp 16:9 dark-mode editorial explainer slide.\n\n    Use Dark Expressive Editorial.\n\nThe background must be deep graphite, charcoal, or near-black with controlled gradients only when they help depth and focus. Use crisp white typography, restrained luminous #EB1700 accents, muted cool-gray structure, and high-contrast dark cards or panels.\n\nThis dark branch may be more cinematic and keynote-style than the white branch, but it must remain explanatory, premium, legible, and enterprise credible.\n\nDark-mode visual posture:\n- forceful but not chaotic\n- more atmospheric than white\n- stronger contrast between unstable and governed states\n- no neon overload\n- no glossy control-room UI\n- no cyberpunk wallpaper\n- no detached spectacle\n- no fake dashboards\n- no random energy ribbons without meaning\n- no product-board drift unless the slide is explicitly about product architecture\n\n    Narrative objective:\n    Position AICD clearly inside the family.\n\n    Visual explanation to depict:\n    AICD highlighted as the doctrine layer feeding the rest of the family\n\n    Layout requirements:\n    single-layer spotlight within the broader family map\n\n    Composition rules:\n    - anchor the title close to the top edge with minimal dead space above it\n    - preserve the same teaching story as the white version\n    - create stronger contrast between unstable, naive, fragmented, or risky regions and governed, structured, reliable regions\n    - use a visually memorable central architecture, transformation path, control-plane flow, or lifecycle structure\n    - make the most important concept visually dominant\n    - allow more atmosphere, glow, depth, and motion than the white version only where it improves explanation\n    - keep text readable from a screen-share distance\n    - keep the slide premium and controlled, not chaotic\n\n    Visible text discipline:\nAll visible text in the image must be exactly and only the text listed in the Visible text section. Do not add any words. Do not invent labels. Do not paraphrase. Do not shorten. Do not duplicate. Do not render prompt instructions, technical markers, file names, source names, safe-zone notes, or scaffolding.\n\n    Visible text:\n    AI Capability Discipline is the doctrine layer.\nIt resets the mental model.\nIt teaches capability formation, routing, source authority, eval validity, and maintenance.\n\n    Extra art direction:\n    Make it foundational.\n\n    Avoid:\n    neon overload, sci-fi wallpaper, fake command-center UI, glossy dashboard panels, stock people, robots, random holograms, decorative circuitry, unreadable microtext, vendor logos, watermarks, prompt scaffolding, and visual chaos.\n\n    Priority order:\n1. exact visible text fidelity\n2. thesis clarity and teaching story\n3. Dark Expressive family discipline\n4. semantic coupling between text and graphic structure\n5. premium enterprise credibility\n6. visual impressiveness without clutter"
    },
    {
      "slide_id": "GCF-05",
      "title": "WESS Development Commitment governs build-readiness and commitment.",
      "narrative_role": "package positioning",
      "objective": "Position WESS as the team operating model.",
      "visible_text": [
        "WESS Development Commitment governs build-readiness and commitment.",
        "It protects scarce engineering capacity.",
        "It routes work from sandbox to operational capability."
      ],
      "white_render_prompt": "Create a sharp 16:9 editorial explainer slide.\n\n    Use Mainline White — Structured Expressive.\n\nThe background must be pure #FFFFFF white, flat, uniform, and brand-clean. Do not add any background tint, wash, gradient, vignette, paper texture, studio falloff, atmospheric shading, or non-white field treatment.\n\nThis must look like a premium enterprise editorial explainer and consulting-grade teaching artifact, not a poster, not a fake dashboard, not a template box farm, and not a cinematic hero graphic.\n\nVisual system:\n- pure white background only\n- bold red headline in #EB1700 or black headline with selective #EB1700 emphasis\n- black body text\n- neutral gray structure and dividers\n- flat white cards with thin neutral-gray borders\n- stronger internal hierarchy inside the most important cards\n- slightly abstract explanatory diagrams\n- integrated note cards and editorial bands\n- medium density, not sparse\n- moderate panelization, not over-boxed\n- elevated editorial rhythm with varied card scale and visual pacing\n- medium-high contrast emphasis\n- medium-high connector emphasis only where it explains the story\n- selective red accents where they improve emphasis, rhythm, or conceptual contrast\n- moderate asymmetry and right-side emphasis when the newer, stronger, or more important idea belongs there\n- strong semantic coupling between nearby text and supporting visual elements\n- strict clean-footer behavior without visible reserve markers\n\nWhite-mode visual posture:\n- graphically impressive\n- structured expressive\n- boardroom-safe\n- meaning-first\n- visually memorable without chaos\n- less conservative than a plain consulting template\n- never decorative for its own sake\n\n    Narrative objective:\n    Position WESS as the team operating model.\n\n    Visual explanation to depict:\n    WESS lane model highlighted as the commitment and operating layer\n\n    Layout requirements:\n    package spotlight tied to the lane model\n\n    Composition rules:\n    - anchor the title close to the top edge with minimal empty space above it\n    - keep title and subtitle compactly stacked in a tight top title zone\n    - use one dominant explanatory architecture across the middle\n    - vary card sizes and visual weight based on conceptual importance\n    - use integrated note cards attached directly to the regions they explain\n    - use slightly abstract diagrams, hinge shapes, control bands, routing paths, or lifecycle flows only when they clarify the meaning\n    - avoid equal-weight box grids unless the story truly requires equality\n    - make the most important concept visually dominant\n    - preserve clean margins and a clean footer without showing any reserve-space marker\n    - use white space actively, but do not make the slide timid or visually empty\n\n    Visible text discipline:\nAll visible text in the image must be exactly and only the text listed in the Visible text section. Do not add any words. Do not invent labels. Do not paraphrase. Do not shorten. Do not duplicate. Do not render prompt instructions, technical markers, file names, source names, safe-zone notes, or scaffolding.\n\n    Visible text:\n    WESS Development Commitment governs build-readiness and commitment.\nIt protects scarce engineering capacity.\nIt routes work from sandbox to operational capability.\n\n    Extra art direction:\n    Operational and practical.\n\n    Avoid:\n    any non-white background, background tint, gradients in the white field, cinematic poster behavior, giant hero machinery, glossy UI, fake dashboards, stock people, robots, decorative data centers, random circuit boards, over-panelization, red everywhere, helper labels, prompt scaffolding, watermarks, and text gibberish.\n\n    Priority order:\n1. exact visible text fidelity\n2. thesis clarity and teaching story\n3. Mainline White or Dark Expressive family discipline\n4. semantic coupling between text and graphic structure\n5. premium enterprise credibility\n6. visual impressiveness without clutter",
      "dark_render_prompt": "Create a sharp 16:9 dark-mode editorial explainer slide.\n\n    Use Dark Expressive Editorial.\n\nThe background must be deep graphite, charcoal, or near-black with controlled gradients only when they help depth and focus. Use crisp white typography, restrained luminous #EB1700 accents, muted cool-gray structure, and high-contrast dark cards or panels.\n\nThis dark branch may be more cinematic and keynote-style than the white branch, but it must remain explanatory, premium, legible, and enterprise credible.\n\nDark-mode visual posture:\n- forceful but not chaotic\n- more atmospheric than white\n- stronger contrast between unstable and governed states\n- no neon overload\n- no glossy control-room UI\n- no cyberpunk wallpaper\n- no detached spectacle\n- no fake dashboards\n- no random energy ribbons without meaning\n- no product-board drift unless the slide is explicitly about product architecture\n\n    Narrative objective:\n    Position WESS as the team operating model.\n\n    Visual explanation to depict:\n    WESS lane model highlighted as the commitment and operating layer\n\n    Layout requirements:\n    package spotlight tied to the lane model\n\n    Composition rules:\n    - anchor the title close to the top edge with minimal dead space above it\n    - preserve the same teaching story as the white version\n    - create stronger contrast between unstable, naive, fragmented, or risky regions and governed, structured, reliable regions\n    - use a visually memorable central architecture, transformation path, control-plane flow, or lifecycle structure\n    - make the most important concept visually dominant\n    - allow more atmosphere, glow, depth, and motion than the white version only where it improves explanation\n    - keep text readable from a screen-share distance\n    - keep the slide premium and controlled, not chaotic\n\n    Visible text discipline:\nAll visible text in the image must be exactly and only the text listed in the Visible text section. Do not add any words. Do not invent labels. Do not paraphrase. Do not shorten. Do not duplicate. Do not render prompt instructions, technical markers, file names, source names, safe-zone notes, or scaffolding.\n\n    Visible text:\n    WESS Development Commitment governs build-readiness and commitment.\nIt protects scarce engineering capacity.\nIt routes work from sandbox to operational capability.\n\n    Extra art direction:\n    Operational and practical.\n\n    Avoid:\n    neon overload, sci-fi wallpaper, fake command-center UI, glossy dashboard panels, stock people, robots, random holograms, decorative circuitry, unreadable microtext, vendor logos, watermarks, prompt scaffolding, and visual chaos.\n\n    Priority order:\n1. exact visible text fidelity\n2. thesis clarity and teaching story\n3. Dark Expressive family discipline\n4. semantic coupling between text and graphic structure\n5. premium enterprise credibility\n6. visual impressiveness without clutter"
    },
    {
      "slide_id": "GCF-06",
      "title": "Enterprise Architecture Review Assistant is the applied reference implementation.",
      "narrative_role": "package positioning",
      "objective": "Position EA as the concrete instantiation of the doctrine.",
      "visible_text": [
        "Enterprise Architecture Review Assistant is the applied reference implementation.",
        "It shows how the discipline becomes a governed assistant architecture.",
        "It turns theory into an applied build candidate."
      ],
      "white_render_prompt": "Create a sharp 16:9 editorial explainer slide.\n\n    Use Mainline White — Structured Expressive.\n\nThe background must be pure #FFFFFF white, flat, uniform, and brand-clean. Do not add any background tint, wash, gradient, vignette, paper texture, studio falloff, atmospheric shading, or non-white field treatment.\n\nThis must look like a premium enterprise editorial explainer and consulting-grade teaching artifact, not a poster, not a fake dashboard, not a template box farm, and not a cinematic hero graphic.\n\nVisual system:\n- pure white background only\n- bold red headline in #EB1700 or black headline with selective #EB1700 emphasis\n- black body text\n- neutral gray structure and dividers\n- flat white cards with thin neutral-gray borders\n- stronger internal hierarchy inside the most important cards\n- slightly abstract explanatory diagrams\n- integrated note cards and editorial bands\n- medium density, not sparse\n- moderate panelization, not over-boxed\n- elevated editorial rhythm with varied card scale and visual pacing\n- medium-high contrast emphasis\n- medium-high connector emphasis only where it explains the story\n- selective red accents where they improve emphasis, rhythm, or conceptual contrast\n- moderate asymmetry and right-side emphasis when the newer, stronger, or more important idea belongs there\n- strong semantic coupling between nearby text and supporting visual elements\n- strict clean-footer behavior without visible reserve markers\n\nWhite-mode visual posture:\n- graphically impressive\n- structured expressive\n- boardroom-safe\n- meaning-first\n- visually memorable without chaos\n- less conservative than a plain consulting template\n- never decorative for its own sake\n\n    Narrative objective:\n    Position EA as the concrete instantiation of the doctrine.\n\n    Visual explanation to depict:\n    EA package shown as a real applied capability instantiated from the doctrine and core primitives\n\n    Layout requirements:\n    package spotlight with input/output flow from doctrine to implementation\n\n    Composition rules:\n    - anchor the title close to the top edge with minimal empty space above it\n    - keep title and subtitle compactly stacked in a tight top title zone\n    - use one dominant explanatory architecture across the middle\n    - vary card sizes and visual weight based on conceptual importance\n    - use integrated note cards attached directly to the regions they explain\n    - use slightly abstract diagrams, hinge shapes, control bands, routing paths, or lifecycle flows only when they clarify the meaning\n    - avoid equal-weight box grids unless the story truly requires equality\n    - make the most important concept visually dominant\n    - preserve clean margins and a clean footer without showing any reserve-space marker\n    - use white space actively, but do not make the slide timid or visually empty\n\n    Visible text discipline:\nAll visible text in the image must be exactly and only the text listed in the Visible text section. Do not add any words. Do not invent labels. Do not paraphrase. Do not shorten. Do not duplicate. Do not render prompt instructions, technical markers, file names, source names, safe-zone notes, or scaffolding.\n\n    Visible text:\n    Enterprise Architecture Review Assistant is the applied reference implementation.\nIt shows how the discipline becomes a governed assistant architecture.\nIt turns theory into an applied build candidate.\n\n    Extra art direction:\n    Concrete and credible.\n\n    Avoid:\n    any non-white background, background tint, gradients in the white field, cinematic poster behavior, giant hero machinery, glossy UI, fake dashboards, stock people, robots, decorative data centers, random circuit boards, over-panelization, red everywhere, helper labels, prompt scaffolding, watermarks, and text gibberish.\n\n    Priority order:\n1. exact visible text fidelity\n2. thesis clarity and teaching story\n3. Mainline White or Dark Expressive family discipline\n4. semantic coupling between text and graphic structure\n5. premium enterprise credibility\n6. visual impressiveness without clutter",
      "dark_render_prompt": "Create a sharp 16:9 dark-mode editorial explainer slide.\n\n    Use Dark Expressive Editorial.\n\nThe background must be deep graphite, charcoal, or near-black with controlled gradients only when they help depth and focus. Use crisp white typography, restrained luminous #EB1700 accents, muted cool-gray structure, and high-contrast dark cards or panels.\n\nThis dark branch may be more cinematic and keynote-style than the white branch, but it must remain explanatory, premium, legible, and enterprise credible.\n\nDark-mode visual posture:\n- forceful but not chaotic\n- more atmospheric than white\n- stronger contrast between unstable and governed states\n- no neon overload\n- no glossy control-room UI\n- no cyberpunk wallpaper\n- no detached spectacle\n- no fake dashboards\n- no random energy ribbons without meaning\n- no product-board drift unless the slide is explicitly about product architecture\n\n    Narrative objective:\n    Position EA as the concrete instantiation of the doctrine.\n\n    Visual explanation to depict:\n    EA package shown as a real applied capability instantiated from the doctrine and core primitives\n\n    Layout requirements:\n    package spotlight with input/output flow from doctrine to implementation\n\n    Composition rules:\n    - anchor the title close to the top edge with minimal dead space above it\n    - preserve the same teaching story as the white version\n    - create stronger contrast between unstable, naive, fragmented, or risky regions and governed, structured, reliable regions\n    - use a visually memorable central architecture, transformation path, control-plane flow, or lifecycle structure\n    - make the most important concept visually dominant\n    - allow more atmosphere, glow, depth, and motion than the white version only where it improves explanation\n    - keep text readable from a screen-share distance\n    - keep the slide premium and controlled, not chaotic\n\n    Visible text discipline:\nAll visible text in the image must be exactly and only the text listed in the Visible text section. Do not add any words. Do not invent labels. Do not paraphrase. Do not shorten. Do not duplicate. Do not render prompt instructions, technical markers, file names, source names, safe-zone notes, or scaffolding.\n\n    Visible text:\n    Enterprise Architecture Review Assistant is the applied reference implementation.\nIt shows how the discipline becomes a governed assistant architecture.\nIt turns theory into an applied build candidate.\n\n    Extra art direction:\n    Concrete and credible.\n\n    Avoid:\n    neon overload, sci-fi wallpaper, fake command-center UI, glossy dashboard panels, stock people, robots, random holograms, decorative circuitry, unreadable microtext, vendor logos, watermarks, prompt scaffolding, and visual chaos.\n\n    Priority order:\n1. exact visible text fidelity\n2. thesis clarity and teaching story\n3. Dark Expressive family discipline\n4. semantic coupling between text and graphic structure\n5. premium enterprise credibility\n6. visual impressiveness without clutter"
    },
    {
      "slide_id": "GCF-07",
      "title": "Shared primitives keep the family coherent.",
      "narrative_role": "coherence model",
      "objective": "Show the common primitives that unify the family.",
      "visible_text": [
        "Shared primitives keep the family coherent.",
        "Source authority",
        "Evidence states",
        "Routing",
        "Human review",
        "Lifecycle maintenance"
      ],
      "white_render_prompt": "Create a sharp 16:9 editorial explainer slide.\n\n    Use Mainline White — Structured Expressive.\n\nThe background must be pure #FFFFFF white, flat, uniform, and brand-clean. Do not add any background tint, wash, gradient, vignette, paper texture, studio falloff, atmospheric shading, or non-white field treatment.\n\nThis must look like a premium enterprise editorial explainer and consulting-grade teaching artifact, not a poster, not a fake dashboard, not a template box farm, and not a cinematic hero graphic.\n\nVisual system:\n- pure white background only\n- bold red headline in #EB1700 or black headline with selective #EB1700 emphasis\n- black body text\n- neutral gray structure and dividers\n- flat white cards with thin neutral-gray borders\n- stronger internal hierarchy inside the most important cards\n- slightly abstract explanatory diagrams\n- integrated note cards and editorial bands\n- medium density, not sparse\n- moderate panelization, not over-boxed\n- elevated editorial rhythm with varied card scale and visual pacing\n- medium-high contrast emphasis\n- medium-high connector emphasis only where it explains the story\n- selective red accents where they improve emphasis, rhythm, or conceptual contrast\n- moderate asymmetry and right-side emphasis when the newer, stronger, or more important idea belongs there\n- strong semantic coupling between nearby text and supporting visual elements\n- strict clean-footer behavior without visible reserve markers\n\nWhite-mode visual posture:\n- graphically impressive\n- structured expressive\n- boardroom-safe\n- meaning-first\n- visually memorable without chaos\n- less conservative than a plain consulting template\n- never decorative for its own sake\n\n    Narrative objective:\n    Show the common primitives that unify the family.\n\n    Visual explanation to depict:\n    shared primitives hub feeding multiple family packages\n\n    Layout requirements:\n    hub-and-spoke or common-core diagram\n\n    Composition rules:\n    - anchor the title close to the top edge with minimal empty space above it\n    - keep title and subtitle compactly stacked in a tight top title zone\n    - use one dominant explanatory architecture across the middle\n    - vary card sizes and visual weight based on conceptual importance\n    - use integrated note cards attached directly to the regions they explain\n    - use slightly abstract diagrams, hinge shapes, control bands, routing paths, or lifecycle flows only when they clarify the meaning\n    - avoid equal-weight box grids unless the story truly requires equality\n    - make the most important concept visually dominant\n    - preserve clean margins and a clean footer without showing any reserve-space marker\n    - use white space actively, but do not make the slide timid or visually empty\n\n    Visible text discipline:\nAll visible text in the image must be exactly and only the text listed in the Visible text section. Do not add any words. Do not invent labels. Do not paraphrase. Do not shorten. Do not duplicate. Do not render prompt instructions, technical markers, file names, source names, safe-zone notes, or scaffolding.\n\n    Visible text:\n    Shared primitives keep the family coherent.\nSource authority\nEvidence states\nRouting\nHuman review\nLifecycle maintenance\n\n    Extra art direction:\n    Make the primitives feel reusable and canonical.\n\n    Avoid:\n    any non-white background, background tint, gradients in the white field, cinematic poster behavior, giant hero machinery, glossy UI, fake dashboards, stock people, robots, decorative data centers, random circuit boards, over-panelization, red everywhere, helper labels, prompt scaffolding, watermarks, and text gibberish.\n\n    Priority order:\n1. exact visible text fidelity\n2. thesis clarity and teaching story\n3. Mainline White or Dark Expressive family discipline\n4. semantic coupling between text and graphic structure\n5. premium enterprise credibility\n6. visual impressiveness without clutter",
      "dark_render_prompt": "Create a sharp 16:9 dark-mode editorial explainer slide.\n\n    Use Dark Expressive Editorial.\n\nThe background must be deep graphite, charcoal, or near-black with controlled gradients only when they help depth and focus. Use crisp white typography, restrained luminous #EB1700 accents, muted cool-gray structure, and high-contrast dark cards or panels.\n\nThis dark branch may be more cinematic and keynote-style than the white branch, but it must remain explanatory, premium, legible, and enterprise credible.\n\nDark-mode visual posture:\n- forceful but not chaotic\n- more atmospheric than white\n- stronger contrast between unstable and governed states\n- no neon overload\n- no glossy control-room UI\n- no cyberpunk wallpaper\n- no detached spectacle\n- no fake dashboards\n- no random energy ribbons without meaning\n- no product-board drift unless the slide is explicitly about product architecture\n\n    Narrative objective:\n    Show the common primitives that unify the family.\n\n    Visual explanation to depict:\n    shared primitives hub feeding multiple family packages\n\n    Layout requirements:\n    hub-and-spoke or common-core diagram\n\n    Composition rules:\n    - anchor the title close to the top edge with minimal dead space above it\n    - preserve the same teaching story as the white version\n    - create stronger contrast between unstable, naive, fragmented, or risky regions and governed, structured, reliable regions\n    - use a visually memorable central architecture, transformation path, control-plane flow, or lifecycle structure\n    - make the most important concept visually dominant\n    - allow more atmosphere, glow, depth, and motion than the white version only where it improves explanation\n    - keep text readable from a screen-share distance\n    - keep the slide premium and controlled, not chaotic\n\n    Visible text discipline:\nAll visible text in the image must be exactly and only the text listed in the Visible text section. Do not add any words. Do not invent labels. Do not paraphrase. Do not shorten. Do not duplicate. Do not render prompt instructions, technical markers, file names, source names, safe-zone notes, or scaffolding.\n\n    Visible text:\n    Shared primitives keep the family coherent.\nSource authority\nEvidence states\nRouting\nHuman review\nLifecycle maintenance\n\n    Extra art direction:\n    Make the primitives feel reusable and canonical.\n\n    Avoid:\n    neon overload, sci-fi wallpaper, fake command-center UI, glossy dashboard panels, stock people, robots, random holograms, decorative circuitry, unreadable microtext, vendor logos, watermarks, prompt scaffolding, and visual chaos.\n\n    Priority order:\n1. exact visible text fidelity\n2. thesis clarity and teaching story\n3. Dark Expressive family discipline\n4. semantic coupling between text and graphic structure\n5. premium enterprise credibility\n6. visual impressiveness without clutter"
    },
    {
      "slide_id": "GCF-08",
      "title": "Route work by risk, commitment depth, and control needs.",
      "narrative_role": "decision use map",
      "objective": "Show how to decide which package or lane to use.",
      "visible_text": [
        "Route work by risk, commitment depth, and control needs.",
        "Low-risk exploration",
        "Team build commitment",
        "Applied capability design",
        "Evaluation and validation"
      ],
      "white_render_prompt": "Create a sharp 16:9 editorial explainer slide.\n\n    Use Mainline White — Structured Expressive.\n\nThe background must be pure #FFFFFF white, flat, uniform, and brand-clean. Do not add any background tint, wash, gradient, vignette, paper texture, studio falloff, atmospheric shading, or non-white field treatment.\n\nThis must look like a premium enterprise editorial explainer and consulting-grade teaching artifact, not a poster, not a fake dashboard, not a template box farm, and not a cinematic hero graphic.\n\nVisual system:\n- pure white background only\n- bold red headline in #EB1700 or black headline with selective #EB1700 emphasis\n- black body text\n- neutral gray structure and dividers\n- flat white cards with thin neutral-gray borders\n- stronger internal hierarchy inside the most important cards\n- slightly abstract explanatory diagrams\n- integrated note cards and editorial bands\n- medium density, not sparse\n- moderate panelization, not over-boxed\n- elevated editorial rhythm with varied card scale and visual pacing\n- medium-high contrast emphasis\n- medium-high connector emphasis only where it explains the story\n- selective red accents where they improve emphasis, rhythm, or conceptual contrast\n- moderate asymmetry and right-side emphasis when the newer, stronger, or more important idea belongs there\n- strong semantic coupling between nearby text and supporting visual elements\n- strict clean-footer behavior without visible reserve markers\n\nWhite-mode visual posture:\n- graphically impressive\n- structured expressive\n- boardroom-safe\n- meaning-first\n- visually memorable without chaos\n- less conservative than a plain consulting template\n- never decorative for its own sake\n\n    Narrative objective:\n    Show how to decide which package or lane to use.\n\n    Visual explanation to depict:\n    decision routing map that points different work types to the right package or lane\n\n    Layout requirements:\n    routing matrix or decision tree\n\n    Composition rules:\n    - anchor the title close to the top edge with minimal empty space above it\n    - keep title and subtitle compactly stacked in a tight top title zone\n    - use one dominant explanatory architecture across the middle\n    - vary card sizes and visual weight based on conceptual importance\n    - use integrated note cards attached directly to the regions they explain\n    - use slightly abstract diagrams, hinge shapes, control bands, routing paths, or lifecycle flows only when they clarify the meaning\n    - avoid equal-weight box grids unless the story truly requires equality\n    - make the most important concept visually dominant\n    - preserve clean margins and a clean footer without showing any reserve-space marker\n    - use white space actively, but do not make the slide timid or visually empty\n\n    Visible text discipline:\nAll visible text in the image must be exactly and only the text listed in the Visible text section. Do not add any words. Do not invent labels. Do not paraphrase. Do not shorten. Do not duplicate. Do not render prompt instructions, technical markers, file names, source names, safe-zone notes, or scaffolding.\n\n    Visible text:\n    Route work by risk, commitment depth, and control needs.\nLow-risk exploration\nTeam build commitment\nApplied capability design\nEvaluation and validation\n\n    Extra art direction:\n    Very clear and actionable.\n\n    Avoid:\n    any non-white background, background tint, gradients in the white field, cinematic poster behavior, giant hero machinery, glossy UI, fake dashboards, stock people, robots, decorative data centers, random circuit boards, over-panelization, red everywhere, helper labels, prompt scaffolding, watermarks, and text gibberish.\n\n    Priority order:\n1. exact visible text fidelity\n2. thesis clarity and teaching story\n3. Mainline White or Dark Expressive family discipline\n4. semantic coupling between text and graphic structure\n5. premium enterprise credibility\n6. visual impressiveness without clutter",
      "dark_render_prompt": "Create a sharp 16:9 dark-mode editorial explainer slide.\n\n    Use Dark Expressive Editorial.\n\nThe background must be deep graphite, charcoal, or near-black with controlled gradients only when they help depth and focus. Use crisp white typography, restrained luminous #EB1700 accents, muted cool-gray structure, and high-contrast dark cards or panels.\n\nThis dark branch may be more cinematic and keynote-style than the white branch, but it must remain explanatory, premium, legible, and enterprise credible.\n\nDark-mode visual posture:\n- forceful but not chaotic\n- more atmospheric than white\n- stronger contrast between unstable and governed states\n- no neon overload\n- no glossy control-room UI\n- no cyberpunk wallpaper\n- no detached spectacle\n- no fake dashboards\n- no random energy ribbons without meaning\n- no product-board drift unless the slide is explicitly about product architecture\n\n    Narrative objective:\n    Show how to decide which package or lane to use.\n\n    Visual explanation to depict:\n    decision routing map that points different work types to the right package or lane\n\n    Layout requirements:\n    routing matrix or decision tree\n\n    Composition rules:\n    - anchor the title close to the top edge with minimal dead space above it\n    - preserve the same teaching story as the white version\n    - create stronger contrast between unstable, naive, fragmented, or risky regions and governed, structured, reliable regions\n    - use a visually memorable central architecture, transformation path, control-plane flow, or lifecycle structure\n    - make the most important concept visually dominant\n    - allow more atmosphere, glow, depth, and motion than the white version only where it improves explanation\n    - keep text readable from a screen-share distance\n    - keep the slide premium and controlled, not chaotic\n\n    Visible text discipline:\nAll visible text in the image must be exactly and only the text listed in the Visible text section. Do not add any words. Do not invent labels. Do not paraphrase. Do not shorten. Do not duplicate. Do not render prompt instructions, technical markers, file names, source names, safe-zone notes, or scaffolding.\n\n    Visible text:\n    Route work by risk, commitment depth, and control needs.\nLow-risk exploration\nTeam build commitment\nApplied capability design\nEvaluation and validation\n\n    Extra art direction:\n    Very clear and actionable.\n\n    Avoid:\n    neon overload, sci-fi wallpaper, fake command-center UI, glossy dashboard panels, stock people, robots, random holograms, decorative circuitry, unreadable microtext, vendor logos, watermarks, prompt scaffolding, and visual chaos.\n\n    Priority order:\n1. exact visible text fidelity\n2. thesis clarity and teaching story\n3. Dark Expressive family discipline\n4. semantic coupling between text and graphic structure\n5. premium enterprise credibility\n6. visual impressiveness without clutter"
    },
    {
      "slide_id": "GCF-09",
      "title": "Use the right package at the right altitude.",
      "narrative_role": "summary guidance",
      "objective": "Give a memorable decision rule to practitioners and leaders.",
      "visible_text": [
        "Use the right package at the right altitude.",
        "Teach with the doctrine.",
        "Commit with the operating model.",
        "Build with the implementation pattern.",
        "Validate with the evaluation harness."
      ],
      "white_render_prompt": "Create a sharp 16:9 editorial explainer slide.\n\n    Use Mainline White — Structured Expressive.\n\nThe background must be pure #FFFFFF white, flat, uniform, and brand-clean. Do not add any background tint, wash, gradient, vignette, paper texture, studio falloff, atmospheric shading, or non-white field treatment.\n\nThis must look like a premium enterprise editorial explainer and consulting-grade teaching artifact, not a poster, not a fake dashboard, not a template box farm, and not a cinematic hero graphic.\n\nVisual system:\n- pure white background only\n- bold red headline in #EB1700 or black headline with selective #EB1700 emphasis\n- black body text\n- neutral gray structure and dividers\n- flat white cards with thin neutral-gray borders\n- stronger internal hierarchy inside the most important cards\n- slightly abstract explanatory diagrams\n- integrated note cards and editorial bands\n- medium density, not sparse\n- moderate panelization, not over-boxed\n- elevated editorial rhythm with varied card scale and visual pacing\n- medium-high contrast emphasis\n- medium-high connector emphasis only where it explains the story\n- selective red accents where they improve emphasis, rhythm, or conceptual contrast\n- moderate asymmetry and right-side emphasis when the newer, stronger, or more important idea belongs there\n- strong semantic coupling between nearby text and supporting visual elements\n- strict clean-footer behavior without visible reserve markers\n\nWhite-mode visual posture:\n- graphically impressive\n- structured expressive\n- boardroom-safe\n- meaning-first\n- visually memorable without chaos\n- less conservative than a plain consulting template\n- never decorative for its own sake\n\n    Narrative objective:\n    Give a memorable decision rule to practitioners and leaders.\n\n    Visual explanation to depict:\n    altitude or ladder metaphor with package choice matched to operating need\n\n    Layout requirements:\n    four-step altitude ladder\n\n    Composition rules:\n    - anchor the title close to the top edge with minimal empty space above it\n    - keep title and subtitle compactly stacked in a tight top title zone\n    - use one dominant explanatory architecture across the middle\n    - vary card sizes and visual weight based on conceptual importance\n    - use integrated note cards attached directly to the regions they explain\n    - use slightly abstract diagrams, hinge shapes, control bands, routing paths, or lifecycle flows only when they clarify the meaning\n    - avoid equal-weight box grids unless the story truly requires equality\n    - make the most important concept visually dominant\n    - preserve clean margins and a clean footer without showing any reserve-space marker\n    - use white space actively, but do not make the slide timid or visually empty\n\n    Visible text discipline:\nAll visible text in the image must be exactly and only the text listed in the Visible text section. Do not add any words. Do not invent labels. Do not paraphrase. Do not shorten. Do not duplicate. Do not render prompt instructions, technical markers, file names, source names, safe-zone notes, or scaffolding.\n\n    Visible text:\n    Use the right package at the right altitude.\nTeach with the doctrine.\nCommit with the operating model.\nBuild with the implementation pattern.\nValidate with the evaluation harness.\n\n    Extra art direction:\n    Memorable, simple, and polished.\n\n    Avoid:\n    any non-white background, background tint, gradients in the white field, cinematic poster behavior, giant hero machinery, glossy UI, fake dashboards, stock people, robots, decorative data centers, random circuit boards, over-panelization, red everywhere, helper labels, prompt scaffolding, watermarks, and text gibberish.\n\n    Priority order:\n1. exact visible text fidelity\n2. thesis clarity and teaching story\n3. Mainline White or Dark Expressive family discipline\n4. semantic coupling between text and graphic structure\n5. premium enterprise credibility\n6. visual impressiveness without clutter",
      "dark_render_prompt": "Create a sharp 16:9 dark-mode editorial explainer slide.\n\n    Use Dark Expressive Editorial.\n\nThe background must be deep graphite, charcoal, or near-black with controlled gradients only when they help depth and focus. Use crisp white typography, restrained luminous #EB1700 accents, muted cool-gray structure, and high-contrast dark cards or panels.\n\nThis dark branch may be more cinematic and keynote-style than the white branch, but it must remain explanatory, premium, legible, and enterprise credible.\n\nDark-mode visual posture:\n- forceful but not chaotic\n- more atmospheric than white\n- stronger contrast between unstable and governed states\n- no neon overload\n- no glossy control-room UI\n- no cyberpunk wallpaper\n- no detached spectacle\n- no fake dashboards\n- no random energy ribbons without meaning\n- no product-board drift unless the slide is explicitly about product architecture\n\n    Narrative objective:\n    Give a memorable decision rule to practitioners and leaders.\n\n    Visual explanation to depict:\n    altitude or ladder metaphor with package choice matched to operating need\n\n    Layout requirements:\n    four-step altitude ladder\n\n    Composition rules:\n    - anchor the title close to the top edge with minimal dead space above it\n    - preserve the same teaching story as the white version\n    - create stronger contrast between unstable, naive, fragmented, or risky regions and governed, structured, reliable regions\n    - use a visually memorable central architecture, transformation path, control-plane flow, or lifecycle structure\n    - make the most important concept visually dominant\n    - allow more atmosphere, glow, depth, and motion than the white version only where it improves explanation\n    - keep text readable from a screen-share distance\n    - keep the slide premium and controlled, not chaotic\n\n    Visible text discipline:\nAll visible text in the image must be exactly and only the text listed in the Visible text section. Do not add any words. Do not invent labels. Do not paraphrase. Do not shorten. Do not duplicate. Do not render prompt instructions, technical markers, file names, source names, safe-zone notes, or scaffolding.\n\n    Visible text:\n    Use the right package at the right altitude.\nTeach with the doctrine.\nCommit with the operating model.\nBuild with the implementation pattern.\nValidate with the evaluation harness.\n\n    Extra art direction:\n    Memorable, simple, and polished.\n\n    Avoid:\n    neon overload, sci-fi wallpaper, fake command-center UI, glossy dashboard panels, stock people, robots, random holograms, decorative circuitry, unreadable microtext, vendor logos, watermarks, prompt scaffolding, and visual chaos.\n\n    Priority order:\n1. exact visible text fidelity\n2. thesis clarity and teaching story\n3. Dark Expressive family discipline\n4. semantic coupling between text and graphic structure\n5. premium enterprise credibility\n6. visual impressiveness without clutter"
    },
    {
      "slide_id": "GCF-10",
      "title": "Leadership move: fund the discipline, not just the interface.",
      "narrative_role": "closing leadership ask",
      "objective": "Close the family story with a unifying leadership action.",
      "visible_text": [
        "Leadership move: fund the discipline, not just the interface.",
        "Support doctrine.",
        "Support controlled commitment.",
        "Support applied capability design.",
        "Support validation and maintenance."
      ],
      "white_render_prompt": "Create a sharp 16:9 editorial explainer slide.\n\n    Use Mainline White — Structured Expressive.\n\nThe background must be pure #FFFFFF white, flat, uniform, and brand-clean. Do not add any background tint, wash, gradient, vignette, paper texture, studio falloff, atmospheric shading, or non-white field treatment.\n\nThis must look like a premium enterprise editorial explainer and consulting-grade teaching artifact, not a poster, not a fake dashboard, not a template box farm, and not a cinematic hero graphic.\n\nVisual system:\n- pure white background only\n- bold red headline in #EB1700 or black headline with selective #EB1700 emphasis\n- black body text\n- neutral gray structure and dividers\n- flat white cards with thin neutral-gray borders\n- stronger internal hierarchy inside the most important cards\n- slightly abstract explanatory diagrams\n- integrated note cards and editorial bands\n- medium density, not sparse\n- moderate panelization, not over-boxed\n- elevated editorial rhythm with varied card scale and visual pacing\n- medium-high contrast emphasis\n- medium-high connector emphasis only where it explains the story\n- selective red accents where they improve emphasis, rhythm, or conceptual contrast\n- moderate asymmetry and right-side emphasis when the newer, stronger, or more important idea belongs there\n- strong semantic coupling between nearby text and supporting visual elements\n- strict clean-footer behavior without visible reserve markers\n\nWhite-mode visual posture:\n- graphically impressive\n- structured expressive\n- boardroom-safe\n- meaning-first\n- visually memorable without chaos\n- less conservative than a plain consulting template\n- never decorative for its own sake\n\n    Narrative objective:\n    Close the family story with a unifying leadership action.\n\n    Visual explanation to depict:\n    leadership investment stack showing disciplined investment priorities across the family\n\n    Layout requirements:\n    clean closing call-to-action with four funding pillars\n\n    Composition rules:\n    - anchor the title close to the top edge with minimal empty space above it\n    - keep title and subtitle compactly stacked in a tight top title zone\n    - use one dominant explanatory architecture across the middle\n    - vary card sizes and visual weight based on conceptual importance\n    - use integrated note cards attached directly to the regions they explain\n    - use slightly abstract diagrams, hinge shapes, control bands, routing paths, or lifecycle flows only when they clarify the meaning\n    - avoid equal-weight box grids unless the story truly requires equality\n    - make the most important concept visually dominant\n    - preserve clean margins and a clean footer without showing any reserve-space marker\n    - use white space actively, but do not make the slide timid or visually empty\n\n    Visible text discipline:\nAll visible text in the image must be exactly and only the text listed in the Visible text section. Do not add any words. Do not invent labels. Do not paraphrase. Do not shorten. Do not duplicate. Do not render prompt instructions, technical markers, file names, source names, safe-zone notes, or scaffolding.\n\n    Visible text:\n    Leadership move: fund the discipline, not just the interface.\nSupport doctrine.\nSupport controlled commitment.\nSupport applied capability design.\nSupport validation and maintenance.\n\n    Extra art direction:\n    Strong, strategic, and board-ready.\n\n    Avoid:\n    any non-white background, background tint, gradients in the white field, cinematic poster behavior, giant hero machinery, glossy UI, fake dashboards, stock people, robots, decorative data centers, random circuit boards, over-panelization, red everywhere, helper labels, prompt scaffolding, watermarks, and text gibberish.\n\n    Priority order:\n1. exact visible text fidelity\n2. thesis clarity and teaching story\n3. Mainline White or Dark Expressive family discipline\n4. semantic coupling between text and graphic structure\n5. premium enterprise credibility\n6. visual impressiveness without clutter",
      "dark_render_prompt": "Create a sharp 16:9 dark-mode editorial explainer slide.\n\n    Use Dark Expressive Editorial.\n\nThe background must be deep graphite, charcoal, or near-black with controlled gradients only when they help depth and focus. Use crisp white typography, restrained luminous #EB1700 accents, muted cool-gray structure, and high-contrast dark cards or panels.\n\nThis dark branch may be more cinematic and keynote-style than the white branch, but it must remain explanatory, premium, legible, and enterprise credible.\n\nDark-mode visual posture:\n- forceful but not chaotic\n- more atmospheric than white\n- stronger contrast between unstable and governed states\n- no neon overload\n- no glossy control-room UI\n- no cyberpunk wallpaper\n- no detached spectacle\n- no fake dashboards\n- no random energy ribbons without meaning\n- no product-board drift unless the slide is explicitly about product architecture\n\n    Narrative objective:\n    Close the family story with a unifying leadership action.\n\n    Visual explanation to depict:\n    leadership investment stack showing disciplined investment priorities across the family\n\n    Layout requirements:\n    clean closing call-to-action with four funding pillars\n\n    Composition rules:\n    - anchor the title close to the top edge with minimal dead space above it\n    - preserve the same teaching story as the white version\n    - create stronger contrast between unstable, naive, fragmented, or risky regions and governed, structured, reliable regions\n    - use a visually memorable central architecture, transformation path, control-plane flow, or lifecycle structure\n    - make the most important concept visually dominant\n    - allow more atmosphere, glow, depth, and motion than the white version only where it improves explanation\n    - keep text readable from a screen-share distance\n    - keep the slide premium and controlled, not chaotic\n\n    Visible text discipline:\nAll visible text in the image must be exactly and only the text listed in the Visible text section. Do not add any words. Do not invent labels. Do not paraphrase. Do not shorten. Do not duplicate. Do not render prompt instructions, technical markers, file names, source names, safe-zone notes, or scaffolding.\n\n    Visible text:\n    Leadership move: fund the discipline, not just the interface.\nSupport doctrine.\nSupport controlled commitment.\nSupport applied capability design.\nSupport validation and maintenance.\n\n    Extra art direction:\n    Strong, strategic, and board-ready.\n\n    Avoid:\n    neon overload, sci-fi wallpaper, fake command-center UI, glossy dashboard panels, stock people, robots, random holograms, decorative circuitry, unreadable microtext, vendor logos, watermarks, prompt scaffolding, and visual chaos.\n\n    Priority order:\n1. exact visible text fidelity\n2. thesis clarity and teaching story\n3. Dark Expressive family discipline\n4. semantic coupling between text and graphic structure\n5. premium enterprise credibility\n6. visual impressiveness without clutter"
    }
  ]
}