# Enterprise Architecture Review Assistant Visual Prompt Deck Duo v1.1 Source package version: **v1.14.1** 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. ## EARA-01 - Enterprise Architecture Review Assistant **Narrative role:** opening thesis **Objective:** Introduce the assistant as a governed review capability, not just an AI feature. ### Visible text corpus ```text Enterprise Architecture Review Assistant A governed review capability for architecture intake, analysis, evidence, and recommendation support. Controlled build-preparation candidate Not broad pilot or production ``` ### White-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: Introduce the assistant as a governed review capability, not just an AI feature. Visual explanation to depict: hero opener showing an architecture review engine transforming scattered inputs into structured recommendations and evidence Layout requirements: hero title with central review-engine graphic and succinct 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: Enterprise Architecture Review Assistant A governed review capability for architecture intake, analysis, evidence, and recommendation support. Controlled build-preparation candidate Not broad pilot or production Extra art direction: Premium and authoritative, with architecture-review seriousness. 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: Introduce the assistant as a governed review capability, not just an AI feature. Visual explanation to depict: hero opener showing an architecture review engine transforming scattered inputs into structured recommendations and evidence Layout requirements: hero title with central review-engine graphic and succinct 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: Enterprise Architecture Review Assistant A governed review capability for architecture intake, analysis, evidence, and recommendation support. Controlled build-preparation candidate Not broad pilot or production Extra art direction: Premium and authoritative, with architecture-review seriousness. 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 ``` ## EARA-02 - Why leadership should care **Narrative role:** executive relevance **Objective:** Frame the business problem clearly for leadership. ### Visible text corpus ```text Why leadership should care Architecture review pressure is rising. Review knowledge is scattered. Decision quality depends on source authority, review consistency, and explainable outputs. ``` ### White-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: Frame the business problem clearly for leadership. Visual explanation to depict: pressure-versus-fragmentation story with demand pressure rising on one side and scattered knowledge fragments on the other, resolved by a structured capability Layout requirements: problem/response composition with tension on the left and a structured answer on the right 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: Why leadership should care Architecture review pressure is rising. Review knowledge is scattered. Decision quality depends on source authority, review consistency, and explainable outputs. Extra art direction: Make the pain visible without becoming melodramatic. 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: Frame the business problem clearly for leadership. Visual explanation to depict: pressure-versus-fragmentation story with demand pressure rising on one side and scattered knowledge fragments on the other, resolved by a structured capability Layout requirements: problem/response composition with tension on the left and a structured answer on the right 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: Why leadership should care Architecture review pressure is rising. Review knowledge is scattered. Decision quality depends on source authority, review consistency, and explainable outputs. Extra art direction: Make the pain visible without becoming melodramatic. 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 ``` ## EARA-03 - Do we want a clever demo, or a durable review capability? **Narrative role:** decision framing **Objective:** Differentiate novelty from durable operational value. ### Visible text corpus ```text Do we want a clever demo, or a durable review capability? A demo proves possibility. A durable capability requires evidence loops, source discipline, roles, and sustainment. ``` ### White-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 novelty from durable operational value. Visual explanation to depict: comparison between a shiny demo artifact and a durable capability stack with governance, review, and sustainment Layout requirements: balanced comparison slide with a visible maturity gap 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: Do we want a clever demo, or a durable review capability? A demo proves possibility. A durable capability requires evidence loops, source discipline, roles, and sustainment. Extra art direction: The demo side can look tempting; the durable side should look trustworthy. 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 novelty from durable operational value. Visual explanation to depict: comparison between a shiny demo artifact and a durable capability stack with governance, review, and sustainment Layout requirements: balanced comparison slide with a visible maturity gap 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: Do we want a clever demo, or a durable review capability? A demo proves possibility. A durable capability requires evidence loops, source discipline, roles, and sustainment. Extra art direction: The demo side can look tempting; the durable side should look trustworthy. 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 ``` ## EARA-04 - Architecture review pressure is rising while review knowledge remains scattered. **Narrative role:** problem detail **Objective:** Explain the operational pain in concrete terms. ### Visible text corpus ```text Architecture review pressure is rising while review knowledge remains scattered. Inputs arrive from many channels. Criteria live across documents, teams, and habits. The review brain is fragmented. ``` ### White-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: Explain the operational pain in concrete terms. Visual explanation to depict: many inbound artifacts and channels flowing into fragmented review knowledge, highlighting the need for consolidation Layout requirements: inbound chaos converging on a broken review surface, with a hint of structured consolidation 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: Architecture review pressure is rising while review knowledge remains scattered. Inputs arrive from many channels. Criteria live across documents, teams, and habits. The review brain is fragmented. Extra art direction: Use artifact-like tiles rather than generic icons. 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: Explain the operational pain in concrete terms. Visual explanation to depict: many inbound artifacts and channels flowing into fragmented review knowledge, highlighting the need for consolidation Layout requirements: inbound chaos converging on a broken review surface, with a hint of structured consolidation 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: Architecture review pressure is rising while review knowledge remains scattered. Inputs arrive from many channels. Criteria live across documents, teams, and habits. The review brain is fragmented. Extra art direction: Use artifact-like tiles rather than generic icons. 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 ``` ## EARA-05 - “Build an agent” is the wrong center of gravity. **Narrative role:** mental model correction **Objective:** Show that the center of gravity is the review logic, not the agent label. ### Visible text corpus ```text “Build an agent” is the wrong center of gravity. The center is not the chat surface. The center is the review logic, source authority, decision criteria, and evidence model. ``` ### White-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 center of gravity is the review logic, not the agent label. Visual explanation to depict: a miscentered spotlight on an agent/chat icon contrasted with the real core made of review logic, criteria, source maps, and evidence Layout requirements: off-center illusion corrected by a structured core diagram 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: “Build an agent” is the wrong center of gravity. The center is not the chat surface. The center is the review logic, source authority, decision criteria, and evidence model. Extra art direction: This should feel like a sharp reframing 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: Show that the center of gravity is the review logic, not the agent label. Visual explanation to depict: a miscentered spotlight on an agent/chat icon contrasted with the real core made of review logic, criteria, source maps, and evidence Layout requirements: off-center illusion corrected by a structured core diagram 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: “Build an agent” is the wrong center of gravity. The center is not the chat surface. The center is the review logic, source authority, decision criteria, and evidence model. Extra art direction: This should feel like a sharp reframing 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 ``` ## EARA-06 - The capability has three layers — only one is the agent experience. **Narrative role:** architecture model **Objective:** Explain the layered architecture cleanly. ### Visible text corpus ```text The capability has three layers — only one is the agent experience. Layer 1: review brain Layer 2: governance and evidence loop Layer 3: user experience layer ``` ### White-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: Explain the layered architecture cleanly. Visual explanation to depict: three-layer architecture stack showing the user experience as the topmost visible layer over the deeper review brain and governance layers Layout requirements: clean layered stack diagram 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 has three layers — only one is the agent experience. Layer 1: review brain Layer 2: governance and evidence loop Layer 3: user experience layer Extra art direction: Make the hidden layers feel more substantive than the visible top layer. 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: Explain the layered architecture cleanly. Visual explanation to depict: three-layer architecture stack showing the user experience as the topmost visible layer over the deeper review brain and governance layers Layout requirements: clean layered stack diagram 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 has three layers — only one is the agent experience. Layer 1: review brain Layer 2: governance and evidence loop Layer 3: user experience layer Extra art direction: Make the hidden layers feel more substantive than the visible top layer. 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 ``` ## EARA-07 - The hard work is codifying how the enterprise judges architecture fitness. **Narrative role:** core value **Objective:** Show the true work of the capability. ### Visible text corpus ```text The hard work is codifying how the enterprise judges architecture fitness. Criteria Evidence Trade-offs Exceptions Recommendations ``` ### 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 the true work of the capability. Visual explanation to depict: codified review brain made of criteria, evidence, trade-off analysis, and recommendation logic Layout requirements: central review-brain map with five key judgment components 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 hard work is codifying how the enterprise judges architecture fitness. Criteria Evidence Trade-offs Exceptions Recommendations Extra art direction: Serious, methodical, and knowledge-rich. 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 the true work of the capability. Visual explanation to depict: codified review brain made of criteria, evidence, trade-off analysis, and recommendation logic Layout requirements: central review-brain map with five key judgment components 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 hard work is codifying how the enterprise judges architecture fitness. Criteria Evidence Trade-offs Exceptions Recommendations Extra art direction: Serious, methodical, and knowledge-rich. 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 ``` ## EARA-08 - The first proof is an evidence loop, not a shiny interface. **Narrative role:** proof strategy **Objective:** Focus the first proof on capability substance and feedback. ### Visible text corpus ```text The first proof is an evidence loop, not a shiny interface. Start with source package. Run structured review. Capture reviewer feedback. Improve the logic. ``` ### White-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: Focus the first proof on capability substance and feedback. Visual explanation to depict: tight evidence loop cycling through source package, structured review, reviewer feedback, and refinement Layout requirements: four-step loop or flywheel 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 first proof is an evidence loop, not a shiny interface. Start with source package. Run structured review. Capture reviewer feedback. Improve the logic. Extra art direction: Show disciplined iteration, not spectacle. 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: Focus the first proof on capability substance and feedback. Visual explanation to depict: tight evidence loop cycling through source package, structured review, reviewer feedback, and refinement Layout requirements: four-step loop or flywheel 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 first proof is an evidence loop, not a shiny interface. Start with source package. Run structured review. Capture reviewer feedback. Improve the logic. Extra art direction: Show disciplined iteration, not spectacle. 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 ``` ## EARA-09 - Deterministic where possible. AI where ambiguity exists. Human where judgment matters. **Narrative role:** operating principle **Objective:** Show the balanced division of labor. ### Visible text corpus ```text Deterministic where possible. AI where ambiguity exists. Human where judgment matters. Use each mode where it is strongest. ``` ### 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 the balanced division of labor. Visual explanation to depict: three-mode operating model with deterministic automation, AI reasoning, and human judgment each occupying the right zone Layout requirements: three-column or triangular operating model 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: Deterministic where possible. AI where ambiguity exists. Human where judgment matters. Use each mode where it is strongest. Extra art direction: Balanced, precise, and teachable. 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 the balanced division of labor. Visual explanation to depict: three-mode operating model with deterministic automation, AI reasoning, and human judgment each occupying the right zone Layout requirements: three-column or triangular operating model 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: Deterministic where possible. AI where ambiguity exists. Human where judgment matters. Use each mode where it is strongest. Extra art direction: Balanced, precise, and teachable. 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 ``` ## EARA-10 - The path should be staged — prove the review brain before scaling the runtime. **Narrative role:** roadmap **Objective:** Show a prudent staged path forward. ### Visible text corpus ```text The path should be staged — prove the review brain before scaling the runtime. Stage 1: curate source authority Stage 2: prove review logic Stage 3: scale runtime and experience ``` ### White-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 a prudent staged path forward. Visual explanation to depict: staged progression from source curation to review-brain proof to runtime scaling Layout requirements: three-stage roadmap with increasing sophistication 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 path should be staged — prove the review brain before scaling the runtime. Stage 1: curate source authority Stage 2: prove review logic Stage 3: scale runtime and experience Extra art direction: Make the sequencing feel rational and disciplined. 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 a prudent staged path forward. Visual explanation to depict: staged progression from source curation to review-brain proof to runtime scaling Layout requirements: three-stage roadmap with increasing sophistication 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 path should be staged — prove the review brain before scaling the runtime. Stage 1: curate source authority Stage 2: prove review logic Stage 3: scale runtime and experience Extra art direction: Make the sequencing feel rational and disciplined. 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 ``` ## EARA-11 - Outsource the wiring. Do not outsource the review judgment. **Narrative role:** sourcing strategy **Objective:** Differentiate implementation support from judgment ownership. ### Visible text corpus ```text Outsource the wiring. Do not outsource the review judgment. Implementation wiring can be externalized. Architecture judgment, criteria, and source authority remain enterprise-owned. ``` ### White-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 implementation support from judgment ownership. Visual explanation to depict: clear boundary between commodity wiring and enterprise-owned review judgment Layout requirements: two-zone ownership map 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: Outsource the wiring. Do not outsource the review judgment. Implementation wiring can be externalized. Architecture judgment, criteria, and source authority remain enterprise-owned. Extra art direction: Make ownership and boundaries 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: Differentiate implementation support from judgment ownership. Visual explanation to depict: clear boundary between commodity wiring and enterprise-owned review judgment Layout requirements: two-zone ownership map 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: Outsource the wiring. Do not outsource the review judgment. Implementation wiring can be externalized. Architecture judgment, criteria, and source authority remain enterprise-owned. Extra art direction: Make ownership and boundaries 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 ``` ## EARA-12 - A modest alpha still needs real roles. **Narrative role:** operating model **Objective:** Show that even a small alpha requires defined ownership. ### Visible text corpus ```text A modest alpha still needs real roles. Sponsor Capability owner Source stewards Reviewers Builders Operators ``` ### 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 even a small alpha requires defined ownership. Visual explanation to depict: role map around the capability showing necessary operating roles and their relationship to the system Layout requirements: role ring or connected role map 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: A modest alpha still needs real roles. Sponsor Capability owner Source stewards Reviewers Builders Operators Extra art direction: Clean role architecture, not a messy org chart. 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 even a small alpha requires defined ownership. Visual explanation to depict: role map around the capability showing necessary operating roles and their relationship to the system Layout requirements: role ring or connected role map 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: A modest alpha still needs real roles. Sponsor Capability owner Source stewards Reviewers Builders Operators Extra art direction: Clean role architecture, not a messy org chart. 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 ``` ## EARA-13 - The package is ready for controlled build preparation — not broad pilot or production. **Narrative role:** status statement **Objective:** State the current maturity without overclaiming. ### Visible text corpus ```text The package is ready for controlled build preparation — not broad pilot or production. Proceed with controlled prep. Do not oversell maturity. Focus on evidence, scope, and validation. ``` ### White-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: State the current maturity without overclaiming. Visual explanation to depict: maturity marker or staged-readiness graphic clearly highlighting the current state Layout requirements: readiness-stage slide with a highlighted current position 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 package is ready for controlled build preparation — not broad pilot or production. Proceed with controlled prep. Do not oversell maturity. Focus on evidence, scope, and validation. Extra art direction: Confident but disciplined. 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: State the current maturity without overclaiming. Visual explanation to depict: maturity marker or staged-readiness graphic clearly highlighting the current state Layout requirements: readiness-stage slide with a highlighted current position 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 package is ready for controlled build preparation — not broad pilot or production. Proceed with controlled prep. Do not oversell maturity. Focus on evidence, scope, and validation. Extra art direction: Confident but disciplined. 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 ``` ## EARA-14 - Sponsor the review brain before funding the shiny interface. **Narrative role:** closing leadership ask **Objective:** Close on a resource-allocation message. ### Visible text corpus ```text Sponsor the review brain before funding the shiny interface. Prioritize source authority. Codify decision logic. Prove the evidence loop. Then scale the experience layer. ``` ### White-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: Close on a resource-allocation message. Visual explanation to depict: resource-allocation hierarchy or investment stack placing the review brain beneath the experience layer Layout requirements: closing call-to-action with four investment priorities 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: Sponsor the review brain before funding the shiny interface. Prioritize source authority. Codify decision logic. Prove the evidence loop. Then scale the experience layer. Extra art direction: Executive and memorable. 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: Close on a resource-allocation message. Visual explanation to depict: resource-allocation hierarchy or investment stack placing the review brain beneath the experience layer Layout requirements: closing call-to-action with four investment priorities 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: Sponsor the review brain before funding the shiny interface. Prioritize source authority. Codify decision logic. Prove the evidence loop. Then scale the experience layer. Extra art direction: Executive and memorable. 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 ```