title: “{Slide title — human readable, Title Case}” slug: {engagement}-{slide-name} # kebab-case, globally unique within slides-content/ date_created: 2026-MM-DD date_modified: 2026-MM-DD tags: # Train-Case (Capitalized-Words-Joined-By-Hyphens)

• {Engagement-Deck} # e.g., Lossless-Group-Deck
• {Structural-Tag} # e.g., Hero-Slide, Vision, Substantiation, Closing

Optional fields — uncomment as they earn their place

lede: “One-line summary, used for indexing and previews.”

slot: “05” # deck-OS slot identifier when known

variant: enhanced-v1 # or all if variant-invariant

status: Draft # Draft | In-Review | Final

authors:

- Michael Staton

derived_from: {parent-outline-filename}.md # if this slide was split out of a top-level outline

{Slide title}

What this slide says

The argument in one paragraph. If a reader retains only this paragraph, what should they take away?

Why this slide exists

The slide’s job in the deck arc — what it sets up, what it pays off, what the deck would be missing without it.

Content

The actual slide content. Iterative; expect this section to fork as variants explore different treatments.

• Headline candidate: …
• Body copy: …
• Bullet points: …
• Image brief: …
• Callouts: …

Substantiation

Citations, evidence, source documents. Per the DD-grade citation discipline (see dididecks-ai/context-v/specs/Dididecks-AI-DD-Ready-Citation-and-Source-Access.md), fact-claims need a source.

• {Source 1 — link or reference}
• {Source 2 — link or reference}

Authoring notes

Open questions, deliberate tradeoffs, decisions deferred to a sibling slide. The place where the why of editorial choices gets recorded so a later collaborator (human or agent) doesn’t undo them by accident.