Detailed Outline

# ppt_deck / detailed_outline

## Goal

Turn the accepted storyline and full source into a deck-level argument and page sequence that a blueprint author can execute.

## Good Work

- Read `source_materials_full_text`, the accepted storyline, evidence table, audience goal, and hard constraints. Planning signals and source slide suggestions are advisory.
- Decide page count, chapters, evidence placement, and pacing from the actual argument. Only explicit hard constraints such as `max_slides` are fixed.
- Give every page an audience-facing claim, evidence, page purpose, content basis, source labels, private speaker/transition notes, and a suitable render recipe.
- Preserve the accepted `claim_spine_lock`, including claim text, source refs, first-use naming, proof/resolution mapping, and forbidden drift.
- Keep paper/manuscript reporting evidence-led: visible claims and key results retain the actual source-backed numbers and limitations, without inventing deployment or promotional value.
- Use public names in visible fields; internal ids and authoring metadata stay in provenance or notes.
- Outline, blueprint, and visual direction may iterate when capacity or hierarchy exposes a structural problem. Preserve explicitly approved decisions and route back only the affected structure.

## Boundary And Handoff

Do not render HTML or copy operator/runtime language into audience-facing content. Return the detailed-outline object required by the attached output contract, with enough evidence and narrative detail for `slide_blueprint`.