ppt-page-plan

To update a single slide in a storyboard without rerunning the entire presentation layout, use targeted page-level replanning to modify the StoryboardPage object for a specific page_id. This preserves overall narrative continuity and page identifiers while correcting the targeted slide.

The best way to adjust content blocks and payload budget on a specific presentation page is to apply slide-level revisions that add, remove, or reshape content_blocks. This process synchronizes payload_budget counts while ensuring source_claim_ids and source_evidence_ids reference existing research-pack entries.

Yes, you can correct the narrative role of a specific slide page with just a readable storyboard.json file. While style-spec.json and task-pack.json are optional for validating style_variant and content_density_profile, the core page update only requires the storyboard file.

A key limitation during slide-level revisions is that rules prevent changing page_id or page_number. The replanning process enforces safety by only writing back the target page object and preventing unintentional modifications to other pages in the storyboard.

Targeted slide replanning requires evaluating upstream and downstream page impacts to maintain narrative continuity across the presentation. This impact assessment reports the required synchronization scope and ensures minimal cross-page disruptions when modifying the target slide.

You need to validate style_variant against style-spec.json during storyboard page planning when applying slide-level revisions to presentations, pitch decks, or storyboards. This validation ensures the updated StoryboardPage object aligns with the defined style constraints.