# Governed Capability Formation Family Visual Prompt Deck Duo v1.1

Source package version: **consolidation v0.1 plus AI Capability Discipline v0.9**

Correction: White prompts now use **Mainline White — Structured Expressive** with a true pure-white field. They are intentionally more visually expressive than a safe template, but still boardroom credible.

## White prompt family

Use Mainline White — Structured Expressive.

The background must be pure #FFFFFF white, flat, uniform, and brand-clean. Do not add any background tint, wash, gradient, vignette, paper texture, studio falloff, atmospheric shading, or non-white field treatment.

This must look like a premium enterprise editorial explainer and consulting-grade teaching artifact, not a poster, not a fake dashboard, not a template box farm, and not a cinematic hero graphic.

Visual system:
- pure white background only
- bold red headline in #EB1700 or black headline with selective #EB1700 emphasis
- black body text
- neutral gray structure and dividers
- flat white cards with thin neutral-gray borders
- stronger internal hierarchy inside the most important cards
- slightly abstract explanatory diagrams
- integrated note cards and editorial bands
- medium density, not sparse
- moderate panelization, not over-boxed
- elevated editorial rhythm with varied card scale and visual pacing
- medium-high contrast emphasis
- medium-high connector emphasis only where it explains the story
- selective red accents where they improve emphasis, rhythm, or conceptual contrast
- moderate asymmetry and right-side emphasis when the newer, stronger, or more important idea belongs there
- strong semantic coupling between nearby text and supporting visual elements
- strict clean-footer behavior without visible reserve markers

White-mode visual posture:
- graphically impressive
- structured expressive
- boardroom-safe
- meaning-first
- visually memorable without chaos
- less conservative than a plain consulting template
- never decorative for its own sake

## Dark prompt family

Use Dark Expressive Editorial.

The background must be deep graphite, charcoal, or near-black with controlled gradients only when they help depth and focus. Use crisp white typography, restrained luminous #EB1700 accents, muted cool-gray structure, and high-contrast dark cards or panels.

This dark branch may be more cinematic and keynote-style than the white branch, but it must remain explanatory, premium, legible, and enterprise credible.

Dark-mode visual posture:
- forceful but not chaotic
- more atmospheric than white
- stronger contrast between unstable and governed states
- no neon overload
- no glossy control-room UI
- no cyberpunk wallpaper
- no detached spectacle
- no fake dashboards
- no random energy ribbons without meaning
- no product-board drift unless the slide is explicitly about product architecture

## Renderer usage note

Use one slide prompt at a time. For renderers with weak text fidelity, generate the visual structure first and add final exact text downstream in PowerPoint, Canva, Figma, or another layout tool. Yes, the machines still occasionally treat typography like a haunted Ouija board.

## GCF-01 - AI Capability Playbook

**Narrative role:** opening thesis

**Objective:** Introduce the family as a coherent stack, not a pile of documents.

### Visible text corpus

```text
AI Capability Playbook
One problem space.
Multiple layers of discipline.
Doctrine, commitment, implementation, and evaluation work together.
```

### 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 family as a coherent stack, not a pile of documents.

    Visual explanation to depict:
    stack or systems map showing multiple layers working together to form governed capability

    Layout requirements:
    hero title with a clean stack relationship 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:
    AI Capability Playbook
One problem space.
Multiple layers of discipline.
Doctrine, commitment, implementation, and evaluation work together.

    Extra art direction:
    Make it feel like a serious framework family, not a random document pile.

    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 family as a coherent stack, not a pile of documents.

    Visual explanation to depict:
    stack or systems map showing multiple layers working together to form governed capability

    Layout requirements:
    hero title with a clean stack relationship 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:
    AI Capability Playbook
One problem space.
Multiple layers of discipline.
Doctrine, commitment, implementation, and evaluation work together.

    Extra art direction:
    Make it feel like a serious framework family, not a random document pile.

    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
```

## GCF-02 - These are not competing frameworks. They are a stack.

**Narrative role:** family positioning

**Objective:** End confusion about overlap and show complementarity.

### Visible text corpus

```text
These are not competing frameworks. They are a stack.
Use each package at the right altitude.
Shared primitives keep the family aligned.
```

### 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:
    End confusion about overlap and show complementarity.

    Visual explanation to depict:
    altitude map or layered stack showing complementarity and shared core primitives

    Layout requirements:
    clear family relationship diagram with altitude labels

    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:
    These are not competing frameworks. They are a stack.
Use each package at the right altitude.
Shared primitives keep the family aligned.

    Extra art direction:
    Use the visual to kill ambiguity.

    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:
    End confusion about overlap and show complementarity.

    Visual explanation to depict:
    altitude map or layered stack showing complementarity and shared core primitives

    Layout requirements:
    clear family relationship diagram with altitude labels

    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:
    These are not competing frameworks. They are a stack.
Use each package at the right altitude.
Shared primitives keep the family aligned.

    Extra art direction:
    Use the visual to kill ambiguity.

    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
```

## GCF-03 - Doctrine, commitment, implementation, and evaluation

**Narrative role:** stack anatomy

**Objective:** Show the four main functional layers in simple terms.

### Visible text corpus

```text
Doctrine, commitment, implementation, and evaluation
Doctrine teaches the discipline.
Commitment governs scarce build capacity.
Implementation proves the pattern in a real use case.
Evaluation tests readiness and credibility.
```

### White-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 four main functional layers in simple terms.

    Visual explanation to depict:
    four-layer stack with concise explanation for each layer

    Layout requirements:
    clean four-tier explainer

    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:
    Doctrine, commitment, implementation, and evaluation
Doctrine teaches the discipline.
Commitment governs scarce build capacity.
Implementation proves the pattern in a real use case.
Evaluation tests readiness and credibility.

    Extra art direction:
    Simple 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:
    Show the four main functional layers in simple terms.

    Visual explanation to depict:
    four-layer stack with concise explanation for each layer

    Layout requirements:
    clean four-tier explainer

    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:
    Doctrine, commitment, implementation, and evaluation
Doctrine teaches the discipline.
Commitment governs scarce build capacity.
Implementation proves the pattern in a real use case.
Evaluation tests readiness and credibility.

    Extra art direction:
    Simple 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
```

## GCF-04 - AI Capability Discipline is the doctrine layer.

**Narrative role:** package positioning

**Objective:** Position AICD clearly inside the family.

### Visible text corpus

```text
AI Capability Discipline is the doctrine layer.
It resets the mental model.
It teaches capability formation, routing, source authority, eval validity, and maintenance.
```

### White-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:
    Position AICD clearly inside the family.

    Visual explanation to depict:
    AICD highlighted as the doctrine layer feeding the rest of the family

    Layout requirements:
    single-layer spotlight within the broader family 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:
    AI Capability Discipline is the doctrine layer.
It resets the mental model.
It teaches capability formation, routing, source authority, eval validity, and maintenance.

    Extra art direction:
    Make it foundational.

    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:
    Position AICD clearly inside the family.

    Visual explanation to depict:
    AICD highlighted as the doctrine layer feeding the rest of the family

    Layout requirements:
    single-layer spotlight within the broader family 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:
    AI Capability Discipline is the doctrine layer.
It resets the mental model.
It teaches capability formation, routing, source authority, eval validity, and maintenance.

    Extra art direction:
    Make it foundational.

    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
```

## GCF-05 - WESS Development Commitment governs build-readiness and commitment.

**Narrative role:** package positioning

**Objective:** Position WESS as the team operating model.

### Visible text corpus

```text
WESS Development Commitment governs build-readiness and commitment.
It protects scarce engineering capacity.
It routes work from sandbox to operational capability.
```

### White-field Mainline White render prompt

```text
Create a sharp 16:9 editorial explainer slide.

    Use Mainline White — Structured Expressive.

The background must be pure #FFFFFF white, flat, uniform, and brand-clean. Do not add any background tint, wash, gradient, vignette, paper texture, studio falloff, atmospheric shading, or non-white field treatment.

This must look like a premium enterprise editorial explainer and consulting-grade teaching artifact, not a poster, not a fake dashboard, not a template box farm, and not a cinematic hero graphic.

Visual system:
- pure white background only
- bold red headline in #EB1700 or black headline with selective #EB1700 emphasis
- black body text
- neutral gray structure and dividers
- flat white cards with thin neutral-gray borders
- stronger internal hierarchy inside the most important cards
- slightly abstract explanatory diagrams
- integrated note cards and editorial bands
- medium density, not sparse
- moderate panelization, not over-boxed
- elevated editorial rhythm with varied card scale and visual pacing
- medium-high contrast emphasis
- medium-high connector emphasis only where it explains the story
- selective red accents where they improve emphasis, rhythm, or conceptual contrast
- moderate asymmetry and right-side emphasis when the newer, stronger, or more important idea belongs there
- strong semantic coupling between nearby text and supporting visual elements
- strict clean-footer behavior without visible reserve markers

White-mode visual posture:
- graphically impressive
- structured expressive
- boardroom-safe
- meaning-first
- visually memorable without chaos
- less conservative than a plain consulting template
- never decorative for its own sake

    Narrative objective:
    Position WESS as the team operating model.

    Visual explanation to depict:
    WESS lane model highlighted as the commitment and operating layer

    Layout requirements:
    package spotlight tied to the lane 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:
    WESS Development Commitment governs build-readiness and commitment.
It protects scarce engineering capacity.
It routes work from sandbox to operational capability.

    Extra art direction:
    Operational and practical.

    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:
    Position WESS as the team operating model.

    Visual explanation to depict:
    WESS lane model highlighted as the commitment and operating layer

    Layout requirements:
    package spotlight tied to the lane 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:
    WESS Development Commitment governs build-readiness and commitment.
It protects scarce engineering capacity.
It routes work from sandbox to operational capability.

    Extra art direction:
    Operational and practical.

    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
```

## GCF-06 - Enterprise Architecture Review Assistant is the applied reference implementation.

**Narrative role:** package positioning

**Objective:** Position EA as the concrete instantiation of the doctrine.

### Visible text corpus

```text
Enterprise Architecture Review Assistant is the applied reference implementation.
It shows how the discipline becomes a governed assistant architecture.
It turns theory into an applied build candidate.
```

### White-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:
    Position EA as the concrete instantiation of the doctrine.

    Visual explanation to depict:
    EA package shown as a real applied capability instantiated from the doctrine and core primitives

    Layout requirements:
    package spotlight with input/output flow from doctrine to implementation

    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 is the applied reference implementation.
It shows how the discipline becomes a governed assistant architecture.
It turns theory into an applied build candidate.

    Extra art direction:
    Concrete and credible.

    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:
    Position EA as the concrete instantiation of the doctrine.

    Visual explanation to depict:
    EA package shown as a real applied capability instantiated from the doctrine and core primitives

    Layout requirements:
    package spotlight with input/output flow from doctrine to implementation

    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 is the applied reference implementation.
It shows how the discipline becomes a governed assistant architecture.
It turns theory into an applied build candidate.

    Extra art direction:
    Concrete and credible.

    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
```

## GCF-07 - Shared primitives keep the family coherent.

**Narrative role:** coherence model

**Objective:** Show the common primitives that unify the family.

### Visible text corpus

```text
Shared primitives keep the family coherent.
Source authority
Evidence states
Routing
Human review
Lifecycle maintenance
```

### 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 common primitives that unify the family.

    Visual explanation to depict:
    shared primitives hub feeding multiple family packages

    Layout requirements:
    hub-and-spoke or common-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:
    Shared primitives keep the family coherent.
Source authority
Evidence states
Routing
Human review
Lifecycle maintenance

    Extra art direction:
    Make the primitives feel reusable and canonical.

    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 common primitives that unify the family.

    Visual explanation to depict:
    shared primitives hub feeding multiple family packages

    Layout requirements:
    hub-and-spoke or common-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:
    Shared primitives keep the family coherent.
Source authority
Evidence states
Routing
Human review
Lifecycle maintenance

    Extra art direction:
    Make the primitives feel reusable and canonical.

    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
```

## GCF-08 - Route work by risk, commitment depth, and control needs.

**Narrative role:** decision use map

**Objective:** Show how to decide which package or lane to use.

### Visible text corpus

```text
Route work by risk, commitment depth, and control needs.
Low-risk exploration
Team build commitment
Applied capability design
Evaluation 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:
    Show how to decide which package or lane to use.

    Visual explanation to depict:
    decision routing map that points different work types to the right package or lane

    Layout requirements:
    routing matrix or decision tree

    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:
    Route work by risk, commitment depth, and control needs.
Low-risk exploration
Team build commitment
Applied capability design
Evaluation and validation

    Extra art direction:
    Very clear and actionable.

    Avoid:
    any non-white background, background tint, gradients in the white field, cinematic poster behavior, giant hero machinery, glossy UI, fake dashboards, stock people, robots, decorative data centers, random circuit boards, over-panelization, red everywhere, helper labels, prompt scaffolding, watermarks, and text gibberish.

    Priority order:
1. exact visible text fidelity
2. thesis clarity and teaching story
3. Mainline White or Dark Expressive family discipline
4. semantic coupling between text and graphic structure
5. premium enterprise credibility
6. visual impressiveness without clutter
```

### Dark-field expressive render prompt

```text
Create a sharp 16:9 dark-mode editorial explainer slide.

    Use Dark Expressive Editorial.

The background must be deep graphite, charcoal, or near-black with controlled gradients only when they help depth and focus. Use crisp white typography, restrained luminous #EB1700 accents, muted cool-gray structure, and high-contrast dark cards or panels.

This dark branch may be more cinematic and keynote-style than the white branch, but it must remain explanatory, premium, legible, and enterprise credible.

Dark-mode visual posture:
- forceful but not chaotic
- more atmospheric than white
- stronger contrast between unstable and governed states
- no neon overload
- no glossy control-room UI
- no cyberpunk wallpaper
- no detached spectacle
- no fake dashboards
- no random energy ribbons without meaning
- no product-board drift unless the slide is explicitly about product architecture

    Narrative objective:
    Show how to decide which package or lane to use.

    Visual explanation to depict:
    decision routing map that points different work types to the right package or lane

    Layout requirements:
    routing matrix or decision tree

    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:
    Route work by risk, commitment depth, and control needs.
Low-risk exploration
Team build commitment
Applied capability design
Evaluation and validation

    Extra art direction:
    Very clear and actionable.

    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
```

## GCF-09 - Use the right package at the right altitude.

**Narrative role:** summary guidance

**Objective:** Give a memorable decision rule to practitioners and leaders.

### Visible text corpus

```text
Use the right package at the right altitude.
Teach with the doctrine.
Commit with the operating model.
Build with the implementation pattern.
Validate with the evaluation harness.
```

### White-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:
    Give a memorable decision rule to practitioners and leaders.

    Visual explanation to depict:
    altitude or ladder metaphor with package choice matched to operating need

    Layout requirements:
    four-step altitude ladder

    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:
    Use the right package at the right altitude.
Teach with the doctrine.
Commit with the operating model.
Build with the implementation pattern.
Validate with the evaluation harness.

    Extra art direction:
    Memorable, simple, and polished.

    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:
    Give a memorable decision rule to practitioners and leaders.

    Visual explanation to depict:
    altitude or ladder metaphor with package choice matched to operating need

    Layout requirements:
    four-step altitude ladder

    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:
    Use the right package at the right altitude.
Teach with the doctrine.
Commit with the operating model.
Build with the implementation pattern.
Validate with the evaluation harness.

    Extra art direction:
    Memorable, simple, and polished.

    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
```

## GCF-10 - Leadership move: fund the discipline, not just the interface.

**Narrative role:** closing leadership ask

**Objective:** Close the family story with a unifying leadership action.

### Visible text corpus

```text
Leadership move: fund the discipline, not just the interface.
Support doctrine.
Support controlled commitment.
Support applied capability design.
Support validation and maintenance.
```

### 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 the family story with a unifying leadership action.

    Visual explanation to depict:
    leadership investment stack showing disciplined investment priorities across the family

    Layout requirements:
    clean closing call-to-action with four funding pillars

    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:
    Leadership move: fund the discipline, not just the interface.
Support doctrine.
Support controlled commitment.
Support applied capability design.
Support validation and maintenance.

    Extra art direction:
    Strong, strategic, and board-ready.

    Avoid:
    any non-white background, background tint, gradients in the white field, cinematic poster behavior, giant hero machinery, glossy UI, fake dashboards, stock people, robots, decorative data centers, random circuit boards, over-panelization, red everywhere, helper labels, prompt scaffolding, watermarks, and text gibberish.

    Priority order:
1. exact visible text fidelity
2. thesis clarity and teaching story
3. Mainline White or Dark Expressive family discipline
4. semantic coupling between text and graphic structure
5. premium enterprise credibility
6. visual impressiveness without clutter
```

### Dark-field expressive render prompt

```text
Create a sharp 16:9 dark-mode editorial explainer slide.

    Use Dark Expressive Editorial.

The background must be deep graphite, charcoal, or near-black with controlled gradients only when they help depth and focus. Use crisp white typography, restrained luminous #EB1700 accents, muted cool-gray structure, and high-contrast dark cards or panels.

This dark branch may be more cinematic and keynote-style than the white branch, but it must remain explanatory, premium, legible, and enterprise credible.

Dark-mode visual posture:
- forceful but not chaotic
- more atmospheric than white
- stronger contrast between unstable and governed states
- no neon overload
- no glossy control-room UI
- no cyberpunk wallpaper
- no detached spectacle
- no fake dashboards
- no random energy ribbons without meaning
- no product-board drift unless the slide is explicitly about product architecture

    Narrative objective:
    Close the family story with a unifying leadership action.

    Visual explanation to depict:
    leadership investment stack showing disciplined investment priorities across the family

    Layout requirements:
    clean closing call-to-action with four funding pillars

    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:
    Leadership move: fund the discipline, not just the interface.
Support doctrine.
Support controlled commitment.
Support applied capability design.
Support validation and maintenance.

    Extra art direction:
    Strong, strategic, and board-ready.

    Avoid:
    neon overload, sci-fi wallpaper, fake command-center UI, glossy dashboard panels, stock people, robots, random holograms, decorative circuitry, unreadable microtext, vendor logos, watermarks, prompt scaffolding, and visual chaos.

    Priority order:
1. exact visible text fidelity
2. thesis clarity and teaching story
3. Dark Expressive family discipline
4. semantic coupling between text and graphic structure
5. premium enterprise credibility
6. visual impressiveness without clutter
```