{ "bundle": "Governed Capability Family Full Prompt Package", "version": "v0.3", "generated_at": "2026-06-18T12:37:42Z", "prompt_family": "Mainline White corrected + Dark Expressive", "packs": [ { "package_name": "AI Capability Discipline", "source_package_version": "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": "AICD-01", "title": "Stop Building AI Theater. Build Capability.", "narrative_role": "opening thesis", "objective": "Reset the reader away from prompt hype and toward the full capability stack.", "visible_text": [ "AI Capability Discipline", "Stop Building AI Theater. Build Capability.", "Prompts, agents, tools, and evals are components.", "Capability requires intent, source authority, schemas, governance, telemetry, maintenance, and measurable value.", "Controlled-sharing candidate", "Not final policy" ], "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 Reset the reader away from prompt hype and toward the full capability stack.\n\n Visual explanation to depict:\n scattered components on the left converging into a disciplined capability engine and outcome on the right, with governance and operations wrapping the system\n\n Layout requirements:\n hero opener with a bold title block, central transformation graphic, and compact evidence/status footer\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\nStop Building AI Theater. Build Capability.\nPrompts, agents, tools, and evals are components.\nCapability requires intent, source authority, schemas, governance, telemetry, maintenance, and measurable value.\nControlled-sharing candidate\nNot final policy\n\n Extra art direction:\n Make the before-state feel fragmented and seductive, and the after-state coherent, governed, and operational.\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 Reset the reader away from prompt hype and toward the full capability stack.\n\n Visual explanation to depict:\n scattered components on the left converging into a disciplined capability engine and outcome on the right, with governance and operations wrapping the system\n\n Layout requirements:\n hero opener with a bold title block, central transformation graphic, and compact evidence/status footer\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\nStop Building AI Theater. Build Capability.\nPrompts, agents, tools, and evals are components.\nCapability requires intent, source authority, schemas, governance, telemetry, maintenance, and measurable value.\nControlled-sharing candidate\nNot final policy\n\n Extra art direction:\n Make the before-state feel fragmented and seductive, and the after-state coherent, governed, and operational.\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": "AICD-02", "title": "AI Is Not Magic. Capability Is Engineered.", "narrative_role": "mental model reset", "objective": "Show that the model is only one part of the system.", "visible_text": [ "AI Is Not Magic. Capability Is Engineered.", "Models can generate.", "Systems determine whether the work is safe, grounded, useful, and repeatable.", "The capability lives in the operating system around the model." ], "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 that the model is only one part of the system.\n\n Visual explanation to depict:\n layered system diagram with a model as one component inside a larger engineered operating system made of context, controls, evals, review, and maintenance\n\n Layout requirements:\n three-tier or concentric-layer explainer with the model visibly smaller than the surrounding system layers\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 Is Not Magic. Capability Is Engineered.\nModels can generate.\nSystems determine whether the work is safe, grounded, useful, and repeatable.\nThe capability lives in the operating system around the model.\n\n Extra art direction:\n Avoid mystical AI imagery. Make it feel like serious systems engineering.\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 that the model is only one part of the system.\n\n Visual explanation to depict:\n layered system diagram with a model as one component inside a larger engineered operating system made of context, controls, evals, review, and maintenance\n\n Layout requirements:\n three-tier or concentric-layer explainer with the model visibly smaller than the surrounding system layers\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 Is Not Magic. Capability Is Engineered.\nModels can generate.\nSystems determine whether the work is safe, grounded, useful, and repeatable.\nThe capability lives in the operating system around the model.\n\n Extra art direction:\n Avoid mystical AI imagery. Make it feel like serious systems engineering.\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": "AICD-03", "title": "Components Are Not Capabilities.", "narrative_role": "decomposition", "objective": "Distinguish between ingredients and an actual operational capability.", "visible_text": [ "Components Are Not Capabilities.", "Prompt", "Agent", "Tool", "Skill", "Eval", "Useful ingredients do not equal a reliable 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 Distinguish between ingredients and an actual operational capability.\n\n Visual explanation to depict:\n ingredient tiles or modules feeding into a separate assembled capability block with an explicit gap between parts and operating capability\n\n Layout requirements:\n modular comparison layout with a left panel of components and a right panel showing assembled capability criteria\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 Components Are Not Capabilities.\nPrompt\nAgent\nTool\nSkill\nEval\nUseful ingredients do not equal a reliable capability.\n\n Extra art direction:\n Use crisp object cards and a clear assembly narrative.\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 Distinguish between ingredients and an actual operational capability.\n\n Visual explanation to depict:\n ingredient tiles or modules feeding into a separate assembled capability block with an explicit gap between parts and operating capability\n\n Layout requirements:\n modular comparison layout with a left panel of components and a right panel showing assembled capability criteria\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 Components Are Not Capabilities.\nPrompt\nAgent\nTool\nSkill\nEval\nUseful ingredients do not equal a reliable capability.\n\n Extra art direction:\n Use crisp object cards and a clear assembly narrative.\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": "AICD-04", "title": "The Capability Equation", "narrative_role": "core framework", "objective": "Make the full capability equation memorable and teachable.", "visible_text": [ "The Capability Equation", "Capability = intent + approved context + source authority + schemas + tools + evals + human review + telemetry + maintenance + measurable value", "Miss enough of these, and the result is theater." ], "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 Make the full capability equation memorable and teachable.\n\n Visual explanation to depict:\n a high-end equation slide with each term represented as a structured token or module, joined into one coherent capability expression\n\n Layout requirements:\n equation-centric composition with supporting iconless modules and a short warning callout\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 The Capability Equation\nCapability = intent + approved context + source authority + schemas + tools + evals + human review + telemetry + maintenance + measurable value\nMiss enough of these, and the result is theater.\n\n Extra art direction:\n This should feel iconic and memorable, almost like a flagship framework slide.\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 Make the full capability equation memorable and teachable.\n\n Visual explanation to depict:\n a high-end equation slide with each term represented as a structured token or module, joined into one coherent capability expression\n\n Layout requirements:\n equation-centric composition with supporting iconless modules and a short warning callout\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 The Capability Equation\nCapability = intent + approved context + source authority + schemas + tools + evals + human review + telemetry + maintenance + measurable value\nMiss enough of these, and the result is theater.\n\n Extra art direction:\n This should feel iconic and memorable, almost like a flagship framework slide.\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": "AICD-05", "title": "Intent Comes Before Evals.", "narrative_role": "evaluation logic", "objective": "Show that evaluation quality depends on an explicit intended task and decision frame.", "visible_text": [ "Intent Comes Before Evals.", "If the task is vague, the eval can be beautifully wrong.", "Clarify the job, the output contract, the reviewer, and the decision rule first." ], "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 that evaluation quality depends on an explicit intended task and decision frame.\n\n Visual explanation to depict:\n flow from intended task definition to output contract to evaluation harness to decision, with a warning branch showing invalid evals when intent is fuzzy\n\n Layout requirements:\n left-to-right decision flow with a visible failure branch\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 Intent Comes Before Evals.\nIf the task is vague, the eval can be beautifully wrong.\nClarify the job, the output contract, the reviewer, and the decision rule first.\n\n Extra art direction:\n Make the invalid-eval path visibly attractive but wrong.\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 that evaluation quality depends on an explicit intended task and decision frame.\n\n Visual explanation to depict:\n flow from intended task definition to output contract to evaluation harness to decision, with a warning branch showing invalid evals when intent is fuzzy\n\n Layout requirements:\n left-to-right decision flow with a visible failure branch\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 Intent Comes Before Evals.\nIf the task is vague, the eval can be beautifully wrong.\nClarify the job, the output contract, the reviewer, and the decision rule first.\n\n Extra art direction:\n Make the invalid-eval path visibly attractive but wrong.\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": "AICD-06", "title": "Context Is the Control Plane.", "narrative_role": "context and grounding", "objective": "Teach that context determines what the model can know and do.", "visible_text": [ "Context Is the Control Plane.", "Context shapes what the model can know, cite, infer, and escalate.", "Source hierarchy matters.", "Approved context beats persuasive prose." ], "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 Teach that context determines what the model can know and do.\n\n Visual explanation to depict:\n control-plane diagram where context packets, source tiers, and instructions govern model behavior and downstream outputs\n\n Layout requirements:\n central control-plane graphic with source layers and controlled output paths\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 Context Is the Control Plane.\nContext shapes what the model can know, cite, infer, and escalate.\nSource hierarchy matters.\nApproved context beats persuasive prose.\n\n Extra art direction:\n Make context feel like the governing infrastructure, not extra flavor text.\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 Teach that context determines what the model can know and do.\n\n Visual explanation to depict:\n control-plane diagram where context packets, source tiers, and instructions govern model behavior and downstream outputs\n\n Layout requirements:\n central control-plane graphic with source layers and controlled output paths\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 Context Is the Control Plane.\nContext shapes what the model can know, cite, infer, and escalate.\nSource hierarchy matters.\nApproved context beats persuasive prose.\n\n Extra art direction:\n Make context feel like the governing infrastructure, not extra flavor text.\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": "AICD-07", "title": "Schema-First Makes AI Inspectable.", "narrative_role": "inspectability", "objective": "Show how schemas and output contracts make AI work governable.", "visible_text": [ "Schema-First Makes AI Inspectable.", "Free-form prose is easy to admire and hard to govern.", "Schemas turn AI work into testable contracts.", "Inspectable output makes review faster and stronger." ], "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 schemas and output contracts make AI work governable.\n\n Visual explanation to depict:\n before-and-after comparison between messy prose output and structured schema-driven output that can be checked, scored, and routed\n\n Layout requirements:\n split-screen comparison with a quality uplift arrow or transformation bridge\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 Schema-First Makes AI Inspectable.\nFree-form prose is easy to admire and hard to govern.\nSchemas turn AI work into testable contracts.\nInspectable output makes review faster and stronger.\n\n Extra art direction:\n Lean into clarity and reviewability.\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 schemas and output contracts make AI work governable.\n\n Visual explanation to depict:\n before-and-after comparison between messy prose output and structured schema-driven output that can be checked, scored, and routed\n\n Layout requirements:\n split-screen comparison with a quality uplift arrow or transformation bridge\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 Schema-First Makes AI Inspectable.\nFree-form prose is easy to admire and hard to govern.\nSchemas turn AI work into testable contracts.\nInspectable output makes review faster and stronger.\n\n Extra art direction:\n Lean into clarity and reviewability.\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": "AICD-08", "title": "Governance Starts With Routing.", "narrative_role": "governance model", "objective": "Make governance feel like intelligent routing, not blanket obstruction.", "visible_text": [ "Governance Starts With Routing.", "Not every use case needs the same lane.", "Route by data, risk, actionability, ownership, and operational impact.", "Good routing is proportional governance." ], "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 Make governance feel like intelligent routing, not blanket obstruction.\n\n Visual explanation to depict:\n lane-routing diagram or triage board moving proposals into different governance paths based on attributes\n\n Layout requirements:\n multi-lane routing board with clear decision triggers and proportional rigor\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 Governance Starts With Routing.\nNot every use case needs the same lane.\nRoute by data, risk, actionability, ownership, and operational impact.\nGood routing is proportional governance.\n\n Extra art direction:\n Make the lanes intelligible at a glance.\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 Make governance feel like intelligent routing, not blanket obstruction.\n\n Visual explanation to depict:\n lane-routing diagram or triage board moving proposals into different governance paths based on attributes\n\n Layout requirements:\n multi-lane routing board with clear decision triggers and proportional rigor\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 Governance Starts With Routing.\nNot every use case needs the same lane.\nRoute by data, risk, actionability, ownership, and operational impact.\nGood routing is proportional governance.\n\n Extra art direction:\n Make the lanes intelligible at a glance.\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": "AICD-09", "title": "External Learning Is Not Enterprise Execution.", "narrative_role": "tool boundary", "objective": "Clarify the difference between learning tools and approved enterprise operating surfaces.", "visible_text": [ "External Learning Is Not Enterprise Execution.", "Commercial tools can teach patterns.", "They do not automatically create approved enterprise data paths.", "Personal experimentation is not sanctioned enterprise execution." ], "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 Clarify the difference between learning tools and approved enterprise operating surfaces.\n\n Visual explanation to depict:\n two clearly separated zones, one for personal learning/synthetic data experimentation and one for approved enterprise execution with explicit governance barriers between them\n\n Layout requirements:\n two-column boundary diagram with a clear policy boundary and approval bridge\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 External Learning Is Not Enterprise Execution.\nCommercial tools can teach patterns.\nThey do not automatically create approved enterprise data paths.\nPersonal experimentation is not sanctioned enterprise execution.\n\n Extra art direction:\n Board-safe, policy-literate, crisp.\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 Clarify the difference between learning tools and approved enterprise operating surfaces.\n\n Visual explanation to depict:\n two clearly separated zones, one for personal learning/synthetic data experimentation and one for approved enterprise execution with explicit governance barriers between them\n\n Layout requirements:\n two-column boundary diagram with a clear policy boundary and approval bridge\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 External Learning Is Not Enterprise Execution.\nCommercial tools can teach patterns.\nThey do not automatically create approved enterprise data paths.\nPersonal experimentation is not sanctioned enterprise execution.\n\n Extra art direction:\n Board-safe, policy-literate, crisp.\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": "AICD-10", "title": "Harnesses Need Maintenance.", "narrative_role": "lifecycle truth", "objective": "Show that prompts, evals, schemas, and source maps drift over time and require upkeep.", "visible_text": [ "Harnesses Need Maintenance.", "Prompts drift.", "Sources change.", "Schemas evolve.", "Evals stale out.", "A capability is maintained, not merely launched." ], "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 that prompts, evals, schemas, and source maps drift over time and require upkeep.\n\n Visual explanation to depict:\n a maintenance loop or lifecycle ring around a capability, showing drift pressures and refresh activities\n\n Layout requirements:\n circular lifecycle or flywheel with maintenance checkpoints\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 Harnesses Need Maintenance.\nPrompts drift.\nSources change.\nSchemas evolve.\nEvals stale out.\nA capability is maintained, not merely launched.\n\n Extra art direction:\n Make the notion of slow drift tangible.\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 that prompts, evals, schemas, and source maps drift over time and require upkeep.\n\n Visual explanation to depict:\n a maintenance loop or lifecycle ring around a capability, showing drift pressures and refresh activities\n\n Layout requirements:\n circular lifecycle or flywheel with maintenance checkpoints\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 Harnesses Need Maintenance.\nPrompts drift.\nSources change.\nSchemas evolve.\nEvals stale out.\nA capability is maintained, not merely launched.\n\n Extra art direction:\n Make the notion of slow drift tangible.\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": "AICD-11", "title": "Tool Pruning Is a Control.", "narrative_role": "agent/tool governance", "objective": "Show that more tools can make agents worse, not better.", "visible_text": [ "Tool Pruning Is a Control.", "More tools can make agents worse.", "Every tool changes the failure surface.", "Prune aggressively. Add only what the job requires." ], "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 that more tools can make agents worse, not better.\n\n Visual explanation to depict:\n toolset reduction story showing a tangled tool cluster simplified into a smaller, more controlled and reliable tool surface\n\n Layout requirements:\n before-and-after tool surface comparison\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 Tool Pruning Is a Control.\nMore tools can make agents worse.\nEvery tool changes the failure surface.\nPrune aggressively. Add only what the job requires.\n\n Extra art direction:\n Emphasize reduced complexity and stronger control.\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 that more tools can make agents worse, not better.\n\n Visual explanation to depict:\n toolset reduction story showing a tangled tool cluster simplified into a smaller, more controlled and reliable tool surface\n\n Layout requirements:\n before-and-after tool surface comparison\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 Tool Pruning Is a Control.\nMore tools can make agents worse.\nEvery tool changes the failure surface.\nPrune aggressively. Add only what the job requires.\n\n Extra art direction:\n Emphasize reduced complexity and stronger control.\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": "AICD-12", "title": "Advisory Is Not Control Plane.", "narrative_role": "document vs runtime distinction", "objective": "Differentiate guidance artifacts from runtime-enforcing systems.", "visible_text": [ "Advisory Is Not Control Plane.", "A document can guide build decisions.", "It does not enforce runtime behavior.", "Advisory rigor matters. Runtime control matters too." ], "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 Differentiate guidance artifacts from runtime-enforcing systems.\n\n Visual explanation to depict:\n split diagram contrasting a static advisory document with a live runtime control plane that enforces behavior\n\n Layout requirements:\n side-by-side conceptual comparison with enforcement mechanisms visible on the runtime side\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 Advisory Is Not Control Plane.\nA document can guide build decisions.\nIt does not enforce runtime behavior.\nAdvisory rigor matters. Runtime control matters too.\n\n Extra art direction:\n Respect both sides while making the distinction unmistakable.\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 Differentiate guidance artifacts from runtime-enforcing systems.\n\n Visual explanation to depict:\n split diagram contrasting a static advisory document with a live runtime control plane that enforces behavior\n\n Layout requirements:\n side-by-side conceptual comparison with enforcement mechanisms visible on the runtime side\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 Advisory Is Not Control Plane.\nA document can guide build decisions.\nIt does not enforce runtime behavior.\nAdvisory rigor matters. Runtime control matters too.\n\n Extra art direction:\n Respect both sides while making the distinction unmistakable.\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": "AICD-13", "title": "Lifecycle Lens Shows the Pattern.", "narrative_role": "applied synthesis", "objective": "Bring the full lifecycle together from idea to operation.", "visible_text": [ "Lifecycle Lens Shows the Pattern.", "Discover", "Design", "Validate", "Govern", "Operate", "Maintain", "The pattern repeats across real AI capability work." ], "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 Bring the full lifecycle together from idea to operation.\n\n Visual explanation to depict:\n clean lifecycle map connecting discovery, design, validation, governance, operation, and maintenance\n\n Layout requirements:\n left-to-right staged lifecycle or circular lifecycle with six distinct stages\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 Lifecycle Lens Shows the Pattern.\nDiscover\nDesign\nValidate\nGovern\nOperate\nMaintain\nThe pattern repeats across real AI capability work.\n\n Extra art direction:\n Use a clean, teachable structure that could stand alone as a reference slide.\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 Bring the full lifecycle together from idea to operation.\n\n Visual explanation to depict:\n clean lifecycle map connecting discovery, design, validation, governance, operation, and maintenance\n\n Layout requirements:\n left-to-right staged lifecycle or circular lifecycle with six distinct stages\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 Lifecycle Lens Shows the Pattern.\nDiscover\nDesign\nValidate\nGovern\nOperate\nMaintain\nThe pattern repeats across real AI capability work.\n\n Extra art direction:\n Use a clean, teachable structure that could stand alone as a reference slide.\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": "AICD-14", "title": "The Leadership Ask", "narrative_role": "close and call to action", "objective": "Conclude with a concrete leadership ask rather than abstract admiration.", "visible_text": [ "The Leadership Ask", "Fund the discipline before the interface.", "Require source authority.", "Demand explicit routing.", "Insist on eval validity.", "Support maintenance, ownership, and telemetry." ], "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 Conclude with a concrete leadership ask rather than abstract admiration.\n\n Visual explanation to depict:\n executive call-to-action slide with five disciplined commitments arranged around a central leadership mandate\n\n Layout requirements:\n clean closing slide with a strong central message and five structured commitments\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 The Leadership Ask\nFund the discipline before the interface.\nRequire source authority.\nDemand explicit routing.\nInsist on eval validity.\nSupport maintenance, ownership, and telemetry.\n\n Extra art direction:\n Confident, decisive, and boardroom-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 Conclude with a concrete leadership ask rather than abstract admiration.\n\n Visual explanation to depict:\n executive call-to-action slide with five disciplined commitments arranged around a central leadership mandate\n\n Layout requirements:\n clean closing slide with a strong central message and five structured commitments\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 The Leadership Ask\nFund the discipline before the interface.\nRequire source authority.\nDemand explicit routing.\nInsist on eval validity.\nSupport maintenance, ownership, and telemetry.\n\n Extra art direction:\n Confident, decisive, and boardroom-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" } ] }, { "package_name": "Enterprise Architecture Review Assistant", "source_package_version": "v1.14.1", "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": "EARA-01", "title": "Enterprise Architecture Review Assistant", "narrative_role": "opening thesis", "objective": "Introduce the assistant as a governed review capability, not just an AI feature.", "visible_text": [ "Enterprise Architecture Review Assistant", "A governed review capability for architecture intake, analysis, evidence, and recommendation support.", "Controlled build-preparation candidate", "Not broad pilot or production" ], "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 assistant as a governed review capability, not just an AI feature.\n\n Visual explanation to depict:\n hero opener showing an architecture review engine transforming scattered inputs into structured recommendations and evidence\n\n Layout requirements:\n hero title with central review-engine graphic and succinct status footer\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\nA governed review capability for architecture intake, analysis, evidence, and recommendation support.\nControlled build-preparation candidate\nNot broad pilot or production\n\n Extra art direction:\n Premium and authoritative, with architecture-review seriousness.\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 assistant as a governed review capability, not just an AI feature.\n\n Visual explanation to depict:\n hero opener showing an architecture review engine transforming scattered inputs into structured recommendations and evidence\n\n Layout requirements:\n hero title with central review-engine graphic and succinct status footer\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\nA governed review capability for architecture intake, analysis, evidence, and recommendation support.\nControlled build-preparation candidate\nNot broad pilot or production\n\n Extra art direction:\n Premium and authoritative, with architecture-review seriousness.\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": "EARA-02", "title": "Why leadership should care", "narrative_role": "executive relevance", "objective": "Frame the business problem clearly for leadership.", "visible_text": [ "Why leadership should care", "Architecture review pressure is rising.", "Review knowledge is scattered.", "Decision quality depends on source authority, review consistency, and explainable outputs." ], "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 Frame the business problem clearly for leadership.\n\n Visual explanation to depict:\n pressure-versus-fragmentation story with demand pressure rising on one side and scattered knowledge fragments on the other, resolved by a structured capability\n\n Layout requirements:\n problem/response composition with tension on the left and a structured answer on the right\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 Why leadership should care\nArchitecture review pressure is rising.\nReview knowledge is scattered.\nDecision quality depends on source authority, review consistency, and explainable outputs.\n\n Extra art direction:\n Make the pain visible without becoming melodramatic.\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 Frame the business problem clearly for leadership.\n\n Visual explanation to depict:\n pressure-versus-fragmentation story with demand pressure rising on one side and scattered knowledge fragments on the other, resolved by a structured capability\n\n Layout requirements:\n problem/response composition with tension on the left and a structured answer on the right\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 Why leadership should care\nArchitecture review pressure is rising.\nReview knowledge is scattered.\nDecision quality depends on source authority, review consistency, and explainable outputs.\n\n Extra art direction:\n Make the pain visible without becoming melodramatic.\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": "EARA-03", "title": "Do we want a clever demo, or a durable review capability?", "narrative_role": "decision framing", "objective": "Differentiate novelty from durable operational value.", "visible_text": [ "Do we want a clever demo, or a durable review capability?", "A demo proves possibility.", "A durable capability requires evidence loops, source discipline, roles, and sustainment." ], "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 Differentiate novelty from durable operational value.\n\n Visual explanation to depict:\n comparison between a shiny demo artifact and a durable capability stack with governance, review, and sustainment\n\n Layout requirements:\n balanced comparison slide with a visible maturity gap\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 Do we want a clever demo, or a durable review capability?\nA demo proves possibility.\nA durable capability requires evidence loops, source discipline, roles, and sustainment.\n\n Extra art direction:\n The demo side can look tempting; the durable side should look trustworthy.\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 Differentiate novelty from durable operational value.\n\n Visual explanation to depict:\n comparison between a shiny demo artifact and a durable capability stack with governance, review, and sustainment\n\n Layout requirements:\n balanced comparison slide with a visible maturity gap\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 Do we want a clever demo, or a durable review capability?\nA demo proves possibility.\nA durable capability requires evidence loops, source discipline, roles, and sustainment.\n\n Extra art direction:\n The demo side can look tempting; the durable side should look trustworthy.\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": "EARA-04", "title": "Architecture review pressure is rising while review knowledge remains scattered.", "narrative_role": "problem detail", "objective": "Explain the operational pain in concrete terms.", "visible_text": [ "Architecture review pressure is rising while review knowledge remains scattered.", "Inputs arrive from many channels.", "Criteria live across documents, teams, and habits.", "The review brain is fragmented." ], "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 Explain the operational pain in concrete terms.\n\n Visual explanation to depict:\n many inbound artifacts and channels flowing into fragmented review knowledge, highlighting the need for consolidation\n\n Layout requirements:\n inbound chaos converging on a broken review surface, with a hint of structured consolidation\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 Architecture review pressure is rising while review knowledge remains scattered.\nInputs arrive from many channels.\nCriteria live across documents, teams, and habits.\nThe review brain is fragmented.\n\n Extra art direction:\n Use artifact-like tiles rather than generic icons.\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 Explain the operational pain in concrete terms.\n\n Visual explanation to depict:\n many inbound artifacts and channels flowing into fragmented review knowledge, highlighting the need for consolidation\n\n Layout requirements:\n inbound chaos converging on a broken review surface, with a hint of structured consolidation\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 Architecture review pressure is rising while review knowledge remains scattered.\nInputs arrive from many channels.\nCriteria live across documents, teams, and habits.\nThe review brain is fragmented.\n\n Extra art direction:\n Use artifact-like tiles rather than generic icons.\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": "EARA-05", "title": "“Build an agent” is the wrong center of gravity.", "narrative_role": "mental model correction", "objective": "Show that the center of gravity is the review logic, not the agent label.", "visible_text": [ "“Build an agent” is the wrong center of gravity.", "The center is not the chat surface.", "The center is the review logic, source authority, decision criteria, and evidence model." ], "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 that the center of gravity is the review logic, not the agent label.\n\n Visual explanation to depict:\n a miscentered spotlight on an agent/chat icon contrasted with the real core made of review logic, criteria, source maps, and evidence\n\n Layout requirements:\n off-center illusion corrected by a structured 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 “Build an agent” is the wrong center of gravity.\nThe center is not the chat surface.\nThe center is the review logic, source authority, decision criteria, and evidence model.\n\n Extra art direction:\n This should feel like a sharp reframing slide.\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 that the center of gravity is the review logic, not the agent label.\n\n Visual explanation to depict:\n a miscentered spotlight on an agent/chat icon contrasted with the real core made of review logic, criteria, source maps, and evidence\n\n Layout requirements:\n off-center illusion corrected by a structured 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 “Build an agent” is the wrong center of gravity.\nThe center is not the chat surface.\nThe center is the review logic, source authority, decision criteria, and evidence model.\n\n Extra art direction:\n This should feel like a sharp reframing slide.\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": "EARA-06", "title": "The capability has three layers — only one is the agent experience.", "narrative_role": "architecture model", "objective": "Explain the layered architecture cleanly.", "visible_text": [ "The capability has three layers — only one is the agent experience.", "Layer 1: review brain", "Layer 2: governance and evidence loop", "Layer 3: user experience layer" ], "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 Explain the layered architecture cleanly.\n\n Visual explanation to depict:\n three-layer architecture stack showing the user experience as the topmost visible layer over the deeper review brain and governance layers\n\n Layout requirements:\n clean layered stack 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 The capability has three layers — only one is the agent experience.\nLayer 1: review brain\nLayer 2: governance and evidence loop\nLayer 3: user experience layer\n\n Extra art direction:\n Make the hidden layers feel more substantive than the visible top layer.\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 Explain the layered architecture cleanly.\n\n Visual explanation to depict:\n three-layer architecture stack showing the user experience as the topmost visible layer over the deeper review brain and governance layers\n\n Layout requirements:\n clean layered stack 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 The capability has three layers — only one is the agent experience.\nLayer 1: review brain\nLayer 2: governance and evidence loop\nLayer 3: user experience layer\n\n Extra art direction:\n Make the hidden layers feel more substantive than the visible top layer.\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": "EARA-07", "title": "The hard work is codifying how the enterprise judges architecture fitness.", "narrative_role": "core value", "objective": "Show the true work of the capability.", "visible_text": [ "The hard work is codifying how the enterprise judges architecture fitness.", "Criteria", "Evidence", "Trade-offs", "Exceptions", "Recommendations" ], "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 true work of the capability.\n\n Visual explanation to depict:\n codified review brain made of criteria, evidence, trade-off analysis, and recommendation logic\n\n Layout requirements:\n central review-brain map with five key judgment components\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 The hard work is codifying how the enterprise judges architecture fitness.\nCriteria\nEvidence\nTrade-offs\nExceptions\nRecommendations\n\n Extra art direction:\n Serious, methodical, and knowledge-rich.\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 true work of the capability.\n\n Visual explanation to depict:\n codified review brain made of criteria, evidence, trade-off analysis, and recommendation logic\n\n Layout requirements:\n central review-brain map with five key judgment components\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 The hard work is codifying how the enterprise judges architecture fitness.\nCriteria\nEvidence\nTrade-offs\nExceptions\nRecommendations\n\n Extra art direction:\n Serious, methodical, and knowledge-rich.\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": "EARA-08", "title": "The first proof is an evidence loop, not a shiny interface.", "narrative_role": "proof strategy", "objective": "Focus the first proof on capability substance and feedback.", "visible_text": [ "The first proof is an evidence loop, not a shiny interface.", "Start with source package.", "Run structured review.", "Capture reviewer feedback.", "Improve the logic." ], "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 Focus the first proof on capability substance and feedback.\n\n Visual explanation to depict:\n tight evidence loop cycling through source package, structured review, reviewer feedback, and refinement\n\n Layout requirements:\n four-step loop or flywheel\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 The first proof is an evidence loop, not a shiny interface.\nStart with source package.\nRun structured review.\nCapture reviewer feedback.\nImprove the logic.\n\n Extra art direction:\n Show disciplined iteration, not spectacle.\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 Focus the first proof on capability substance and feedback.\n\n Visual explanation to depict:\n tight evidence loop cycling through source package, structured review, reviewer feedback, and refinement\n\n Layout requirements:\n four-step loop or flywheel\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 The first proof is an evidence loop, not a shiny interface.\nStart with source package.\nRun structured review.\nCapture reviewer feedback.\nImprove the logic.\n\n Extra art direction:\n Show disciplined iteration, not spectacle.\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": "EARA-09", "title": "Deterministic where possible. AI where ambiguity exists. Human where judgment matters.", "narrative_role": "operating principle", "objective": "Show the balanced division of labor.", "visible_text": [ "Deterministic where possible.", "AI where ambiguity exists.", "Human where judgment matters.", "Use each mode where it is strongest." ], "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 balanced division of labor.\n\n Visual explanation to depict:\n three-mode operating model with deterministic automation, AI reasoning, and human judgment each occupying the right zone\n\n Layout requirements:\n three-column or triangular operating 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 Deterministic where possible.\nAI where ambiguity exists.\nHuman where judgment matters.\nUse each mode where it is strongest.\n\n Extra art direction:\n Balanced, precise, and teachable.\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 balanced division of labor.\n\n Visual explanation to depict:\n three-mode operating model with deterministic automation, AI reasoning, and human judgment each occupying the right zone\n\n Layout requirements:\n three-column or triangular operating 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 Deterministic where possible.\nAI where ambiguity exists.\nHuman where judgment matters.\nUse each mode where it is strongest.\n\n Extra art direction:\n Balanced, precise, and teachable.\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": "EARA-10", "title": "The path should be staged — prove the review brain before scaling the runtime.", "narrative_role": "roadmap", "objective": "Show a prudent staged path forward.", "visible_text": [ "The path should be staged — prove the review brain before scaling the runtime.", "Stage 1: curate source authority", "Stage 2: prove review logic", "Stage 3: scale runtime and experience" ], "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 a prudent staged path forward.\n\n Visual explanation to depict:\n staged progression from source curation to review-brain proof to runtime scaling\n\n Layout requirements:\n three-stage roadmap with increasing sophistication\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 The path should be staged — prove the review brain before scaling the runtime.\nStage 1: curate source authority\nStage 2: prove review logic\nStage 3: scale runtime and experience\n\n Extra art direction:\n Make the sequencing feel rational and disciplined.\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 a prudent staged path forward.\n\n Visual explanation to depict:\n staged progression from source curation to review-brain proof to runtime scaling\n\n Layout requirements:\n three-stage roadmap with increasing sophistication\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 The path should be staged — prove the review brain before scaling the runtime.\nStage 1: curate source authority\nStage 2: prove review logic\nStage 3: scale runtime and experience\n\n Extra art direction:\n Make the sequencing feel rational and disciplined.\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": "EARA-11", "title": "Outsource the wiring. Do not outsource the review judgment.", "narrative_role": "sourcing strategy", "objective": "Differentiate implementation support from judgment ownership.", "visible_text": [ "Outsource the wiring. Do not outsource the review judgment.", "Implementation wiring can be externalized.", "Architecture judgment, criteria, and source authority remain enterprise-owned." ], "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 Differentiate implementation support from judgment ownership.\n\n Visual explanation to depict:\n clear boundary between commodity wiring and enterprise-owned review judgment\n\n Layout requirements:\n two-zone ownership 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 Outsource the wiring. Do not outsource the review judgment.\nImplementation wiring can be externalized.\nArchitecture judgment, criteria, and source authority remain enterprise-owned.\n\n Extra art direction:\n Make ownership and boundaries crisp.\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 Differentiate implementation support from judgment ownership.\n\n Visual explanation to depict:\n clear boundary between commodity wiring and enterprise-owned review judgment\n\n Layout requirements:\n two-zone ownership 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 Outsource the wiring. Do not outsource the review judgment.\nImplementation wiring can be externalized.\nArchitecture judgment, criteria, and source authority remain enterprise-owned.\n\n Extra art direction:\n Make ownership and boundaries crisp.\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": "EARA-12", "title": "A modest alpha still needs real roles.", "narrative_role": "operating model", "objective": "Show that even a small alpha requires defined ownership.", "visible_text": [ "A modest alpha still needs real roles.", "Sponsor", "Capability owner", "Source stewards", "Reviewers", "Builders", "Operators" ], "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 that even a small alpha requires defined ownership.\n\n Visual explanation to depict:\n role map around the capability showing necessary operating roles and their relationship to the system\n\n Layout requirements:\n role ring or connected role 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 A modest alpha still needs real roles.\nSponsor\nCapability owner\nSource stewards\nReviewers\nBuilders\nOperators\n\n Extra art direction:\n Clean role architecture, not a messy org chart.\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 that even a small alpha requires defined ownership.\n\n Visual explanation to depict:\n role map around the capability showing necessary operating roles and their relationship to the system\n\n Layout requirements:\n role ring or connected role 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 A modest alpha still needs real roles.\nSponsor\nCapability owner\nSource stewards\nReviewers\nBuilders\nOperators\n\n Extra art direction:\n Clean role architecture, not a messy org chart.\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": "EARA-13", "title": "The package is ready for controlled build preparation — not broad pilot or production.", "narrative_role": "status statement", "objective": "State the current maturity without overclaiming.", "visible_text": [ "The package is ready for controlled build preparation — not broad pilot or production.", "Proceed with controlled prep.", "Do not oversell maturity.", "Focus on evidence, scope, 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 State the current maturity without overclaiming.\n\n Visual explanation to depict:\n maturity marker or staged-readiness graphic clearly highlighting the current state\n\n Layout requirements:\n readiness-stage slide with a highlighted current position\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 The package is ready for controlled build preparation — not broad pilot or production.\nProceed with controlled prep.\nDo not oversell maturity.\nFocus on evidence, scope, and validation.\n\n Extra art direction:\n Confident but disciplined.\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 State the current maturity without overclaiming.\n\n Visual explanation to depict:\n maturity marker or staged-readiness graphic clearly highlighting the current state\n\n Layout requirements:\n readiness-stage slide with a highlighted current position\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 The package is ready for controlled build preparation — not broad pilot or production.\nProceed with controlled prep.\nDo not oversell maturity.\nFocus on evidence, scope, and validation.\n\n Extra art direction:\n Confident but disciplined.\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": "EARA-14", "title": "Sponsor the review brain before funding the shiny interface.", "narrative_role": "closing leadership ask", "objective": "Close on a resource-allocation message.", "visible_text": [ "Sponsor the review brain before funding the shiny interface.", "Prioritize source authority.", "Codify decision logic.", "Prove the evidence loop.", "Then scale the experience layer." ], "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 on a resource-allocation message.\n\n Visual explanation to depict:\n resource-allocation hierarchy or investment stack placing the review brain beneath the experience layer\n\n Layout requirements:\n closing call-to-action with four investment priorities\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 Sponsor the review brain before funding the shiny interface.\nPrioritize source authority.\nCodify decision logic.\nProve the evidence loop.\nThen scale the experience layer.\n\n Extra art direction:\n Executive 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 Close on a resource-allocation message.\n\n Visual explanation to depict:\n resource-allocation hierarchy or investment stack placing the review brain beneath the experience layer\n\n Layout requirements:\n closing call-to-action with four investment priorities\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 Sponsor the review brain before funding the shiny interface.\nPrioritize source authority.\nCodify decision logic.\nProve the evidence loop.\nThen scale the experience layer.\n\n Extra art direction:\n Executive 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" } ] }, { "package_name": "MLL WESS Development Commitment and Build-Readiness Framework", "source_package_version": "v0.4.2 / v0.5 family-position candidate", "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": "WESS-01", "title": "This is not idea intake. It is commitment governance.", "narrative_role": "opening thesis", "objective": "Clarify the purpose of the framework from the start.", "visible_text": [ "This is not idea intake. It is commitment governance.", "A commitment model for scarce team capacity.", "Not every promising idea deserves immediate build commitment." ], "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 Clarify the purpose of the framework from the start.\n\n Visual explanation to depict:\n distinguish a wide funnel of ideas from a narrower, governed commitment gate tied to scarce capacity\n\n Layout requirements:\n hero opener with a visible narrowing from ideas to governed commitments\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 This is not idea intake. It is commitment governance.\nA commitment model for scarce team capacity.\nNot every promising idea deserves immediate build commitment.\n\n Extra art direction:\n Clean and decisive. Make the capacity constraint real.\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 Clarify the purpose of the framework from the start.\n\n Visual explanation to depict:\n distinguish a wide funnel of ideas from a narrower, governed commitment gate tied to scarce capacity\n\n Layout requirements:\n hero opener with a visible narrowing from ideas to governed commitments\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 This is not idea intake. It is commitment governance.\nA commitment model for scarce team capacity.\nNot every promising idea deserves immediate build commitment.\n\n Extra art direction:\n Clean and decisive. Make the capacity constraint real.\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": "WESS-02", "title": "Scarce capacity is the real constraint.", "narrative_role": "problem framing", "objective": "Make the capacity problem and hidden cost of commitments visible.", "visible_text": [ "Scarce capacity is the real constraint.", "Build work consumes design, testing, documentation, support, and sustainment.", "Uncontrolled commitments create drag, risk, and unfinished obligations." ], "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 Make the capacity problem and hidden cost of commitments visible.\n\n Visual explanation to depict:\n capacity ledger or engineering bandwidth system showing build work consuming multiple forms of scarce capacity\n\n Layout requirements:\n capacity-based explainer with visible load against finite bandwidth\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 Scarce capacity is the real constraint.\nBuild work consumes design, testing, documentation, support, and sustainment.\nUncontrolled commitments create drag, risk, and unfinished obligations.\n\n Extra art direction:\n Operational and grounded.\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 Make the capacity problem and hidden cost of commitments visible.\n\n Visual explanation to depict:\n capacity ledger or engineering bandwidth system showing build work consuming multiple forms of scarce capacity\n\n Layout requirements:\n capacity-based explainer with visible load against finite bandwidth\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 Scarce capacity is the real constraint.\nBuild work consumes design, testing, documentation, support, and sustainment.\nUncontrolled commitments create drag, risk, and unfinished obligations.\n\n Extra art direction:\n Operational and grounded.\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": "WESS-03", "title": "Four lanes create proportional rigor.", "narrative_role": "framework overview", "objective": "Show the four-lane model and its logic.", "visible_text": [ "Four lanes create proportional rigor.", "Sandbox freely", "Feasibility-check quickly", "Preflight on commitment", "Operationalize responsibly" ], "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-lane model and its logic.\n\n Visual explanation to depict:\n four-lane framework map from light exploration to operationalized capability\n\n Layout requirements:\n horizontal lane model with rising rigor and commitment depth\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 Four lanes create proportional rigor.\nSandbox freely\nFeasibility-check quickly\nPreflight on commitment\nOperationalize responsibly\n\n Extra art direction:\n Strong lane identity, very teachable.\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-lane model and its logic.\n\n Visual explanation to depict:\n four-lane framework map from light exploration to operationalized capability\n\n Layout requirements:\n horizontal lane model with rising rigor and commitment depth\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 Four lanes create proportional rigor.\nSandbox freely\nFeasibility-check quickly\nPreflight on commitment\nOperationalize responsibly\n\n Extra art direction:\n Strong lane identity, very teachable.\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": "WESS-04", "title": "Sandbox freely.", "narrative_role": "lane detail", "objective": "Show the lowest-rigor lane and its value.", "visible_text": [ "Sandbox freely.", "Explore ideas quickly.", "Use low-risk experimentation.", "Do not confuse discovery with commitment." ], "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 lowest-rigor lane and its value.\n\n Visual explanation to depict:\n bounded experimentation zone with safe exploration and clear boundary to commitment work\n\n Layout requirements:\n single-lane explainer with a soft exploratory feel but explicit guardrails\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 Sandbox freely.\nExplore ideas quickly.\nUse low-risk experimentation.\nDo not confuse discovery with commitment.\n\n Extra art direction:\n Keep it energetic but bounded.\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 lowest-rigor lane and its value.\n\n Visual explanation to depict:\n bounded experimentation zone with safe exploration and clear boundary to commitment work\n\n Layout requirements:\n single-lane explainer with a soft exploratory feel but explicit guardrails\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 Sandbox freely.\nExplore ideas quickly.\nUse low-risk experimentation.\nDo not confuse discovery with commitment.\n\n Extra art direction:\n Keep it energetic but bounded.\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": "WESS-05", "title": "Feasibility-check quickly.", "narrative_role": "lane detail", "objective": "Explain the 4–16 hour feasibility check and why it exists.", "visible_text": [ "Feasibility-check quickly.", "4–16 hour time-box.", "Test whether the idea deserves deeper investment.", "Produce a grounded go, no-go, or reshape signal." ], "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 Explain the 4–16 hour feasibility check and why it exists.\n\n Visual explanation to depict:\n time-boxed feasibility diagnostic flow that quickly surfaces viability, blockers, and next-step decisions\n\n Layout requirements:\n time-box callout plus a compact decision flow\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 Feasibility-check quickly.\n4–16 hour time-box.\nTest whether the idea deserves deeper investment.\nProduce a grounded go, no-go, or reshape signal.\n\n Extra art direction:\n Fast, disciplined, and no-nonsense.\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 Explain the 4–16 hour feasibility check and why it exists.\n\n Visual explanation to depict:\n time-boxed feasibility diagnostic flow that quickly surfaces viability, blockers, and next-step decisions\n\n Layout requirements:\n time-box callout plus a compact decision flow\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 Feasibility-check quickly.\n4–16 hour time-box.\nTest whether the idea deserves deeper investment.\nProduce a grounded go, no-go, or reshape signal.\n\n Extra art direction:\n Fast, disciplined, and no-nonsense.\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": "WESS-06", "title": "Preflight on commitment.", "narrative_role": "lane detail", "objective": "Show preflight as the commitment gate.", "visible_text": [ "Preflight on commitment.", "Commitment requires source authority, scope clarity, and build-readiness evidence.", "Jira epic requires preflight ID or approved exception." ], "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 preflight as the commitment gate.\n\n Visual explanation to depict:\n preflight gate with required evidence packets passing through before commitment is approved\n\n Layout requirements:\n commitment gate diagram with required proof elements\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 Preflight on commitment.\nCommitment requires source authority, scope clarity, and build-readiness evidence.\nJira epic requires preflight ID or approved exception.\n\n Extra art direction:\n Make the gate feel firm but rational.\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 preflight as the commitment gate.\n\n Visual explanation to depict:\n preflight gate with required evidence packets passing through before commitment is approved\n\n Layout requirements:\n commitment gate diagram with required proof elements\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 Preflight on commitment.\nCommitment requires source authority, scope clarity, and build-readiness evidence.\nJira epic requires preflight ID or approved exception.\n\n Extra art direction:\n Make the gate feel firm but rational.\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": "WESS-07", "title": "Operationalize responsibly.", "narrative_role": "lane detail", "objective": "Show the shift from prototype or build to operating capability.", "visible_text": [ "Operationalize responsibly.", "Repo seed, controls, support model, telemetry, documentation, and handoff matter.", "A working prototype is not the same as an operating service 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 Show the shift from prototype or build to operating capability.\n\n Visual explanation to depict:\n prototype-to-operation transition with operating requirements visibly wrapping the capability\n\n Layout requirements:\n before/after or maturity-transition composition\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 Operationalize responsibly.\nRepo seed, controls, support model, telemetry, documentation, and handoff matter.\nA working prototype is not the same as an operating service capability.\n\n Extra art direction:\n Operational readiness should feel weighty and real.\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 shift from prototype or build to operating capability.\n\n Visual explanation to depict:\n prototype-to-operation transition with operating requirements visibly wrapping the capability\n\n Layout requirements:\n before/after or maturity-transition composition\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 Operationalize responsibly.\nRepo seed, controls, support model, telemetry, documentation, and handoff matter.\nA working prototype is not the same as an operating service capability.\n\n Extra art direction:\n Operational readiness should feel weighty and real.\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": "WESS-08", "title": "Copilot prototypes are not production capabilities.", "narrative_role": "boundary setting", "objective": "Separate discovery tooling from operationalized team capability.", "visible_text": [ "Copilot prototypes are not production capabilities.", "Discovery can start in lightweight surfaces.", "Operational use needs stronger controls, ownership, and sustainment." ], "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 Separate discovery tooling from operationalized team capability.\n\n Visual explanation to depict:\n two-surface comparison between lightweight prototype surfaces and controlled operational capability surfaces\n\n Layout requirements:\n two-zone comparison with escalation path\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 Copilot prototypes are not production capabilities.\nDiscovery can start in lightweight surfaces.\nOperational use needs stronger controls, ownership, and sustainment.\n\n Extra art direction:\n Subtle, not anti-tool. Just clear-eyed.\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 Separate discovery tooling from operationalized team capability.\n\n Visual explanation to depict:\n two-surface comparison between lightweight prototype surfaces and controlled operational capability surfaces\n\n Layout requirements:\n two-zone comparison with escalation path\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 Copilot prototypes are not production capabilities.\nDiscovery can start in lightweight surfaces.\nOperational use needs stronger controls, ownership, and sustainment.\n\n Extra art direction:\n Subtle, not anti-tool. Just clear-eyed.\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": "WESS-09", "title": "Source authority and evidence come before build.", "narrative_role": "governance principle", "objective": "Show why source discipline and evidence packages precede commitment.", "visible_text": [ "Source authority and evidence come before build.", "Approved sources", "Evidence states", "Decision clarity", "Non-inference discipline" ], "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 why source discipline and evidence packages precede commitment.\n\n Visual explanation to depict:\n source authority stack feeding an evidence package that enables a build decision\n\n Layout requirements:\n source-to-evidence-to-decision flow\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 Source authority and evidence come before build.\nApproved sources\nEvidence states\nDecision clarity\nNon-inference discipline\n\n Extra art direction:\n Rigorous and structured.\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 why source discipline and evidence packages precede commitment.\n\n Visual explanation to depict:\n source authority stack feeding an evidence package that enables a build decision\n\n Layout requirements:\n source-to-evidence-to-decision flow\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 Source authority and evidence come before build.\nApproved sources\nEvidence states\nDecision clarity\nNon-inference discipline\n\n Extra art direction:\n Rigorous and structured.\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": "WESS-10", "title": "Repo seed, handoff, and support are part of the build.", "narrative_role": "operational responsibility", "objective": "Make downstream obligations visible at build time.", "visible_text": [ "Repo seed, handoff, and support are part of the build.", "Build includes documentation, ownership, support boundaries, and sustainment artifacts.", "Unowned automation becomes hidden debt." ], "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 Make downstream obligations visible at build time.\n\n Visual explanation to depict:\n delivery package exploded view showing code, docs, ownership, support model, and handoff artifacts\n\n Layout requirements:\n artifact package diagram or exploded-view composition\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 Repo seed, handoff, and support are part of the build.\nBuild includes documentation, ownership, support boundaries, and sustainment artifacts.\nUnowned automation becomes hidden debt.\n\n Extra art direction:\n Make the hidden work tangible.\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 Make downstream obligations visible at build time.\n\n Visual explanation to depict:\n delivery package exploded view showing code, docs, ownership, support model, and handoff artifacts\n\n Layout requirements:\n artifact package diagram or exploded-view composition\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 Repo seed, handoff, and support are part of the build.\nBuild includes documentation, ownership, support boundaries, and sustainment artifacts.\nUnowned automation becomes hidden debt.\n\n Extra art direction:\n Make the hidden work tangible.\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": "WESS-11", "title": "Start with a soft gate. Then harden.", "narrative_role": "adoption strategy", "objective": "Explain the soft-gate to hard-gate adoption path.", "visible_text": [ "Start with a soft gate. Then harden.", "30-day soft gate", "Amnesty-style review for existing work", "Move to hard gate once the team can operate it cleanly" ], "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 Explain the soft-gate to hard-gate adoption path.\n\n Visual explanation to depict:\n phased adoption timeline from soft gate to hard gate with existing work review path\n\n Layout requirements:\n timeline or phased transition 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 Start with a soft gate. Then harden.\n30-day soft gate\nAmnesty-style review for existing work\nMove to hard gate once the team can operate it cleanly\n\n Extra art direction:\n Show pragmatism instead of bureaucratic theater.\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 Explain the soft-gate to hard-gate adoption path.\n\n Visual explanation to depict:\n phased adoption timeline from soft gate to hard gate with existing work review path\n\n Layout requirements:\n timeline or phased transition 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 Start with a soft gate. Then harden.\n30-day soft gate\nAmnesty-style review for existing work\nMove to hard gate once the team can operate it cleanly\n\n Extra art direction:\n Show pragmatism instead of bureaucratic theater.\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": "WESS-12", "title": "Leadership ask: protect scarce engineering capacity.", "narrative_role": "closing leadership ask", "objective": "Close with the leadership behavior required to make the framework real.", "visible_text": [ "Leadership ask: protect scarce engineering capacity.", "Require proportional rigor.", "Block uncontrolled commitments.", "Use preflight before build.", "Fund sustainment, not just prototypes." ], "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 with the leadership behavior required to make the framework real.\n\n Visual explanation to depict:\n leadership commitment slide with four disciplined management commitments around a protected capacity core\n\n Layout requirements:\n closing call-to-action with a central leadership mandate and four commitment 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 ask: protect scarce engineering capacity.\nRequire proportional rigor.\nBlock uncontrolled commitments.\nUse preflight before build.\nFund sustainment, not just prototypes.\n\n Extra art direction:\n Strong and managerial.\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 with the leadership behavior required to make the framework real.\n\n Visual explanation to depict:\n leadership commitment slide with four disciplined management commitments around a protected capacity core\n\n Layout requirements:\n closing call-to-action with a central leadership mandate and four commitment 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 ask: protect scarce engineering capacity.\nRequire proportional rigor.\nBlock uncontrolled commitments.\nUse preflight before build.\nFund sustainment, not just prototypes.\n\n Extra art direction:\n Strong and managerial.\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" } ] }, { "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" } ] } ] }