Visual Direction

# ppt_deck / visual_direction

## Goal

Create a deck-wide visual thesis and page rhythm that makes the current blueprint's claim/proof structure observable and authorable across the selected route.

## Good Work

- Consume the real blueprint slide ids/content and any current template profile; do not infer a fixed page count, peak list, archetype quota, or sample palette.
- Define visual identity, hierarchy, typography, palette, spacing, continuity, semantic composition, rhythm, peak pages, and page-family reuse limits for this deck.
- Give every page a first-glance relationship and proof object. Visual form must express the claim semantics, not decorate a repeated card grid.
- Protect readable title/body/label/table/caption scale, safe zones, vertical balance, and separation between adjacent readable blocks.
- Preserve the accepted claim spine and public naming. Visual direction may propose the smallest blueprint route-back when canvas, template capacity, or hierarchy makes a page invalid.
- For `optimize_existing`, name strengths to preserve and regressions to avoid.

## Professional Dependency

Blueprint and visual direction jointly form the materialization basis. The visual director can iterate with the blueprint, but cannot rewrite unsupported claims or grant artifact/review/export authority.

## Handoff

Return the visual-direction object required by the attached output contract, using real slide ids and instructions that page/native/HTML authors can consume.