# AI Capability Discipline Visual Prompt Deck Duo v1.1 Source package version: **v0.9** Correction: White prompts now use **Mainline White — Structured Expressive** with a true pure-white field. They are intentionally more visually expressive than a safe template, but still boardroom credible. ## White prompt family Use Mainline White — Structured Expressive. The 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. This 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. Visual system: - pure white background only - bold red headline in #EB1700 or black headline with selective #EB1700 emphasis - black body text - neutral gray structure and dividers - flat white cards with thin neutral-gray borders - stronger internal hierarchy inside the most important cards - slightly abstract explanatory diagrams - integrated note cards and editorial bands - medium density, not sparse - moderate panelization, not over-boxed - elevated editorial rhythm with varied card scale and visual pacing - medium-high contrast emphasis - medium-high connector emphasis only where it explains the story - selective red accents where they improve emphasis, rhythm, or conceptual contrast - moderate asymmetry and right-side emphasis when the newer, stronger, or more important idea belongs there - strong semantic coupling between nearby text and supporting visual elements - strict clean-footer behavior without visible reserve markers White-mode visual posture: - graphically impressive - structured expressive - boardroom-safe - meaning-first - visually memorable without chaos - less conservative than a plain consulting template - never decorative for its own sake ## Dark prompt family Use Dark Expressive Editorial. The 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. This dark branch may be more cinematic and keynote-style than the white branch, but it must remain explanatory, premium, legible, and enterprise credible. Dark-mode visual posture: - forceful but not chaotic - more atmospheric than white - stronger contrast between unstable and governed states - no neon overload - no glossy control-room UI - no cyberpunk wallpaper - no detached spectacle - no fake dashboards - no random energy ribbons without meaning - no product-board drift unless the slide is explicitly about product architecture ## Renderer usage note Use one slide prompt at a time. For renderers with weak text fidelity, generate the visual structure first and add final exact text downstream in PowerPoint, Canva, Figma, or another layout tool. Yes, the machines still occasionally treat typography like a haunted Ouija board. ## AICD-01 - 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 corpus ```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-field Mainline White render prompt ```text Create a sharp 16:9 editorial explainer slide. Use Mainline White — Structured Expressive. The 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. This 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. Visual system: - pure white background only - bold red headline in #EB1700 or black headline with selective #EB1700 emphasis - black body text - neutral gray structure and dividers - flat white cards with thin neutral-gray borders - stronger internal hierarchy inside the most important cards - slightly abstract explanatory diagrams - integrated note cards and editorial bands - medium density, not sparse - moderate panelization, not over-boxed - elevated editorial rhythm with varied card scale and visual pacing - medium-high contrast emphasis - medium-high connector emphasis only where it explains the story - selective red accents where they improve emphasis, rhythm, or conceptual contrast - moderate asymmetry and right-side emphasis when the newer, stronger, or more important idea belongs there - strong semantic coupling between nearby text and supporting visual elements - strict clean-footer behavior without visible reserve markers White-mode visual posture: - graphically impressive - structured expressive - boardroom-safe - meaning-first - visually memorable without chaos - less conservative than a plain consulting template - never decorative for its own sake Narrative objective: Reset the reader away from prompt hype and toward the full capability stack. Visual explanation to depict: scattered components on the left converging into a disciplined capability engine and outcome on the right, with governance and operations wrapping the system Layout requirements: hero opener with a bold title block, central transformation graphic, and compact evidence/status footer Composition rules: - anchor the title close to the top edge with minimal empty space above it - keep title and subtitle compactly stacked in a tight top title zone - use one dominant explanatory architecture across the middle - vary card sizes and visual weight based on conceptual importance - use integrated note cards attached directly to the regions they explain - use slightly abstract diagrams, hinge shapes, control bands, routing paths, or lifecycle flows only when they clarify the meaning - avoid equal-weight box grids unless the story truly requires equality - make the most important concept visually dominant - preserve clean margins and a clean footer without showing any reserve-space marker - use white space actively, but do not make the slide timid or visually empty Visible text discipline: All 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. 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 Extra art direction: Make the before-state feel fragmented and seductive, and the after-state coherent, governed, and operational. Avoid: 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. Priority order: 1. exact visible text fidelity 2. thesis clarity and teaching story 3. Mainline White or Dark Expressive family discipline 4. semantic coupling between text and graphic structure 5. premium enterprise credibility 6. visual impressiveness without clutter ``` ### Dark-field expressive render prompt ```text Create a sharp 16:9 dark-mode editorial explainer slide. Use Dark Expressive Editorial. The 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. This dark branch may be more cinematic and keynote-style than the white branch, but it must remain explanatory, premium, legible, and enterprise credible. Dark-mode visual posture: - forceful but not chaotic - more atmospheric than white - stronger contrast between unstable and governed states - no neon overload - no glossy control-room UI - no cyberpunk wallpaper - no detached spectacle - no fake dashboards - no random energy ribbons without meaning - no product-board drift unless the slide is explicitly about product architecture Narrative objective: Reset the reader away from prompt hype and toward the full capability stack. Visual explanation to depict: scattered components on the left converging into a disciplined capability engine and outcome on the right, with governance and operations wrapping the system Layout requirements: hero opener with a bold title block, central transformation graphic, and compact evidence/status footer Composition rules: - anchor the title close to the top edge with minimal dead space above it - preserve the same teaching story as the white version - create stronger contrast between unstable, naive, fragmented, or risky regions and governed, structured, reliable regions - use a visually memorable central architecture, transformation path, control-plane flow, or lifecycle structure - make the most important concept visually dominant - allow more atmosphere, glow, depth, and motion than the white version only where it improves explanation - keep text readable from a screen-share distance - keep the slide premium and controlled, not chaotic Visible text discipline: All 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. 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 Extra art direction: Make the before-state feel fragmented and seductive, and the after-state coherent, governed, and operational. Avoid: 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. Priority order: 1. exact visible text fidelity 2. thesis clarity and teaching story 3. Dark Expressive family discipline 4. semantic coupling between text and graphic structure 5. premium enterprise credibility 6. visual impressiveness without clutter ``` ## AICD-02 - 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 corpus ```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-field Mainline White render prompt ```text Create a sharp 16:9 editorial explainer slide. Use Mainline White — Structured Expressive. The 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. This 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. Visual system: - pure white background only - bold red headline in #EB1700 or black headline with selective #EB1700 emphasis - black body text - neutral gray structure and dividers - flat white cards with thin neutral-gray borders - stronger internal hierarchy inside the most important cards - slightly abstract explanatory diagrams - integrated note cards and editorial bands - medium density, not sparse - moderate panelization, not over-boxed - elevated editorial rhythm with varied card scale and visual pacing - medium-high contrast emphasis - medium-high connector emphasis only where it explains the story - selective red accents where they improve emphasis, rhythm, or conceptual contrast - moderate asymmetry and right-side emphasis when the newer, stronger, or more important idea belongs there - strong semantic coupling between nearby text and supporting visual elements - strict clean-footer behavior without visible reserve markers White-mode visual posture: - graphically impressive - structured expressive - boardroom-safe - meaning-first - visually memorable without chaos - less conservative than a plain consulting template - never decorative for its own sake Narrative objective: Show that the model is only one part of the system. Visual explanation to depict: layered system diagram with a model as one component inside a larger engineered operating system made of context, controls, evals, review, and maintenance Layout requirements: three-tier or concentric-layer explainer with the model visibly smaller than the surrounding system layers Composition rules: - anchor the title close to the top edge with minimal empty space above it - keep title and subtitle compactly stacked in a tight top title zone - use one dominant explanatory architecture across the middle - vary card sizes and visual weight based on conceptual importance - use integrated note cards attached directly to the regions they explain - use slightly abstract diagrams, hinge shapes, control bands, routing paths, or lifecycle flows only when they clarify the meaning - avoid equal-weight box grids unless the story truly requires equality - make the most important concept visually dominant - preserve clean margins and a clean footer without showing any reserve-space marker - use white space actively, but do not make the slide timid or visually empty Visible text discipline: All 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. 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. Extra art direction: Avoid mystical AI imagery. Make it feel like serious systems engineering. Avoid: 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. Priority order: 1. exact visible text fidelity 2. thesis clarity and teaching story 3. Mainline White or Dark Expressive family discipline 4. semantic coupling between text and graphic structure 5. premium enterprise credibility 6. visual impressiveness without clutter ``` ### Dark-field expressive render prompt ```text Create a sharp 16:9 dark-mode editorial explainer slide. Use Dark Expressive Editorial. The 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. This dark branch may be more cinematic and keynote-style than the white branch, but it must remain explanatory, premium, legible, and enterprise credible. Dark-mode visual posture: - forceful but not chaotic - more atmospheric than white - stronger contrast between unstable and governed states - no neon overload - no glossy control-room UI - no cyberpunk wallpaper - no detached spectacle - no fake dashboards - no random energy ribbons without meaning - no product-board drift unless the slide is explicitly about product architecture Narrative objective: Show that the model is only one part of the system. Visual explanation to depict: layered system diagram with a model as one component inside a larger engineered operating system made of context, controls, evals, review, and maintenance Layout requirements: three-tier or concentric-layer explainer with the model visibly smaller than the surrounding system layers Composition rules: - anchor the title close to the top edge with minimal dead space above it - preserve the same teaching story as the white version - create stronger contrast between unstable, naive, fragmented, or risky regions and governed, structured, reliable regions - use a visually memorable central architecture, transformation path, control-plane flow, or lifecycle structure - make the most important concept visually dominant - allow more atmosphere, glow, depth, and motion than the white version only where it improves explanation - keep text readable from a screen-share distance - keep the slide premium and controlled, not chaotic Visible text discipline: All 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. 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. Extra art direction: Avoid mystical AI imagery. Make it feel like serious systems engineering. Avoid: 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. Priority order: 1. exact visible text fidelity 2. thesis clarity and teaching story 3. Dark Expressive family discipline 4. semantic coupling between text and graphic structure 5. premium enterprise credibility 6. visual impressiveness without clutter ``` ## AICD-03 - Components Are Not Capabilities. **Narrative role:** decomposition **Objective:** Distinguish between ingredients and an actual operational capability. ### Visible text corpus ```text Components Are Not Capabilities. Prompt Agent Tool Skill Eval Useful ingredients do not equal a reliable capability. ``` ### White-field Mainline White render prompt ```text Create a sharp 16:9 editorial explainer slide. Use Mainline White — Structured Expressive. The 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. This 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. Visual system: - pure white background only - bold red headline in #EB1700 or black headline with selective #EB1700 emphasis - black body text - neutral gray structure and dividers - flat white cards with thin neutral-gray borders - stronger internal hierarchy inside the most important cards - slightly abstract explanatory diagrams - integrated note cards and editorial bands - medium density, not sparse - moderate panelization, not over-boxed - elevated editorial rhythm with varied card scale and visual pacing - medium-high contrast emphasis - medium-high connector emphasis only where it explains the story - selective red accents where they improve emphasis, rhythm, or conceptual contrast - moderate asymmetry and right-side emphasis when the newer, stronger, or more important idea belongs there - strong semantic coupling between nearby text and supporting visual elements - strict clean-footer behavior without visible reserve markers White-mode visual posture: - graphically impressive - structured expressive - boardroom-safe - meaning-first - visually memorable without chaos - less conservative than a plain consulting template - never decorative for its own sake Narrative objective: Distinguish between ingredients and an actual operational capability. Visual explanation to depict: ingredient tiles or modules feeding into a separate assembled capability block with an explicit gap between parts and operating capability Layout requirements: modular comparison layout with a left panel of components and a right panel showing assembled capability criteria Composition rules: - anchor the title close to the top edge with minimal empty space above it - keep title and subtitle compactly stacked in a tight top title zone - use one dominant explanatory architecture across the middle - vary card sizes and visual weight based on conceptual importance - use integrated note cards attached directly to the regions they explain - use slightly abstract diagrams, hinge shapes, control bands, routing paths, or lifecycle flows only when they clarify the meaning - avoid equal-weight box grids unless the story truly requires equality - make the most important concept visually dominant - preserve clean margins and a clean footer without showing any reserve-space marker - use white space actively, but do not make the slide timid or visually empty Visible text discipline: All 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. Visible text: Components Are Not Capabilities. Prompt Agent Tool Skill Eval Useful ingredients do not equal a reliable capability. Extra art direction: Use crisp object cards and a clear assembly narrative. Avoid: 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. Priority order: 1. exact visible text fidelity 2. thesis clarity and teaching story 3. Mainline White or Dark Expressive family discipline 4. semantic coupling between text and graphic structure 5. premium enterprise credibility 6. visual impressiveness without clutter ``` ### Dark-field expressive render prompt ```text Create a sharp 16:9 dark-mode editorial explainer slide. Use Dark Expressive Editorial. The 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. This dark branch may be more cinematic and keynote-style than the white branch, but it must remain explanatory, premium, legible, and enterprise credible. Dark-mode visual posture: - forceful but not chaotic - more atmospheric than white - stronger contrast between unstable and governed states - no neon overload - no glossy control-room UI - no cyberpunk wallpaper - no detached spectacle - no fake dashboards - no random energy ribbons without meaning - no product-board drift unless the slide is explicitly about product architecture Narrative objective: Distinguish between ingredients and an actual operational capability. Visual explanation to depict: ingredient tiles or modules feeding into a separate assembled capability block with an explicit gap between parts and operating capability Layout requirements: modular comparison layout with a left panel of components and a right panel showing assembled capability criteria Composition rules: - anchor the title close to the top edge with minimal dead space above it - preserve the same teaching story as the white version - create stronger contrast between unstable, naive, fragmented, or risky regions and governed, structured, reliable regions - use a visually memorable central architecture, transformation path, control-plane flow, or lifecycle structure - make the most important concept visually dominant - allow more atmosphere, glow, depth, and motion than the white version only where it improves explanation - keep text readable from a screen-share distance - keep the slide premium and controlled, not chaotic Visible text discipline: All 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. Visible text: Components Are Not Capabilities. Prompt Agent Tool Skill Eval Useful ingredients do not equal a reliable capability. Extra art direction: Use crisp object cards and a clear assembly narrative. Avoid: 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. Priority order: 1. exact visible text fidelity 2. thesis clarity and teaching story 3. Dark Expressive family discipline 4. semantic coupling between text and graphic structure 5. premium enterprise credibility 6. visual impressiveness without clutter ``` ## AICD-04 - The Capability Equation **Narrative role:** core framework **Objective:** Make the full capability equation memorable and teachable. ### Visible text corpus ```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-field Mainline White render prompt ```text Create a sharp 16:9 editorial explainer slide. Use Mainline White — Structured Expressive. The 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. This 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. Visual system: - pure white background only - bold red headline in #EB1700 or black headline with selective #EB1700 emphasis - black body text - neutral gray structure and dividers - flat white cards with thin neutral-gray borders - stronger internal hierarchy inside the most important cards - slightly abstract explanatory diagrams - integrated note cards and editorial bands - medium density, not sparse - moderate panelization, not over-boxed - elevated editorial rhythm with varied card scale and visual pacing - medium-high contrast emphasis - medium-high connector emphasis only where it explains the story - selective red accents where they improve emphasis, rhythm, or conceptual contrast - moderate asymmetry and right-side emphasis when the newer, stronger, or more important idea belongs there - strong semantic coupling between nearby text and supporting visual elements - strict clean-footer behavior without visible reserve markers White-mode visual posture: - graphically impressive - structured expressive - boardroom-safe - meaning-first - visually memorable without chaos - less conservative than a plain consulting template - never decorative for its own sake Narrative objective: Make the full capability equation memorable and teachable. Visual explanation to depict: a high-end equation slide with each term represented as a structured token or module, joined into one coherent capability expression Layout requirements: equation-centric composition with supporting iconless modules and a short warning callout Composition rules: - anchor the title close to the top edge with minimal empty space above it - keep title and subtitle compactly stacked in a tight top title zone - use one dominant explanatory architecture across the middle - vary card sizes and visual weight based on conceptual importance - use integrated note cards attached directly to the regions they explain - use slightly abstract diagrams, hinge shapes, control bands, routing paths, or lifecycle flows only when they clarify the meaning - avoid equal-weight box grids unless the story truly requires equality - make the most important concept visually dominant - preserve clean margins and a clean footer without showing any reserve-space marker - use white space actively, but do not make the slide timid or visually empty Visible text discipline: All 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. 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. Extra art direction: This should feel iconic and memorable, almost like a flagship framework slide. Avoid: 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. Priority order: 1. exact visible text fidelity 2. thesis clarity and teaching story 3. Mainline White or Dark Expressive family discipline 4. semantic coupling between text and graphic structure 5. premium enterprise credibility 6. visual impressiveness without clutter ``` ### Dark-field expressive render prompt ```text Create a sharp 16:9 dark-mode editorial explainer slide. Use Dark Expressive Editorial. The 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. This dark branch may be more cinematic and keynote-style than the white branch, but it must remain explanatory, premium, legible, and enterprise credible. Dark-mode visual posture: - forceful but not chaotic - more atmospheric than white - stronger contrast between unstable and governed states - no neon overload - no glossy control-room UI - no cyberpunk wallpaper - no detached spectacle - no fake dashboards - no random energy ribbons without meaning - no product-board drift unless the slide is explicitly about product architecture Narrative objective: Make the full capability equation memorable and teachable. Visual explanation to depict: a high-end equation slide with each term represented as a structured token or module, joined into one coherent capability expression Layout requirements: equation-centric composition with supporting iconless modules and a short warning callout Composition rules: - anchor the title close to the top edge with minimal dead space above it - preserve the same teaching story as the white version - create stronger contrast between unstable, naive, fragmented, or risky regions and governed, structured, reliable regions - use a visually memorable central architecture, transformation path, control-plane flow, or lifecycle structure - make the most important concept visually dominant - allow more atmosphere, glow, depth, and motion than the white version only where it improves explanation - keep text readable from a screen-share distance - keep the slide premium and controlled, not chaotic Visible text discipline: All 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. 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. Extra art direction: This should feel iconic and memorable, almost like a flagship framework slide. Avoid: 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. Priority order: 1. exact visible text fidelity 2. thesis clarity and teaching story 3. Dark Expressive family discipline 4. semantic coupling between text and graphic structure 5. premium enterprise credibility 6. visual impressiveness without clutter ``` ## AICD-05 - Intent Comes Before Evals. **Narrative role:** evaluation logic **Objective:** Show that evaluation quality depends on an explicit intended task and decision frame. ### Visible text corpus ```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-field Mainline White render prompt ```text Create a sharp 16:9 editorial explainer slide. Use Mainline White — Structured Expressive. The 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. This 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. Visual system: - pure white background only - bold red headline in #EB1700 or black headline with selective #EB1700 emphasis - black body text - neutral gray structure and dividers - flat white cards with thin neutral-gray borders - stronger internal hierarchy inside the most important cards - slightly abstract explanatory diagrams - integrated note cards and editorial bands - medium density, not sparse - moderate panelization, not over-boxed - elevated editorial rhythm with varied card scale and visual pacing - medium-high contrast emphasis - medium-high connector emphasis only where it explains the story - selective red accents where they improve emphasis, rhythm, or conceptual contrast - moderate asymmetry and right-side emphasis when the newer, stronger, or more important idea belongs there - strong semantic coupling between nearby text and supporting visual elements - strict clean-footer behavior without visible reserve markers White-mode visual posture: - graphically impressive - structured expressive - boardroom-safe - meaning-first - visually memorable without chaos - less conservative than a plain consulting template - never decorative for its own sake Narrative objective: Show that evaluation quality depends on an explicit intended task and decision frame. Visual explanation to depict: flow from intended task definition to output contract to evaluation harness to decision, with a warning branch showing invalid evals when intent is fuzzy Layout requirements: left-to-right decision flow with a visible failure branch Composition rules: - anchor the title close to the top edge with minimal empty space above it - keep title and subtitle compactly stacked in a tight top title zone - use one dominant explanatory architecture across the middle - vary card sizes and visual weight based on conceptual importance - use integrated note cards attached directly to the regions they explain - use slightly abstract diagrams, hinge shapes, control bands, routing paths, or lifecycle flows only when they clarify the meaning - avoid equal-weight box grids unless the story truly requires equality - make the most important concept visually dominant - preserve clean margins and a clean footer without showing any reserve-space marker - use white space actively, but do not make the slide timid or visually empty Visible text discipline: All 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. 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. Extra art direction: Make the invalid-eval path visibly attractive but wrong. Avoid: 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. Priority order: 1. exact visible text fidelity 2. thesis clarity and teaching story 3. Mainline White or Dark Expressive family discipline 4. semantic coupling between text and graphic structure 5. premium enterprise credibility 6. visual impressiveness without clutter ``` ### Dark-field expressive render prompt ```text Create a sharp 16:9 dark-mode editorial explainer slide. Use Dark Expressive Editorial. The 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. This dark branch may be more cinematic and keynote-style than the white branch, but it must remain explanatory, premium, legible, and enterprise credible. Dark-mode visual posture: - forceful but not chaotic - more atmospheric than white - stronger contrast between unstable and governed states - no neon overload - no glossy control-room UI - no cyberpunk wallpaper - no detached spectacle - no fake dashboards - no random energy ribbons without meaning - no product-board drift unless the slide is explicitly about product architecture Narrative objective: Show that evaluation quality depends on an explicit intended task and decision frame. Visual explanation to depict: flow from intended task definition to output contract to evaluation harness to decision, with a warning branch showing invalid evals when intent is fuzzy Layout requirements: left-to-right decision flow with a visible failure branch Composition rules: - anchor the title close to the top edge with minimal dead space above it - preserve the same teaching story as the white version - create stronger contrast between unstable, naive, fragmented, or risky regions and governed, structured, reliable regions - use a visually memorable central architecture, transformation path, control-plane flow, or lifecycle structure - make the most important concept visually dominant - allow more atmosphere, glow, depth, and motion than the white version only where it improves explanation - keep text readable from a screen-share distance - keep the slide premium and controlled, not chaotic Visible text discipline: All 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. 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. Extra art direction: Make the invalid-eval path visibly attractive but wrong. Avoid: 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. Priority order: 1. exact visible text fidelity 2. thesis clarity and teaching story 3. Dark Expressive family discipline 4. semantic coupling between text and graphic structure 5. premium enterprise credibility 6. visual impressiveness without clutter ``` ## AICD-06 - Context Is the Control Plane. **Narrative role:** context and grounding **Objective:** Teach that context determines what the model can know and do. ### Visible text corpus ```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-field Mainline White render prompt ```text Create a sharp 16:9 editorial explainer slide. Use Mainline White — Structured Expressive. The 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. This 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. Visual system: - pure white background only - bold red headline in #EB1700 or black headline with selective #EB1700 emphasis - black body text - neutral gray structure and dividers - flat white cards with thin neutral-gray borders - stronger internal hierarchy inside the most important cards - slightly abstract explanatory diagrams - integrated note cards and editorial bands - medium density, not sparse - moderate panelization, not over-boxed - elevated editorial rhythm with varied card scale and visual pacing - medium-high contrast emphasis - medium-high connector emphasis only where it explains the story - selective red accents where they improve emphasis, rhythm, or conceptual contrast - moderate asymmetry and right-side emphasis when the newer, stronger, or more important idea belongs there - strong semantic coupling between nearby text and supporting visual elements - strict clean-footer behavior without visible reserve markers White-mode visual posture: - graphically impressive - structured expressive - boardroom-safe - meaning-first - visually memorable without chaos - less conservative than a plain consulting template - never decorative for its own sake Narrative objective: Teach that context determines what the model can know and do. Visual explanation to depict: control-plane diagram where context packets, source tiers, and instructions govern model behavior and downstream outputs Layout requirements: central control-plane graphic with source layers and controlled output paths Composition rules: - anchor the title close to the top edge with minimal empty space above it - keep title and subtitle compactly stacked in a tight top title zone - use one dominant explanatory architecture across the middle - vary card sizes and visual weight based on conceptual importance - use integrated note cards attached directly to the regions they explain - use slightly abstract diagrams, hinge shapes, control bands, routing paths, or lifecycle flows only when they clarify the meaning - avoid equal-weight box grids unless the story truly requires equality - make the most important concept visually dominant - preserve clean margins and a clean footer without showing any reserve-space marker - use white space actively, but do not make the slide timid or visually empty Visible text discipline: All 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. 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. Extra art direction: Make context feel like the governing infrastructure, not extra flavor text. Avoid: 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. Priority order: 1. exact visible text fidelity 2. thesis clarity and teaching story 3. Mainline White or Dark Expressive family discipline 4. semantic coupling between text and graphic structure 5. premium enterprise credibility 6. visual impressiveness without clutter ``` ### Dark-field expressive render prompt ```text Create a sharp 16:9 dark-mode editorial explainer slide. Use Dark Expressive Editorial. The 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. This dark branch may be more cinematic and keynote-style than the white branch, but it must remain explanatory, premium, legible, and enterprise credible. Dark-mode visual posture: - forceful but not chaotic - more atmospheric than white - stronger contrast between unstable and governed states - no neon overload - no glossy control-room UI - no cyberpunk wallpaper - no detached spectacle - no fake dashboards - no random energy ribbons without meaning - no product-board drift unless the slide is explicitly about product architecture Narrative objective: Teach that context determines what the model can know and do. Visual explanation to depict: control-plane diagram where context packets, source tiers, and instructions govern model behavior and downstream outputs Layout requirements: central control-plane graphic with source layers and controlled output paths Composition rules: - anchor the title close to the top edge with minimal dead space above it - preserve the same teaching story as the white version - create stronger contrast between unstable, naive, fragmented, or risky regions and governed, structured, reliable regions - use a visually memorable central architecture, transformation path, control-plane flow, or lifecycle structure - make the most important concept visually dominant - allow more atmosphere, glow, depth, and motion than the white version only where it improves explanation - keep text readable from a screen-share distance - keep the slide premium and controlled, not chaotic Visible text discipline: All 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. 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. Extra art direction: Make context feel like the governing infrastructure, not extra flavor text. Avoid: 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. Priority order: 1. exact visible text fidelity 2. thesis clarity and teaching story 3. Dark Expressive family discipline 4. semantic coupling between text and graphic structure 5. premium enterprise credibility 6. visual impressiveness without clutter ``` ## AICD-07 - Schema-First Makes AI Inspectable. **Narrative role:** inspectability **Objective:** Show how schemas and output contracts make AI work governable. ### Visible text corpus ```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-field Mainline White render prompt ```text Create a sharp 16:9 editorial explainer slide. Use Mainline White — Structured Expressive. The 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. This 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. Visual system: - pure white background only - bold red headline in #EB1700 or black headline with selective #EB1700 emphasis - black body text - neutral gray structure and dividers - flat white cards with thin neutral-gray borders - stronger internal hierarchy inside the most important cards - slightly abstract explanatory diagrams - integrated note cards and editorial bands - medium density, not sparse - moderate panelization, not over-boxed - elevated editorial rhythm with varied card scale and visual pacing - medium-high contrast emphasis - medium-high connector emphasis only where it explains the story - selective red accents where they improve emphasis, rhythm, or conceptual contrast - moderate asymmetry and right-side emphasis when the newer, stronger, or more important idea belongs there - strong semantic coupling between nearby text and supporting visual elements - strict clean-footer behavior without visible reserve markers White-mode visual posture: - graphically impressive - structured expressive - boardroom-safe - meaning-first - visually memorable without chaos - less conservative than a plain consulting template - never decorative for its own sake Narrative objective: Show how schemas and output contracts make AI work governable. Visual explanation to depict: before-and-after comparison between messy prose output and structured schema-driven output that can be checked, scored, and routed Layout requirements: split-screen comparison with a quality uplift arrow or transformation bridge Composition rules: - anchor the title close to the top edge with minimal empty space above it - keep title and subtitle compactly stacked in a tight top title zone - use one dominant explanatory architecture across the middle - vary card sizes and visual weight based on conceptual importance - use integrated note cards attached directly to the regions they explain - use slightly abstract diagrams, hinge shapes, control bands, routing paths, or lifecycle flows only when they clarify the meaning - avoid equal-weight box grids unless the story truly requires equality - make the most important concept visually dominant - preserve clean margins and a clean footer without showing any reserve-space marker - use white space actively, but do not make the slide timid or visually empty Visible text discipline: All 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. 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. Extra art direction: Lean into clarity and reviewability. Avoid: 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. Priority order: 1. exact visible text fidelity 2. thesis clarity and teaching story 3. Mainline White or Dark Expressive family discipline 4. semantic coupling between text and graphic structure 5. premium enterprise credibility 6. visual impressiveness without clutter ``` ### Dark-field expressive render prompt ```text Create a sharp 16:9 dark-mode editorial explainer slide. Use Dark Expressive Editorial. The 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. This dark branch may be more cinematic and keynote-style than the white branch, but it must remain explanatory, premium, legible, and enterprise credible. Dark-mode visual posture: - forceful but not chaotic - more atmospheric than white - stronger contrast between unstable and governed states - no neon overload - no glossy control-room UI - no cyberpunk wallpaper - no detached spectacle - no fake dashboards - no random energy ribbons without meaning - no product-board drift unless the slide is explicitly about product architecture Narrative objective: Show how schemas and output contracts make AI work governable. Visual explanation to depict: before-and-after comparison between messy prose output and structured schema-driven output that can be checked, scored, and routed Layout requirements: split-screen comparison with a quality uplift arrow or transformation bridge Composition rules: - anchor the title close to the top edge with minimal dead space above it - preserve the same teaching story as the white version - create stronger contrast between unstable, naive, fragmented, or risky regions and governed, structured, reliable regions - use a visually memorable central architecture, transformation path, control-plane flow, or lifecycle structure - make the most important concept visually dominant - allow more atmosphere, glow, depth, and motion than the white version only where it improves explanation - keep text readable from a screen-share distance - keep the slide premium and controlled, not chaotic Visible text discipline: All 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. 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. Extra art direction: Lean into clarity and reviewability. Avoid: 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. Priority order: 1. exact visible text fidelity 2. thesis clarity and teaching story 3. Dark Expressive family discipline 4. semantic coupling between text and graphic structure 5. premium enterprise credibility 6. visual impressiveness without clutter ``` ## AICD-08 - Governance Starts With Routing. **Narrative role:** governance model **Objective:** Make governance feel like intelligent routing, not blanket obstruction. ### Visible text corpus ```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-field Mainline White render prompt ```text Create a sharp 16:9 editorial explainer slide. Use Mainline White — Structured Expressive. The 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. This 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. Visual system: - pure white background only - bold red headline in #EB1700 or black headline with selective #EB1700 emphasis - black body text - neutral gray structure and dividers - flat white cards with thin neutral-gray borders - stronger internal hierarchy inside the most important cards - slightly abstract explanatory diagrams - integrated note cards and editorial bands - medium density, not sparse - moderate panelization, not over-boxed - elevated editorial rhythm with varied card scale and visual pacing - medium-high contrast emphasis - medium-high connector emphasis only where it explains the story - selective red accents where they improve emphasis, rhythm, or conceptual contrast - moderate asymmetry and right-side emphasis when the newer, stronger, or more important idea belongs there - strong semantic coupling between nearby text and supporting visual elements - strict clean-footer behavior without visible reserve markers White-mode visual posture: - graphically impressive - structured expressive - boardroom-safe - meaning-first - visually memorable without chaos - less conservative than a plain consulting template - never decorative for its own sake Narrative objective: Make governance feel like intelligent routing, not blanket obstruction. Visual explanation to depict: lane-routing diagram or triage board moving proposals into different governance paths based on attributes Layout requirements: multi-lane routing board with clear decision triggers and proportional rigor Composition rules: - anchor the title close to the top edge with minimal empty space above it - keep title and subtitle compactly stacked in a tight top title zone - use one dominant explanatory architecture across the middle - vary card sizes and visual weight based on conceptual importance - use integrated note cards attached directly to the regions they explain - use slightly abstract diagrams, hinge shapes, control bands, routing paths, or lifecycle flows only when they clarify the meaning - avoid equal-weight box grids unless the story truly requires equality - make the most important concept visually dominant - preserve clean margins and a clean footer without showing any reserve-space marker - use white space actively, but do not make the slide timid or visually empty Visible text discipline: All 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. 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. Extra art direction: Make the lanes intelligible at a glance. Avoid: 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. Priority order: 1. exact visible text fidelity 2. thesis clarity and teaching story 3. Mainline White or Dark Expressive family discipline 4. semantic coupling between text and graphic structure 5. premium enterprise credibility 6. visual impressiveness without clutter ``` ### Dark-field expressive render prompt ```text Create a sharp 16:9 dark-mode editorial explainer slide. Use Dark Expressive Editorial. The 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. This dark branch may be more cinematic and keynote-style than the white branch, but it must remain explanatory, premium, legible, and enterprise credible. Dark-mode visual posture: - forceful but not chaotic - more atmospheric than white - stronger contrast between unstable and governed states - no neon overload - no glossy control-room UI - no cyberpunk wallpaper - no detached spectacle - no fake dashboards - no random energy ribbons without meaning - no product-board drift unless the slide is explicitly about product architecture Narrative objective: Make governance feel like intelligent routing, not blanket obstruction. Visual explanation to depict: lane-routing diagram or triage board moving proposals into different governance paths based on attributes Layout requirements: multi-lane routing board with clear decision triggers and proportional rigor Composition rules: - anchor the title close to the top edge with minimal dead space above it - preserve the same teaching story as the white version - create stronger contrast between unstable, naive, fragmented, or risky regions and governed, structured, reliable regions - use a visually memorable central architecture, transformation path, control-plane flow, or lifecycle structure - make the most important concept visually dominant - allow more atmosphere, glow, depth, and motion than the white version only where it improves explanation - keep text readable from a screen-share distance - keep the slide premium and controlled, not chaotic Visible text discipline: All 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. 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. Extra art direction: Make the lanes intelligible at a glance. Avoid: 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. Priority order: 1. exact visible text fidelity 2. thesis clarity and teaching story 3. Dark Expressive family discipline 4. semantic coupling between text and graphic structure 5. premium enterprise credibility 6. visual impressiveness without clutter ``` ## AICD-09 - External Learning Is Not Enterprise Execution. **Narrative role:** tool boundary **Objective:** Clarify the difference between learning tools and approved enterprise operating surfaces. ### Visible text corpus ```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-field Mainline White render prompt ```text Create a sharp 16:9 editorial explainer slide. Use Mainline White — Structured Expressive. The 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. This 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. Visual system: - pure white background only - bold red headline in #EB1700 or black headline with selective #EB1700 emphasis - black body text - neutral gray structure and dividers - flat white cards with thin neutral-gray borders - stronger internal hierarchy inside the most important cards - slightly abstract explanatory diagrams - integrated note cards and editorial bands - medium density, not sparse - moderate panelization, not over-boxed - elevated editorial rhythm with varied card scale and visual pacing - medium-high contrast emphasis - medium-high connector emphasis only where it explains the story - selective red accents where they improve emphasis, rhythm, or conceptual contrast - moderate asymmetry and right-side emphasis when the newer, stronger, or more important idea belongs there - strong semantic coupling between nearby text and supporting visual elements - strict clean-footer behavior without visible reserve markers White-mode visual posture: - graphically impressive - structured expressive - boardroom-safe - meaning-first - visually memorable without chaos - less conservative than a plain consulting template - never decorative for its own sake Narrative objective: Clarify the difference between learning tools and approved enterprise operating surfaces. Visual explanation to depict: two clearly separated zones, one for personal learning/synthetic data experimentation and one for approved enterprise execution with explicit governance barriers between them Layout requirements: two-column boundary diagram with a clear policy boundary and approval bridge Composition rules: - anchor the title close to the top edge with minimal empty space above it - keep title and subtitle compactly stacked in a tight top title zone - use one dominant explanatory architecture across the middle - vary card sizes and visual weight based on conceptual importance - use integrated note cards attached directly to the regions they explain - use slightly abstract diagrams, hinge shapes, control bands, routing paths, or lifecycle flows only when they clarify the meaning - avoid equal-weight box grids unless the story truly requires equality - make the most important concept visually dominant - preserve clean margins and a clean footer without showing any reserve-space marker - use white space actively, but do not make the slide timid or visually empty Visible text discipline: All 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. 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. Extra art direction: Board-safe, policy-literate, crisp. Avoid: 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. Priority order: 1. exact visible text fidelity 2. thesis clarity and teaching story 3. Mainline White or Dark Expressive family discipline 4. semantic coupling between text and graphic structure 5. premium enterprise credibility 6. visual impressiveness without clutter ``` ### Dark-field expressive render prompt ```text Create a sharp 16:9 dark-mode editorial explainer slide. Use Dark Expressive Editorial. The 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. This dark branch may be more cinematic and keynote-style than the white branch, but it must remain explanatory, premium, legible, and enterprise credible. Dark-mode visual posture: - forceful but not chaotic - more atmospheric than white - stronger contrast between unstable and governed states - no neon overload - no glossy control-room UI - no cyberpunk wallpaper - no detached spectacle - no fake dashboards - no random energy ribbons without meaning - no product-board drift unless the slide is explicitly about product architecture Narrative objective: Clarify the difference between learning tools and approved enterprise operating surfaces. Visual explanation to depict: two clearly separated zones, one for personal learning/synthetic data experimentation and one for approved enterprise execution with explicit governance barriers between them Layout requirements: two-column boundary diagram with a clear policy boundary and approval bridge Composition rules: - anchor the title close to the top edge with minimal dead space above it - preserve the same teaching story as the white version - create stronger contrast between unstable, naive, fragmented, or risky regions and governed, structured, reliable regions - use a visually memorable central architecture, transformation path, control-plane flow, or lifecycle structure - make the most important concept visually dominant - allow more atmosphere, glow, depth, and motion than the white version only where it improves explanation - keep text readable from a screen-share distance - keep the slide premium and controlled, not chaotic Visible text discipline: All 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. 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. Extra art direction: Board-safe, policy-literate, crisp. Avoid: 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. Priority order: 1. exact visible text fidelity 2. thesis clarity and teaching story 3. Dark Expressive family discipline 4. semantic coupling between text and graphic structure 5. premium enterprise credibility 6. visual impressiveness without clutter ``` ## AICD-10 - Harnesses Need Maintenance. **Narrative role:** lifecycle truth **Objective:** Show that prompts, evals, schemas, and source maps drift over time and require upkeep. ### Visible text corpus ```text Harnesses Need Maintenance. Prompts drift. Sources change. Schemas evolve. Evals stale out. A capability is maintained, not merely launched. ``` ### White-field Mainline White render prompt ```text Create a sharp 16:9 editorial explainer slide. Use Mainline White — Structured Expressive. The 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. This 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. Visual system: - pure white background only - bold red headline in #EB1700 or black headline with selective #EB1700 emphasis - black body text - neutral gray structure and dividers - flat white cards with thin neutral-gray borders - stronger internal hierarchy inside the most important cards - slightly abstract explanatory diagrams - integrated note cards and editorial bands - medium density, not sparse - moderate panelization, not over-boxed - elevated editorial rhythm with varied card scale and visual pacing - medium-high contrast emphasis - medium-high connector emphasis only where it explains the story - selective red accents where they improve emphasis, rhythm, or conceptual contrast - moderate asymmetry and right-side emphasis when the newer, stronger, or more important idea belongs there - strong semantic coupling between nearby text and supporting visual elements - strict clean-footer behavior without visible reserve markers White-mode visual posture: - graphically impressive - structured expressive - boardroom-safe - meaning-first - visually memorable without chaos - less conservative than a plain consulting template - never decorative for its own sake Narrative objective: Show that prompts, evals, schemas, and source maps drift over time and require upkeep. Visual explanation to depict: a maintenance loop or lifecycle ring around a capability, showing drift pressures and refresh activities Layout requirements: circular lifecycle or flywheel with maintenance checkpoints Composition rules: - anchor the title close to the top edge with minimal empty space above it - keep title and subtitle compactly stacked in a tight top title zone - use one dominant explanatory architecture across the middle - vary card sizes and visual weight based on conceptual importance - use integrated note cards attached directly to the regions they explain - use slightly abstract diagrams, hinge shapes, control bands, routing paths, or lifecycle flows only when they clarify the meaning - avoid equal-weight box grids unless the story truly requires equality - make the most important concept visually dominant - preserve clean margins and a clean footer without showing any reserve-space marker - use white space actively, but do not make the slide timid or visually empty Visible text discipline: All 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. Visible text: Harnesses Need Maintenance. Prompts drift. Sources change. Schemas evolve. Evals stale out. A capability is maintained, not merely launched. Extra art direction: Make the notion of slow drift tangible. Avoid: 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. Priority order: 1. exact visible text fidelity 2. thesis clarity and teaching story 3. Mainline White or Dark Expressive family discipline 4. semantic coupling between text and graphic structure 5. premium enterprise credibility 6. visual impressiveness without clutter ``` ### Dark-field expressive render prompt ```text Create a sharp 16:9 dark-mode editorial explainer slide. Use Dark Expressive Editorial. The 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. This dark branch may be more cinematic and keynote-style than the white branch, but it must remain explanatory, premium, legible, and enterprise credible. Dark-mode visual posture: - forceful but not chaotic - more atmospheric than white - stronger contrast between unstable and governed states - no neon overload - no glossy control-room UI - no cyberpunk wallpaper - no detached spectacle - no fake dashboards - no random energy ribbons without meaning - no product-board drift unless the slide is explicitly about product architecture Narrative objective: Show that prompts, evals, schemas, and source maps drift over time and require upkeep. Visual explanation to depict: a maintenance loop or lifecycle ring around a capability, showing drift pressures and refresh activities Layout requirements: circular lifecycle or flywheel with maintenance checkpoints Composition rules: - anchor the title close to the top edge with minimal dead space above it - preserve the same teaching story as the white version - create stronger contrast between unstable, naive, fragmented, or risky regions and governed, structured, reliable regions - use a visually memorable central architecture, transformation path, control-plane flow, or lifecycle structure - make the most important concept visually dominant - allow more atmosphere, glow, depth, and motion than the white version only where it improves explanation - keep text readable from a screen-share distance - keep the slide premium and controlled, not chaotic Visible text discipline: All 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. Visible text: Harnesses Need Maintenance. Prompts drift. Sources change. Schemas evolve. Evals stale out. A capability is maintained, not merely launched. Extra art direction: Make the notion of slow drift tangible. Avoid: 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. Priority order: 1. exact visible text fidelity 2. thesis clarity and teaching story 3. Dark Expressive family discipline 4. semantic coupling between text and graphic structure 5. premium enterprise credibility 6. visual impressiveness without clutter ``` ## AICD-11 - Tool Pruning Is a Control. **Narrative role:** agent/tool governance **Objective:** Show that more tools can make agents worse, not better. ### Visible text corpus ```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-field Mainline White render prompt ```text Create a sharp 16:9 editorial explainer slide. Use Mainline White — Structured Expressive. The 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. This 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. Visual system: - pure white background only - bold red headline in #EB1700 or black headline with selective #EB1700 emphasis - black body text - neutral gray structure and dividers - flat white cards with thin neutral-gray borders - stronger internal hierarchy inside the most important cards - slightly abstract explanatory diagrams - integrated note cards and editorial bands - medium density, not sparse - moderate panelization, not over-boxed - elevated editorial rhythm with varied card scale and visual pacing - medium-high contrast emphasis - medium-high connector emphasis only where it explains the story - selective red accents where they improve emphasis, rhythm, or conceptual contrast - moderate asymmetry and right-side emphasis when the newer, stronger, or more important idea belongs there - strong semantic coupling between nearby text and supporting visual elements - strict clean-footer behavior without visible reserve markers White-mode visual posture: - graphically impressive - structured expressive - boardroom-safe - meaning-first - visually memorable without chaos - less conservative than a plain consulting template - never decorative for its own sake Narrative objective: Show that more tools can make agents worse, not better. Visual explanation to depict: toolset reduction story showing a tangled tool cluster simplified into a smaller, more controlled and reliable tool surface Layout requirements: before-and-after tool surface comparison Composition rules: - anchor the title close to the top edge with minimal empty space above it - keep title and subtitle compactly stacked in a tight top title zone - use one dominant explanatory architecture across the middle - vary card sizes and visual weight based on conceptual importance - use integrated note cards attached directly to the regions they explain - use slightly abstract diagrams, hinge shapes, control bands, routing paths, or lifecycle flows only when they clarify the meaning - avoid equal-weight box grids unless the story truly requires equality - make the most important concept visually dominant - preserve clean margins and a clean footer without showing any reserve-space marker - use white space actively, but do not make the slide timid or visually empty Visible text discipline: All 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. 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. Extra art direction: Emphasize reduced complexity and stronger control. Avoid: 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. Priority order: 1. exact visible text fidelity 2. thesis clarity and teaching story 3. Mainline White or Dark Expressive family discipline 4. semantic coupling between text and graphic structure 5. premium enterprise credibility 6. visual impressiveness without clutter ``` ### Dark-field expressive render prompt ```text Create a sharp 16:9 dark-mode editorial explainer slide. Use Dark Expressive Editorial. The 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. This dark branch may be more cinematic and keynote-style than the white branch, but it must remain explanatory, premium, legible, and enterprise credible. Dark-mode visual posture: - forceful but not chaotic - more atmospheric than white - stronger contrast between unstable and governed states - no neon overload - no glossy control-room UI - no cyberpunk wallpaper - no detached spectacle - no fake dashboards - no random energy ribbons without meaning - no product-board drift unless the slide is explicitly about product architecture Narrative objective: Show that more tools can make agents worse, not better. Visual explanation to depict: toolset reduction story showing a tangled tool cluster simplified into a smaller, more controlled and reliable tool surface Layout requirements: before-and-after tool surface comparison Composition rules: - anchor the title close to the top edge with minimal dead space above it - preserve the same teaching story as the white version - create stronger contrast between unstable, naive, fragmented, or risky regions and governed, structured, reliable regions - use a visually memorable central architecture, transformation path, control-plane flow, or lifecycle structure - make the most important concept visually dominant - allow more atmosphere, glow, depth, and motion than the white version only where it improves explanation - keep text readable from a screen-share distance - keep the slide premium and controlled, not chaotic Visible text discipline: All 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. 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. Extra art direction: Emphasize reduced complexity and stronger control. Avoid: 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. Priority order: 1. exact visible text fidelity 2. thesis clarity and teaching story 3. Dark Expressive family discipline 4. semantic coupling between text and graphic structure 5. premium enterprise credibility 6. visual impressiveness without clutter ``` ## AICD-12 - Advisory Is Not Control Plane. **Narrative role:** document vs runtime distinction **Objective:** Differentiate guidance artifacts from runtime-enforcing systems. ### Visible text corpus ```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-field Mainline White render prompt ```text Create a sharp 16:9 editorial explainer slide. Use Mainline White — Structured Expressive. The 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. This 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. Visual system: - pure white background only - bold red headline in #EB1700 or black headline with selective #EB1700 emphasis - black body text - neutral gray structure and dividers - flat white cards with thin neutral-gray borders - stronger internal hierarchy inside the most important cards - slightly abstract explanatory diagrams - integrated note cards and editorial bands - medium density, not sparse - moderate panelization, not over-boxed - elevated editorial rhythm with varied card scale and visual pacing - medium-high contrast emphasis - medium-high connector emphasis only where it explains the story - selective red accents where they improve emphasis, rhythm, or conceptual contrast - moderate asymmetry and right-side emphasis when the newer, stronger, or more important idea belongs there - strong semantic coupling between nearby text and supporting visual elements - strict clean-footer behavior without visible reserve markers White-mode visual posture: - graphically impressive - structured expressive - boardroom-safe - meaning-first - visually memorable without chaos - less conservative than a plain consulting template - never decorative for its own sake Narrative objective: Differentiate guidance artifacts from runtime-enforcing systems. Visual explanation to depict: split diagram contrasting a static advisory document with a live runtime control plane that enforces behavior Layout requirements: side-by-side conceptual comparison with enforcement mechanisms visible on the runtime side Composition rules: - anchor the title close to the top edge with minimal empty space above it - keep title and subtitle compactly stacked in a tight top title zone - use one dominant explanatory architecture across the middle - vary card sizes and visual weight based on conceptual importance - use integrated note cards attached directly to the regions they explain - use slightly abstract diagrams, hinge shapes, control bands, routing paths, or lifecycle flows only when they clarify the meaning - avoid equal-weight box grids unless the story truly requires equality - make the most important concept visually dominant - preserve clean margins and a clean footer without showing any reserve-space marker - use white space actively, but do not make the slide timid or visually empty Visible text discipline: All 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. 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. Extra art direction: Respect both sides while making the distinction unmistakable. Avoid: 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. Priority order: 1. exact visible text fidelity 2. thesis clarity and teaching story 3. Mainline White or Dark Expressive family discipline 4. semantic coupling between text and graphic structure 5. premium enterprise credibility 6. visual impressiveness without clutter ``` ### Dark-field expressive render prompt ```text Create a sharp 16:9 dark-mode editorial explainer slide. Use Dark Expressive Editorial. The 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. This dark branch may be more cinematic and keynote-style than the white branch, but it must remain explanatory, premium, legible, and enterprise credible. Dark-mode visual posture: - forceful but not chaotic - more atmospheric than white - stronger contrast between unstable and governed states - no neon overload - no glossy control-room UI - no cyberpunk wallpaper - no detached spectacle - no fake dashboards - no random energy ribbons without meaning - no product-board drift unless the slide is explicitly about product architecture Narrative objective: Differentiate guidance artifacts from runtime-enforcing systems. Visual explanation to depict: split diagram contrasting a static advisory document with a live runtime control plane that enforces behavior Layout requirements: side-by-side conceptual comparison with enforcement mechanisms visible on the runtime side Composition rules: - anchor the title close to the top edge with minimal dead space above it - preserve the same teaching story as the white version - create stronger contrast between unstable, naive, fragmented, or risky regions and governed, structured, reliable regions - use a visually memorable central architecture, transformation path, control-plane flow, or lifecycle structure - make the most important concept visually dominant - allow more atmosphere, glow, depth, and motion than the white version only where it improves explanation - keep text readable from a screen-share distance - keep the slide premium and controlled, not chaotic Visible text discipline: All 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. 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. Extra art direction: Respect both sides while making the distinction unmistakable. Avoid: 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. Priority order: 1. exact visible text fidelity 2. thesis clarity and teaching story 3. Dark Expressive family discipline 4. semantic coupling between text and graphic structure 5. premium enterprise credibility 6. visual impressiveness without clutter ``` ## AICD-13 - Lifecycle Lens Shows the Pattern. **Narrative role:** applied synthesis **Objective:** Bring the full lifecycle together from idea to operation. ### Visible text corpus ```text Lifecycle Lens Shows the Pattern. Discover Design Validate Govern Operate Maintain The pattern repeats across real AI capability work. ``` ### White-field Mainline White render prompt ```text Create a sharp 16:9 editorial explainer slide. Use Mainline White — Structured Expressive. The 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. This 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. Visual system: - pure white background only - bold red headline in #EB1700 or black headline with selective #EB1700 emphasis - black body text - neutral gray structure and dividers - flat white cards with thin neutral-gray borders - stronger internal hierarchy inside the most important cards - slightly abstract explanatory diagrams - integrated note cards and editorial bands - medium density, not sparse - moderate panelization, not over-boxed - elevated editorial rhythm with varied card scale and visual pacing - medium-high contrast emphasis - medium-high connector emphasis only where it explains the story - selective red accents where they improve emphasis, rhythm, or conceptual contrast - moderate asymmetry and right-side emphasis when the newer, stronger, or more important idea belongs there - strong semantic coupling between nearby text and supporting visual elements - strict clean-footer behavior without visible reserve markers White-mode visual posture: - graphically impressive - structured expressive - boardroom-safe - meaning-first - visually memorable without chaos - less conservative than a plain consulting template - never decorative for its own sake Narrative objective: Bring the full lifecycle together from idea to operation. Visual explanation to depict: clean lifecycle map connecting discovery, design, validation, governance, operation, and maintenance Layout requirements: left-to-right staged lifecycle or circular lifecycle with six distinct stages Composition rules: - anchor the title close to the top edge with minimal empty space above it - keep title and subtitle compactly stacked in a tight top title zone - use one dominant explanatory architecture across the middle - vary card sizes and visual weight based on conceptual importance - use integrated note cards attached directly to the regions they explain - use slightly abstract diagrams, hinge shapes, control bands, routing paths, or lifecycle flows only when they clarify the meaning - avoid equal-weight box grids unless the story truly requires equality - make the most important concept visually dominant - preserve clean margins and a clean footer without showing any reserve-space marker - use white space actively, but do not make the slide timid or visually empty Visible text discipline: All 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. Visible text: Lifecycle Lens Shows the Pattern. Discover Design Validate Govern Operate Maintain The pattern repeats across real AI capability work. Extra art direction: Use a clean, teachable structure that could stand alone as a reference slide. Avoid: 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. Priority order: 1. exact visible text fidelity 2. thesis clarity and teaching story 3. Mainline White or Dark Expressive family discipline 4. semantic coupling between text and graphic structure 5. premium enterprise credibility 6. visual impressiveness without clutter ``` ### Dark-field expressive render prompt ```text Create a sharp 16:9 dark-mode editorial explainer slide. Use Dark Expressive Editorial. The 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. This dark branch may be more cinematic and keynote-style than the white branch, but it must remain explanatory, premium, legible, and enterprise credible. Dark-mode visual posture: - forceful but not chaotic - more atmospheric than white - stronger contrast between unstable and governed states - no neon overload - no glossy control-room UI - no cyberpunk wallpaper - no detached spectacle - no fake dashboards - no random energy ribbons without meaning - no product-board drift unless the slide is explicitly about product architecture Narrative objective: Bring the full lifecycle together from idea to operation. Visual explanation to depict: clean lifecycle map connecting discovery, design, validation, governance, operation, and maintenance Layout requirements: left-to-right staged lifecycle or circular lifecycle with six distinct stages Composition rules: - anchor the title close to the top edge with minimal dead space above it - preserve the same teaching story as the white version - create stronger contrast between unstable, naive, fragmented, or risky regions and governed, structured, reliable regions - use a visually memorable central architecture, transformation path, control-plane flow, or lifecycle structure - make the most important concept visually dominant - allow more atmosphere, glow, depth, and motion than the white version only where it improves explanation - keep text readable from a screen-share distance - keep the slide premium and controlled, not chaotic Visible text discipline: All 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. Visible text: Lifecycle Lens Shows the Pattern. Discover Design Validate Govern Operate Maintain The pattern repeats across real AI capability work. Extra art direction: Use a clean, teachable structure that could stand alone as a reference slide. Avoid: 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. Priority order: 1. exact visible text fidelity 2. thesis clarity and teaching story 3. Dark Expressive family discipline 4. semantic coupling between text and graphic structure 5. premium enterprise credibility 6. visual impressiveness without clutter ``` ## AICD-14 - The Leadership Ask **Narrative role:** close and call to action **Objective:** Conclude with a concrete leadership ask rather than abstract admiration. ### Visible text corpus ```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-field Mainline White render prompt ```text Create a sharp 16:9 editorial explainer slide. Use Mainline White — Structured Expressive. The 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. This 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. Visual system: - pure white background only - bold red headline in #EB1700 or black headline with selective #EB1700 emphasis - black body text - neutral gray structure and dividers - flat white cards with thin neutral-gray borders - stronger internal hierarchy inside the most important cards - slightly abstract explanatory diagrams - integrated note cards and editorial bands - medium density, not sparse - moderate panelization, not over-boxed - elevated editorial rhythm with varied card scale and visual pacing - medium-high contrast emphasis - medium-high connector emphasis only where it explains the story - selective red accents where they improve emphasis, rhythm, or conceptual contrast - moderate asymmetry and right-side emphasis when the newer, stronger, or more important idea belongs there - strong semantic coupling between nearby text and supporting visual elements - strict clean-footer behavior without visible reserve markers White-mode visual posture: - graphically impressive - structured expressive - boardroom-safe - meaning-first - visually memorable without chaos - less conservative than a plain consulting template - never decorative for its own sake Narrative objective: Conclude with a concrete leadership ask rather than abstract admiration. Visual explanation to depict: executive call-to-action slide with five disciplined commitments arranged around a central leadership mandate Layout requirements: clean closing slide with a strong central message and five structured commitments Composition rules: - anchor the title close to the top edge with minimal empty space above it - keep title and subtitle compactly stacked in a tight top title zone - use one dominant explanatory architecture across the middle - vary card sizes and visual weight based on conceptual importance - use integrated note cards attached directly to the regions they explain - use slightly abstract diagrams, hinge shapes, control bands, routing paths, or lifecycle flows only when they clarify the meaning - avoid equal-weight box grids unless the story truly requires equality - make the most important concept visually dominant - preserve clean margins and a clean footer without showing any reserve-space marker - use white space actively, but do not make the slide timid or visually empty Visible text discipline: All 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. 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. Extra art direction: Confident, decisive, and boardroom-ready. Avoid: 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. Priority order: 1. exact visible text fidelity 2. thesis clarity and teaching story 3. Mainline White or Dark Expressive family discipline 4. semantic coupling between text and graphic structure 5. premium enterprise credibility 6. visual impressiveness without clutter ``` ### Dark-field expressive render prompt ```text Create a sharp 16:9 dark-mode editorial explainer slide. Use Dark Expressive Editorial. The 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. This dark branch may be more cinematic and keynote-style than the white branch, but it must remain explanatory, premium, legible, and enterprise credible. Dark-mode visual posture: - forceful but not chaotic - more atmospheric than white - stronger contrast between unstable and governed states - no neon overload - no glossy control-room UI - no cyberpunk wallpaper - no detached spectacle - no fake dashboards - no random energy ribbons without meaning - no product-board drift unless the slide is explicitly about product architecture Narrative objective: Conclude with a concrete leadership ask rather than abstract admiration. Visual explanation to depict: executive call-to-action slide with five disciplined commitments arranged around a central leadership mandate Layout requirements: clean closing slide with a strong central message and five structured commitments Composition rules: - anchor the title close to the top edge with minimal dead space above it - preserve the same teaching story as the white version - create stronger contrast between unstable, naive, fragmented, or risky regions and governed, structured, reliable regions - use a visually memorable central architecture, transformation path, control-plane flow, or lifecycle structure - make the most important concept visually dominant - allow more atmosphere, glow, depth, and motion than the white version only where it improves explanation - keep text readable from a screen-share distance - keep the slide premium and controlled, not chaotic Visible text discipline: All 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. 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. Extra art direction: Confident, decisive, and boardroom-ready. Avoid: 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. Priority order: 1. exact visible text fidelity 2. thesis clarity and teaching story 3. Dark Expressive family discipline 4. semantic coupling between text and graphic structure 5. premium enterprise credibility 6. visual impressiveness without clutter ```