One AST, Two Native PowerPoint Decks

July 14, 2026 · View on GitHub

Humanize PPT × PPT Master: lock what the story needs to say in a testable structure, then let a native PowerPoint renderer own how it looks.

Not a Web Page in PowerPoint

Many AI decks look finished until delivery, when every slide turns out to be one uneditable image. This workflow separates ownership:

  • Humanize PPT owns the audience, narrative, slide intent, and speaker notes.
  • PPT Master owns the visual system, per-slide SVG, native DrawingML, and export.
  • Text, shapes, relationships, and notes remain editable in PowerPoint.

Core message: Compatibility means preserving both the content contract and native editability—not merely producing a file that opens.

A Repeatable Production Chain

The workflow moves through five ordered stages:

  1. Source material
  2. Humanize AST and slide contract
  3. PPT Master's three-stage design confirmation
  4. Native editable PPTX
  5. Humanize presentation checkup

Core message: Every layer has a clear owner, so fixes return to the source that owns the problem instead of patching exported OOXML.

More Than Five Images

A native delivery keeps all of the following:

  • Editable text and shapes
  • Decomposable flows and relationships
  • Speaker notes on every slide
  • Slide transitions
  • An independently verifiable OOXML package

Core message: The audience gets the design; the creator gets a file they can keep working in.

Same Path, Two Languages

Chinese and English use the same five-slide story, the same design confirmation gate, and the same native export and checkup standards. The language changes the copy and typography strategy—not the support level.

Closing line: One semantic contract, two languages, two genuinely editable PowerPoint decks.