Artifacts
Six outputs, two pipeline runs
Each tile below opens a self-contained page — the exact HTML the pipeline wrote, styled in the Variant A system.
Presentation pipeline
Webinar Deck
The audition tape — a 24-slide, self-contained HTML deck for the live session Fleet delivers to a prospective buyer's team.
Open the deckPresentation pipeline
Program Outline
"The Resilience Program Outline" — a three-session lead magnet built to be forwarded to a CFO or CHRO. Print-ready.
Open the outlineCampaign pipeline
Email Sequence
Five drafted emails across a 16-day send window — subject lines, preview text, and full body copy for each.
Open the sequenceCampaign pipeline
Landing Page
The registration page a buyer lands on from an email or ad. Sets up the session as an audition, not a webinar.
Open the landing pageCampaign pipeline
Thank-You Page
What a registrant sees immediately after signing up — confirmation details and a calendar chip.
Open the thank-you pageCampaign pipeline
Replay Page
The post-session page: recording placeholder, share prompt, and the earned biography, held for the end.
Open the replay pageHow this was made
Two pipeline runs, one campaign brief
Both pipelines read the same campaign brief as their single source of truth for facts, offer, buyer, and voice — so nothing in the deck contradicts anything in the emails.
campaign-webinar.yaml— run702e1f4e— produced the landing page, thank-you page, replay page, and five emails.presentation-orchestrator.yaml— runcf7d363f— produced the webinar deck and, alongside the campaign run, the program outline.
Every artifact passed through review gates before it reached this page:
Plus a byte-level artifact contract: each pipeline stage's output path is pinned in the campaign brief, and a verification step asserts every pinned file exists with nonzero content before the run is considered complete. A stage that writes to the wrong place fails the run.