Pitch Deck Architecture

Page-level design lives in $best-practices-slide-design (ten archetypes). This skill is the layer above it: how a DECK is shaped, and how that shape is allowed to be decided.

The rule that exists because it was broken

Sections are DERIVED from the source document. Never hardcoded.

A compiler that contains sections = [("The Problem", ...), ("How It Works", ...)] is not compiling a source into a deck — it is decorating a hand-written narrative with the source's words. Observed 2026-08-12 in $pitchdeck: a four-section list authored from memory shipped as "README to deck" for weeks. When the same README was actually READ by a model seat, its argument turned out to be one repeated thesis restated across five contexts, not a problem/solution arc — a structure no hardcoded list would ever have found.