# Blueprint slide patterns

## Non-negotiable authoring rules

- **Slide titles use Medium (500), which is also the maximum font weight.** No SemiBold, Bold, or heavier authored text. Use grayscale shades for extra hierarchy; historical screenshots do not override this rule.
- **Minimize text content specifically.** Keep slide text concise and tell the user in agent chat about meaningful information omitted or condensed. Preserve essential caveats and explicitly required content; do not make the remaining claims misleading.

Choose a pattern by content hierarchy, then move its gutters to fit. Patterns are editable starting points, not a fixed sequence for every deck.

| Pattern | Main structure | Marker placement |
| --- | --- | --- |
| Blank foundation | One large region, source 48 px inset | Four perimeter intersections |
| Inset foundation | One smaller region; moved gutters | Four intersections of moved boundaries |
| Equal split | Two primary columns | Outer corners and divider endpoints |
| Two-by-two | Four peer regions | Primary boundary junctions and central crossing |
| Image-led cover | One image/title composition | Outer gutter intersections; image can overlap |
| Title and content | Title band plus body | Title-band boundary junctions |
| Two-column explanation | Title band, two peer body regions | Outer corners and title/body band endpoints only; no subordinate column hexes |
| Three principles | Title band, three primary body regions | Outer corners and title/body band endpoints only; no subordinate column hexes |
| Figure and interpretation | Broad figure beside narrow explanation | Main vertical split endpoints |
| Scientific case | Text and figure, secondary metadata row | Main split only; metadata row stays plain |
| Metric and list | Broad metric plus narrow supporting list | Main split only; list rows stay plain |
| Deep-inset contact | Narrow central text band | Four moved boundary intersections |
| Process | Stages beneath a title | Outer corners and title/body endpoints; subordinate stages have lines only |
| Roadmap | Phases beneath a title; secondary date/outcome organization | Outer corners and title/body endpoints; subordinate phases have lines only |
| Evidence chart | Large chart within primary content region | Blueprint boundary only; chart grid is separate |
| Appendix table | Title, full row-and-column table grid, notes band; balanced cell padding | Hexes at major section boundaries; ordinary cell intersections have lines without hexes |
| Replaceable image cover | Blank artwork region, title and subtitle | Outer gutter intersections |

[Open the built file](https://www.figma.com/slides/n8T67Y2MXlA0JOMOJdB8v4). Exact node IDs are in [the reference register](references.md). Additional layouts are permitted if they use the same hierarchy-first construction. Do not infer a new mandatory accent, illustration motif, or dark treatment from an unrelated example.

For tables, use the user-adjusted table (template node `6:121`); do not copy the original generated table spacing.

For four peer principles, the corrected construction guide (`6:172`) demonstrates one short statement per quadrant, row-major reading order, visible horizontal and vertical subordinate grid divisions, and balanced cell padding. Use this when the content hierarchy warrants four equal regions; it is not a universal four-item mandate.

## Topmost hierarchy only — explicit correction

Hexes mark only the TOPMOST level of hierarchy division. Identify that level explicitly before placing markers. In a title-plus-grid slide, title and grid are the top-level regions; grid cells are subordinate. Keep all useful grid lines, but omit hexes at their internal crossing and at the four places their dividers meet the grid boundary. Retain the four outer corners and the two title/grid boundary endpoints (six hexes total). A divider touching a top-level boundary does not itself become top-level.