This is the
open machine’s actual output — not a demo. One brief in
content-index.json → the agent composes, renders, certifies, and ships every asset below.
See it run here;
run it yourself —
the whole engine is open source. Each card links back to its storyboard (the brief + the exact composition). Built by Dom Davis. Minus the hype.
brand · Email Hero GIF · ⟁ Signum
Four parts, one engine
pending render
9:16 · TikTok · Instagram Reels · YouTube Shorts · Facebook Reels · Stories · Threads · Pinterest
pending render
1:1 · Instagram feed · Facebook · X/Twitter · Bluesky · LinkedIn feed
pending render
16:9 · YouTube · X card · LinkedIn video · Blog (embed)
cuts · 1+ Email (Resend, owned list)
storyboard → brief + scenesstaff training · longform · ⟁ Magister
The first week in a seat
pending render
16:9 · YouTube (long-form)
cuts · 2YouTube Shorts 9:16 · 60s · SceneReel+ Blog (static .xyz + Duda .com)
storyboard → brief + scenesmultimedia · Content Strategy · ⟁ Lumen
Strategy decides what to skip
pending render
9:16 · TikTok · Instagram Reels · YouTube Shorts · Facebook Reels · Stories · Threads · Pinterest
pending render
1:1 · Instagram feed · Facebook · X/Twitter · Bluesky · LinkedIn feed
pending render
16:9 · YouTube · X card · LinkedIn video · Blog (embed)
cuts · 9LinkedIn 1:1 · 120s · LinkedInDocX 1:1 · 120s · XThreadCardYouTube Shorts 9:16 · 60s · SceneReelInstagram (Reels · feed) 9:16 · 90s · StoryReelFacebook (Reels · feed) 9:16 · 90s · SceneReelThreads 1:1 · 90s · SceneReelTikTok 9:16 · 60s · TikTokNativePinterest 9:16 · 60s · PinterestPinBluesky 1:1 · 60s · SceneReel
storyboard → brief + scenesit dev · Software Development · ⟁ Faber
Custom software, said plainly
pending render
9:16 · TikTok · Instagram Reels · YouTube Shorts · Facebook Reels · Stories · Threads · Pinterest
pending render
1:1 · Instagram feed · Facebook · X/Twitter · Bluesky · LinkedIn feed
pending render
16:9 · YouTube · X card · LinkedIn video · Blog (embed)
cuts · 9LinkedIn 1:1 · 120s · LinkedInDocX 1:1 · 120s · XThreadCardYouTube Shorts 9:16 · 60s · SceneReelInstagram (Reels · feed) 9:16 · 90s · StoryReelFacebook (Reels · feed) 9:16 · 90s · SceneReelThreads 1:1 · 90s · SceneReelTikTok 9:16 · 60s · TikTokNativePinterest 9:16 · 60s · PinterestPinBluesky 1:1 · 60s · SceneReel
storyboard → brief + scenesemerging tech · Internet of Things · ⟁ Augur
Sensors are just data sources
pending render
9:16 · TikTok · Instagram Reels · YouTube Shorts · Facebook Reels · Stories · Threads · Pinterest
pending render
1:1 · Instagram feed · Facebook · X/Twitter · Bluesky · LinkedIn feed
pending render
16:9 · YouTube · X card · LinkedIn video · Blog (embed)
cuts · 9LinkedIn 1:1 · 120s · LinkedInDocX 1:1 · 120s · XThreadCardYouTube Shorts 9:16 · 60s · SceneReelInstagram (Reels · feed) 9:16 · 90s · StoryReelFacebook (Reels · feed) 9:16 · 90s · SceneReelThreads 1:1 · 90s · SceneReelTikTok 9:16 · 60s · TikTokNativePinterest 9:16 · 60s · PinterestPinBluesky 1:1 · 60s · SceneReel
storyboard → brief + scenesemerging tech · Staying current without burning out (triage, don't chase) · ⟁ Augur
Triage, do not chase
pending render
9:16 · TikTok · Instagram Reels · YouTube Shorts · Facebook Reels · Stories · Threads · Pinterest
pending render
1:1 · Instagram feed · Facebook · X/Twitter · Bluesky · LinkedIn feed
pending render
16:9 · YouTube · X card · LinkedIn video · Blog (embed)
cuts · 9LinkedIn 1:1 · 120s · LinkedInDocX 1:1 · 120s · XThreadCardYouTube Shorts 9:16 · 60s · SceneReelInstagram (Reels · feed) 9:16 · 90s · StoryReelFacebook (Reels · feed) 9:16 · 90s · SceneReelThreads 1:1 · 90s · SceneReelTikTok 9:16 · 60s · TikTokNativePinterest 9:16 · 60s · PinterestPinBluesky 1:1 · 60s · SceneReel
storyboard → brief + scenesEmail (Resend, owned list)
The day's note — EmailBlockStack · rendered at send
- header 600×300 [html/image] · logo + nav; links live; dark-mode safe
- hero 600×600 [gif/image/html-motion] · the week's 1:1 cut as a loop, first-frame poster fallback, alt text, hosted URL
- secondary 600×400 [html/image/gif] · the one promise in copy, single accent; optional
- tertiary 600×250 [html] · the DOOR - a bulletproof button to the segment's door with the UTM spine; never a generic 'learn more'
- footer 600×200 [html] · logo · links · unsubscribe · NAP
- From nameauthored the name the inbox shows BEFORE the subject, and the first thing a reader decides on. Keep it the same across sends — changing it costs the recognition that earns the open. Never 'noreply'.
- Subjectauthored ≤ 50 chars
- Preheaderauthored ≤ 90 chars; finishes the subject's sentence
- Bodyauthored the day's letter; reads-at-the-kitchen-table register
- CTA doorauthored a segment door id; the tertiary block renders it
- Hero assetauthored the hosted GIF URL + poster + alt text
- Plain-text twin derived from the body; every client gets one
rules · subject ≤ 50 · preheader ≤ 90 · from name set, and the same one as last send · dark mode tested · Outlook shows the poster (no GIF motion) · total HTML < 102 KB (Gmail clips) · plain-text twin present · list = contacts with a consent receipt only · send window = the recipient's morning in their zone, never one flat hour · List-Unsubscribe + List-Unsubscribe-Post on EVERY bulk send: `List-Unsubscribe: <https://…>, <mailto:…>` and `List-Unsubscribe-Post: List-Unsubscribe=One-Click`. Gmail and Yahoo have required one-click unsubscribe of bulk senders since February 2024; without the headers the mail is throttled or spam-foldered no matter how good the copy is. This is the HEADER, set at the send — NOT the same thing as the rule below, which is what happens after somebody clicks it. · unsubscribe honoured at the consent root · every link carries the UTM spine, not only the door — an untagged link in the body is a click the reporting never sees
test matrix · dark mode · Outlook desktop (poster) · Gmail mobile · Apple Mail (motion) · 102 KB clip check
acceptance · gate verify_channel_specs.py#CHANNEL-SPECS PASS · review by executive-manager
Blog (static .xyz + Duda .com)
The week's article — Article
- H1authored the episode's argument as a sentence; ≤ 70 chars
- Meta descriptionauthored ≤ 155 chars and UNIQUE across the blog — the line the search result shows, written as a promise, NOT the first 155 characters of the lede. Change it and the SERP snippet changes; leave it derived and two articles that open alike collide (the 2026-08-25 crawl reported description_duplicate on 8 URLs).
- Authorauthored the byline the page shows and the JSON-LD Person points at; must be a real person with a live author page (/blog/author/<slug>). An article with no named author is the E-E-A-T signal Google's quality guidance asks for and we do not send.
- Published dateauthored ISO date; renders as article:published_time and BlogPosting.datePublished, and orders the listing and the sitemap <lastmod>. Move it and the article moves in the feed.
- Updated dateauthored ISO date, only when the article actually changed; renders as BlogPosting.dateModified. Stamp it on an unchanged article and the freshness signal is a lie.
- OG image 1200×630 the chapter card; no typed name
- In-article hero 1600×900 optional
- 16:9 video embed the week's 16:9 cut, in-article
- Alt textauthored one line per in-article image, describing what the image SHOWS, not what it is called — the text a screen reader reads and the only thing an image search can read. An image authored with no alt text is not rendered.
- Headingsauthored one per chapter; the scan tells the story
- Canonical rel=canonical to the .xyz static page; syndication points back
- Internal linksauthored links to other articles or office pages, in the body, beyond the door CTA — a page nothing links to is an orphan and the crawler reports it as one (sitemap_orphan). Every link carries the UTM spine.
- Door linkauthored the segment door with the UTM spine, once, near the end
- Schema (JSON-LD) Organization + Person(author) + BlogPosting + BreadcrumbList, derived from the layers above. NO templated FAQPage/HowTo — those rich results were deprecated in May 2026 and FAQPage is only honest where a visible Q&A exists. Change the author, dates or description and this changes with them, because it reads them.
- Reading time derived
rules · h1 ≤ 70 · title UNIQUE across the blog (the ≤ 60-char SEO title, not just the h1 — two articles clamped to the same 60 characters are one page to a search engine) · meta description ≤ 155 and UNIQUE across the blog · author named, with a live author page · published date present; updated date only when the article changed · canonical present · one door link · at least one internal link in the body, beyond the door CTA · every image has alt text · JSON-LD present and derived from the authored layers (no hand-typed schema)
acceptance · gate verify_channel_specs.py#CHANNEL-SPECS PASS · review by creative-lead
brand · Email Hero GIF · ⟁ Signum
The part that aims it
pending render
9:16 · TikTok · Instagram Reels · YouTube Shorts · Facebook Reels · Stories · Threads · Pinterest
pending render
1:1 · Instagram feed · Facebook · X/Twitter · Bluesky · LinkedIn feed
pending render
16:9 · YouTube · X card · LinkedIn video · Blog (embed)
cuts · 1+ Email (Resend, owned list)
storyboard → brief + scenesemerging tech · longform · ⟁ Augur
A green build proves nothing
pending render
16:9 · YouTube (long-form)
cuts · 2YouTube Shorts 9:16 · 60s · SceneReel+ Blog (static .xyz + Duda .com)
storyboard → brief + scenesmultimedia · Live Streaming · ⟁ Lumen
Live is proof you are real
pending render
9:16 · TikTok · Instagram Reels · YouTube Shorts · Facebook Reels · Stories · Threads · Pinterest
pending render
1:1 · Instagram feed · Facebook · X/Twitter · Bluesky · LinkedIn feed
pending render
16:9 · YouTube · X card · LinkedIn video · Blog (embed)
cuts · 9LinkedIn 1:1 · 120s · LinkedInDocX 1:1 · 120s · XThreadCardYouTube Shorts 9:16 · 60s · SceneReelInstagram (Reels · feed) 9:16 · 90s · StoryReelFacebook (Reels · feed) 9:16 · 90s · SceneReelThreads 1:1 · 90s · SceneReelTikTok 9:16 · 60s · TikTokNativePinterest 9:16 · 60s · PinterestPinBluesky 1:1 · 60s · SceneReel
storyboard → brief + scenesit dev · Product Management · ⟁ Faber
Deciding what not to build
pending render
9:16 · TikTok · Instagram Reels · YouTube Shorts · Facebook Reels · Stories · Threads · Pinterest
pending render
1:1 · Instagram feed · Facebook · X/Twitter · Bluesky · LinkedIn feed
pending render
16:9 · YouTube · X card · LinkedIn video · Blog (embed)
cuts · 9LinkedIn 1:1 · 120s · LinkedInDocX 1:1 · 120s · XThreadCardYouTube Shorts 9:16 · 60s · SceneReelInstagram (Reels · feed) 9:16 · 90s · StoryReelFacebook (Reels · feed) 9:16 · 90s · SceneReelThreads 1:1 · 90s · SceneReelTikTok 9:16 · 60s · TikTokNativePinterest 9:16 · 60s · PinterestPinBluesky 1:1 · 60s · SceneReel
storyboard → brief + scenesmultimedia · Creative Workflows (the AI content engine) · ⟁ Lumen
One idea, nine native outputs
pending render
9:16 · TikTok · Instagram Reels · YouTube Shorts · Facebook Reels · Stories · Threads · Pinterest
pending render
1:1 · Instagram feed · Facebook · X/Twitter · Bluesky · LinkedIn feed
pending render
16:9 · YouTube · X card · LinkedIn video · Blog (embed)
cuts · 9LinkedIn 1:1 · 120s · LinkedInDocX 1:1 · 120s · XThreadCardYouTube Shorts 9:16 · 60s · SceneReelInstagram (Reels · feed) 9:16 · 90s · StoryReelFacebook (Reels · feed) 9:16 · 90s · SceneReelThreads 1:1 · 90s · SceneReelTikTok 9:16 · 60s · TikTokNativePinterest 9:16 · 60s · PinterestPinBluesky 1:1 · 60s · SceneReel
storyboard → brief + scenesstaff training · Community Incubator + Temerarii Academy (learn · build · connect) · ⟁ Magister
Learn by shipping, not watching
pending render
9:16 · TikTok · Instagram Reels · YouTube Shorts · Facebook Reels · Stories · Threads · Pinterest
pending render
1:1 · Instagram feed · Facebook · X/Twitter · Bluesky · LinkedIn feed
pending render
16:9 · YouTube · X card · LinkedIn video · Blog (embed)
cuts · 9LinkedIn 1:1 · 120s · LinkedInDocX 1:1 · 120s · XThreadCardYouTube Shorts 9:16 · 60s · SceneReelInstagram (Reels · feed) 9:16 · 90s · StoryReelFacebook (Reels · feed) 9:16 · 90s · SceneReelThreads 1:1 · 90s · SceneReelTikTok 9:16 · 60s · TikTokNativePinterest 9:16 · 60s · PinterestPinBluesky 1:1 · 60s · SceneReel
storyboard → brief + scenesstrategic relations · Minus the Hype · ⟁ Nexus
A dashboard is not a decision
pending render
9:16 · TikTok · Instagram Reels · YouTube Shorts · Facebook Reels · Stories · Threads · Pinterest
pending render
1:1 · Instagram feed · Facebook · X/Twitter · Bluesky · LinkedIn feed
pending render
16:9 · YouTube · X card · LinkedIn video · Blog (embed)
cuts · 9LinkedIn 1:1 · 120s · LinkedInDocX 1:1 · 120s · XThreadCardYouTube Shorts 9:16 · 60s · SceneReelInstagram (Reels · feed) 9:16 · 90s · StoryReelFacebook (Reels · feed) 9:16 · 90s · SceneReelThreads 1:1 · 90s · SceneReelTikTok 9:16 · 60s · TikTokNativePinterest 9:16 · 60s · PinterestPinBluesky 1:1 · 60s · SceneReel
storyboard → brief + scenesEmail (Resend, owned list)
The day's note — EmailBlockStack · rendered at send
- header 600×300 [html/image] · logo + nav; links live; dark-mode safe
- hero 600×600 [gif/image/html-motion] · the week's 1:1 cut as a loop, first-frame poster fallback, alt text, hosted URL
- secondary 600×400 [html/image/gif] · the one promise in copy, single accent; optional
- tertiary 600×250 [html] · the DOOR - a bulletproof button to the segment's door with the UTM spine; never a generic 'learn more'
- footer 600×200 [html] · logo · links · unsubscribe · NAP
- From nameauthored the name the inbox shows BEFORE the subject, and the first thing a reader decides on. Keep it the same across sends — changing it costs the recognition that earns the open. Never 'noreply'.
- Subjectauthored ≤ 50 chars
- Preheaderauthored ≤ 90 chars; finishes the subject's sentence
- Bodyauthored the day's letter; reads-at-the-kitchen-table register
- CTA doorauthored a segment door id; the tertiary block renders it
- Hero assetauthored the hosted GIF URL + poster + alt text
- Plain-text twin derived from the body; every client gets one
rules · subject ≤ 50 · preheader ≤ 90 · from name set, and the same one as last send · dark mode tested · Outlook shows the poster (no GIF motion) · total HTML < 102 KB (Gmail clips) · plain-text twin present · list = contacts with a consent receipt only · send window = the recipient's morning in their zone, never one flat hour · List-Unsubscribe + List-Unsubscribe-Post on EVERY bulk send: `List-Unsubscribe: <https://…>, <mailto:…>` and `List-Unsubscribe-Post: List-Unsubscribe=One-Click`. Gmail and Yahoo have required one-click unsubscribe of bulk senders since February 2024; without the headers the mail is throttled or spam-foldered no matter how good the copy is. This is the HEADER, set at the send — NOT the same thing as the rule below, which is what happens after somebody clicks it. · unsubscribe honoured at the consent root · every link carries the UTM spine, not only the door — an untagged link in the body is a click the reporting never sees
test matrix · dark mode · Outlook desktop (poster) · Gmail mobile · Apple Mail (motion) · 102 KB clip check
acceptance · gate verify_channel_specs.py#CHANNEL-SPECS PASS · review by executive-manager
Blog (static .xyz + Duda .com)
The week's article — Article
- H1authored the episode's argument as a sentence; ≤ 70 chars
- Meta descriptionauthored ≤ 155 chars and UNIQUE across the blog — the line the search result shows, written as a promise, NOT the first 155 characters of the lede. Change it and the SERP snippet changes; leave it derived and two articles that open alike collide (the 2026-08-25 crawl reported description_duplicate on 8 URLs).
- Authorauthored the byline the page shows and the JSON-LD Person points at; must be a real person with a live author page (/blog/author/<slug>). An article with no named author is the E-E-A-T signal Google's quality guidance asks for and we do not send.
- Published dateauthored ISO date; renders as article:published_time and BlogPosting.datePublished, and orders the listing and the sitemap <lastmod>. Move it and the article moves in the feed.
- Updated dateauthored ISO date, only when the article actually changed; renders as BlogPosting.dateModified. Stamp it on an unchanged article and the freshness signal is a lie.
- OG image 1200×630 the chapter card; no typed name
- In-article hero 1600×900 optional
- 16:9 video embed the week's 16:9 cut, in-article
- Alt textauthored one line per in-article image, describing what the image SHOWS, not what it is called — the text a screen reader reads and the only thing an image search can read. An image authored with no alt text is not rendered.
- Headingsauthored one per chapter; the scan tells the story
- Canonical rel=canonical to the .xyz static page; syndication points back
- Internal linksauthored links to other articles or office pages, in the body, beyond the door CTA — a page nothing links to is an orphan and the crawler reports it as one (sitemap_orphan). Every link carries the UTM spine.
- Door linkauthored the segment door with the UTM spine, once, near the end
- Schema (JSON-LD) Organization + Person(author) + BlogPosting + BreadcrumbList, derived from the layers above. NO templated FAQPage/HowTo — those rich results were deprecated in May 2026 and FAQPage is only honest where a visible Q&A exists. Change the author, dates or description and this changes with them, because it reads them.
- Reading time derived
rules · h1 ≤ 70 · title UNIQUE across the blog (the ≤ 60-char SEO title, not just the h1 — two articles clamped to the same 60 characters are one page to a search engine) · meta description ≤ 155 and UNIQUE across the blog · author named, with a live author page · published date present; updated date only when the article changed · canonical present · one door link · at least one internal link in the body, beyond the door CTA · every image has alt text · JSON-LD present and derived from the authored layers (no hand-typed schema)
acceptance · gate verify_channel_specs.py#CHANNEL-SPECS PASS · review by creative-lead
brand · Email Hero GIF · ⟁ Signum
The part that sustains it
pending render
9:16 · TikTok · Instagram Reels · YouTube Shorts · Facebook Reels · Stories · Threads · Pinterest
pending render
1:1 · Instagram feed · Facebook · X/Twitter · Bluesky · LinkedIn feed
pending render
16:9 · YouTube · X card · LinkedIn video · Blog (embed)
cuts · 1+ Email (Resend, owned list)
storyboard → brief + scenesperformance · longform · ⟁ Mensor
Blocked, in public
pending render
16:9 · YouTube (long-form)
cuts · 2YouTube Shorts 9:16 · 60s · SceneReel+ Blog (static .xyz + Duda .com)
storyboard → brief + scenesbrand · SMS GIF · ⟁ Signum
Four parts, one system
pending render
9:16 · TikTok · Instagram Reels · YouTube Shorts · Facebook Reels · Stories · Threads · Pinterest
pending render
1:1 · Instagram feed · Facebook · X/Twitter · Bluesky · LinkedIn feed
pending render
16:9 · YouTube · X card · LinkedIn video · Blog (embed)
cuts · 1+ SMS / MMS (Twilio)
storyboard → brief + scenesmultimedia · Screenwriting · ⟁ Lumen
Structure before sentences
pending render
9:16 · TikTok · Instagram Reels · YouTube Shorts · Facebook Reels · Stories · Threads · Pinterest
pending render
1:1 · Instagram feed · Facebook · X/Twitter · Bluesky · LinkedIn feed
pending render
16:9 · YouTube · X card · LinkedIn video · Blog (embed)
cuts · 9LinkedIn 1:1 · 120s · LinkedInDocX 1:1 · 120s · XThreadCardYouTube Shorts 9:16 · 60s · SceneReelInstagram (Reels · feed) 9:16 · 90s · StoryReelFacebook (Reels · feed) 9:16 · 90s · SceneReelThreads 1:1 · 90s · SceneReelTikTok 9:16 · 60s · TikTokNativePinterest 9:16 · 60s · PinterestPinBluesky 1:1 · 60s · SceneReel
storyboard → brief + scenesit dev · Cyber Security · ⟁ Faber
Security is a maintenance habit
pending render
9:16 · TikTok · Instagram Reels · YouTube Shorts · Facebook Reels · Stories · Threads · Pinterest
pending render
1:1 · Instagram feed · Facebook · X/Twitter · Bluesky · LinkedIn feed
pending render
16:9 · YouTube · X card · LinkedIn video · Blog (embed)
cuts · 9LinkedIn 1:1 · 120s · LinkedInDocX 1:1 · 120s · XThreadCardYouTube Shorts 9:16 · 60s · SceneReelInstagram (Reels · feed) 9:16 · 90s · StoryReelFacebook (Reels · feed) 9:16 · 90s · SceneReelThreads 1:1 · 90s · SceneReelTikTok 9:16 · 60s · TikTokNativePinterest 9:16 · 60s · PinterestPinBluesky 1:1 · 60s · SceneReel
storyboard → brief + scenesit dev · The Machine — build-in-public (demystifying data/AI) · ⟁ Faber
The office is open on purpose
pending render
9:16 · TikTok · Instagram Reels · YouTube Shorts · Facebook Reels · Stories · Threads · Pinterest
pending render
1:1 · Instagram feed · Facebook · X/Twitter · Bluesky · LinkedIn feed
pending render
16:9 · YouTube · X card · LinkedIn video · Blog (embed)
cuts · 9LinkedIn 1:1 · 120s · LinkedInDocX 1:1 · 120s · XThreadCardYouTube Shorts 9:16 · 60s · SceneReelInstagram (Reels · feed) 9:16 · 90s · StoryReelFacebook (Reels · feed) 9:16 · 90s · SceneReelThreads 1:1 · 90s · SceneReelTikTok 9:16 · 60s · TikTokNativePinterest 9:16 · 60s · PinterestPinBluesky 1:1 · 60s · SceneReel
storyboard → brief + scenesstaff training · Ask the Operator · ⟁ Magister
Can you just run it?
pending render
9:16 · TikTok · Instagram Reels · YouTube Shorts · Facebook Reels · Stories · Threads · Pinterest
pending render
1:1 · Instagram feed · Facebook · X/Twitter · Bluesky · LinkedIn feed
pending render
16:9 · YouTube · X card · LinkedIn video · Blog (embed)
cuts · 9LinkedIn 1:1 · 120s · LinkedInDocX 1:1 · 120s · XThreadCardYouTube Shorts 9:16 · 60s · SceneReelInstagram (Reels · feed) 9:16 · 90s · StoryReelFacebook (Reels · feed) 9:16 · 90s · SceneReelThreads 1:1 · 90s · SceneReelTikTok 9:16 · 60s · TikTokNativePinterest 9:16 · 60s · PinterestPinBluesky 1:1 · 60s · SceneReel
storyboard → brief + scenesmultimedia · The Stack · ⟁ Lumen
The number, or the vibe
pending render
9:16 · TikTok · Instagram Reels · YouTube Shorts · Facebook Reels · Stories · Threads · Pinterest
pending render
1:1 · Instagram feed · Facebook · X/Twitter · Bluesky · LinkedIn feed
pending render
16:9 · YouTube · X card · LinkedIn video · Blog (embed)
cuts · 9LinkedIn 1:1 · 120s · LinkedInDocX 1:1 · 120s · XThreadCardYouTube Shorts 9:16 · 60s · SceneReelInstagram (Reels · feed) 9:16 · 90s · StoryReelFacebook (Reels · feed) 9:16 · 90s · SceneReelThreads 1:1 · 90s · SceneReelTikTok 9:16 · 60s · TikTokNativePinterest 9:16 · 60s · PinterestPinBluesky 1:1 · 60s · SceneReel
storyboard → brief + scenesEmail (Resend, owned list)
The day's note — EmailBlockStack · rendered at send
- header 600×300 [html/image] · logo + nav; links live; dark-mode safe
- hero 600×600 [gif/image/html-motion] · the week's 1:1 cut as a loop, first-frame poster fallback, alt text, hosted URL
- secondary 600×400 [html/image/gif] · the one promise in copy, single accent; optional
- tertiary 600×250 [html] · the DOOR - a bulletproof button to the segment's door with the UTM spine; never a generic 'learn more'
- footer 600×200 [html] · logo · links · unsubscribe · NAP
- From nameauthored the name the inbox shows BEFORE the subject, and the first thing a reader decides on. Keep it the same across sends — changing it costs the recognition that earns the open. Never 'noreply'.
- Subjectauthored ≤ 50 chars
- Preheaderauthored ≤ 90 chars; finishes the subject's sentence
- Bodyauthored the day's letter; reads-at-the-kitchen-table register
- CTA doorauthored a segment door id; the tertiary block renders it
- Hero assetauthored the hosted GIF URL + poster + alt text
- Plain-text twin derived from the body; every client gets one
rules · subject ≤ 50 · preheader ≤ 90 · from name set, and the same one as last send · dark mode tested · Outlook shows the poster (no GIF motion) · total HTML < 102 KB (Gmail clips) · plain-text twin present · list = contacts with a consent receipt only · send window = the recipient's morning in their zone, never one flat hour · List-Unsubscribe + List-Unsubscribe-Post on EVERY bulk send: `List-Unsubscribe: <https://…>, <mailto:…>` and `List-Unsubscribe-Post: List-Unsubscribe=One-Click`. Gmail and Yahoo have required one-click unsubscribe of bulk senders since February 2024; without the headers the mail is throttled or spam-foldered no matter how good the copy is. This is the HEADER, set at the send — NOT the same thing as the rule below, which is what happens after somebody clicks it. · unsubscribe honoured at the consent root · every link carries the UTM spine, not only the door — an untagged link in the body is a click the reporting never sees
test matrix · dark mode · Outlook desktop (poster) · Gmail mobile · Apple Mail (motion) · 102 KB clip check
acceptance · gate verify_channel_specs.py#CHANNEL-SPECS PASS · review by executive-manager
SMS / MMS (Twilio)
The day's text — SmsMms · rendered at send
- Bodyauthored ≤ 160 chars including the opt-out — but that is the GSM-7 limit. One emoji or one curly apostrophe flips the message to UCS-2 and the real limit is 70. One idea, one link.
- MMS loop 720×720 the 1:1 cut as a short loop; a still if the carrier strips motion
- Linkauthored one shortened link with the UTM spine, to a door
rules · body ≤ 160 incl. opt-out · encoding: GSM-7 → 160 in one message, 153 per segment when concatenated; UCS-2 → 70 and 67. One emoji or one curly apostrophe (’ “ ” — …) flips the whole message to UCS-2 and drops the limit 160 → 70 · segments: 1 — past the single-message limit for its encoding the message is billed as 2+ segments and any carrier that does not reassemble truncates it · HELP and STOP both answered — US carriers (CTIA messaging principles) require the HELP keyword alongside opt-out, not STOP alone · quiet hours (recipient zone) · sender id registered · 2 per week (Tue · Fri) · list = receipts only
acceptance · gate verify_channel_specs.py#CHANNEL-SPECS PASS · review by executive-manager
Blog (static .xyz + Duda .com)
The week's article — Article
- H1authored the episode's argument as a sentence; ≤ 70 chars
- Meta descriptionauthored ≤ 155 chars and UNIQUE across the blog — the line the search result shows, written as a promise, NOT the first 155 characters of the lede. Change it and the SERP snippet changes; leave it derived and two articles that open alike collide (the 2026-08-25 crawl reported description_duplicate on 8 URLs).
- Authorauthored the byline the page shows and the JSON-LD Person points at; must be a real person with a live author page (/blog/author/<slug>). An article with no named author is the E-E-A-T signal Google's quality guidance asks for and we do not send.
- Published dateauthored ISO date; renders as article:published_time and BlogPosting.datePublished, and orders the listing and the sitemap <lastmod>. Move it and the article moves in the feed.
- Updated dateauthored ISO date, only when the article actually changed; renders as BlogPosting.dateModified. Stamp it on an unchanged article and the freshness signal is a lie.
- OG image 1200×630 the chapter card; no typed name
- In-article hero 1600×900 optional
- 16:9 video embed the week's 16:9 cut, in-article
- Alt textauthored one line per in-article image, describing what the image SHOWS, not what it is called — the text a screen reader reads and the only thing an image search can read. An image authored with no alt text is not rendered.
- Headingsauthored one per chapter; the scan tells the story
- Canonical rel=canonical to the .xyz static page; syndication points back
- Internal linksauthored links to other articles or office pages, in the body, beyond the door CTA — a page nothing links to is an orphan and the crawler reports it as one (sitemap_orphan). Every link carries the UTM spine.
- Door linkauthored the segment door with the UTM spine, once, near the end
- Schema (JSON-LD) Organization + Person(author) + BlogPosting + BreadcrumbList, derived from the layers above. NO templated FAQPage/HowTo — those rich results were deprecated in May 2026 and FAQPage is only honest where a visible Q&A exists. Change the author, dates or description and this changes with them, because it reads them.
- Reading time derived
rules · h1 ≤ 70 · title UNIQUE across the blog (the ≤ 60-char SEO title, not just the h1 — two articles clamped to the same 60 characters are one page to a search engine) · meta description ≤ 155 and UNIQUE across the blog · author named, with a live author page · published date present; updated date only when the article changed · canonical present · one door link · at least one internal link in the body, beyond the door CTA · every image has alt text · JSON-LD present and derived from the authored layers (no hand-typed schema)
acceptance · gate verify_channel_specs.py#CHANNEL-SPECS PASS · review by creative-lead
brand · Email Hero GIF · ⟁ Signum
The part that feeds it
pending render
9:16 · TikTok · Instagram Reels · YouTube Shorts · Facebook Reels · Stories · Threads · Pinterest
pending render
1:1 · Instagram feed · Facebook · X/Twitter · Bluesky · LinkedIn feed
pending render
16:9 · YouTube · X card · LinkedIn video · Blog (embed)
cuts · 1+ Email (Resend, owned list)
storyboard → brief + scenesmultimedia · longform · ⟁ Lumen
What a creative authors on a cut
pending render
16:9 · YouTube (long-form)
cuts · 2YouTube Shorts 9:16 · 60s · SceneReel+ Blog (static .xyz + Duda .com)
storyboard → brief + scenesmultimedia · Interviews & Discussion · ⟁ Lumen
An interview is a research tool
pending render
9:16 · TikTok · Instagram Reels · YouTube Shorts · Facebook Reels · Stories · Threads · Pinterest
pending render
1:1 · Instagram feed · Facebook · X/Twitter · Bluesky · LinkedIn feed
pending render
16:9 · YouTube · X card · LinkedIn video · Blog (embed)
cuts · 9LinkedIn 1:1 · 120s · LinkedInDocX 1:1 · 120s · XThreadCardYouTube Shorts 9:16 · 60s · SceneReelInstagram (Reels · feed) 9:16 · 90s · StoryReelFacebook (Reels · feed) 9:16 · 90s · SceneReelThreads 1:1 · 90s · SceneReelTikTok 9:16 · 60s · TikTokNativePinterest 9:16 · 60s · PinterestPinBluesky 1:1 · 60s · SceneReel
storyboard → brief + scenesit dev · Business Intelligence · ⟁ Faber
BI is one agreed number
pending render
9:16 · TikTok · Instagram Reels · YouTube Shorts · Facebook Reels · Stories · Threads · Pinterest
pending render
1:1 · Instagram feed · Facebook · X/Twitter · Bluesky · LinkedIn feed
pending render
16:9 · YouTube · X card · LinkedIn video · Blog (embed)
cuts · 9LinkedIn 1:1 · 120s · LinkedInDocX 1:1 · 120s · XThreadCardYouTube Shorts 9:16 · 60s · SceneReelInstagram (Reels · feed) 9:16 · 90s · StoryReelFacebook (Reels · feed) 9:16 · 90s · SceneReelThreads 1:1 · 90s · SceneReelTikTok 9:16 · 60s · TikTokNativePinterest 9:16 · 60s · PinterestPinBluesky 1:1 · 60s · SceneReel
storyboard → brief + scenesit dev · Custom apps (runnable tools) · ⟁ Faber
A tool per workflow
pending render
9:16 · TikTok · Instagram Reels · YouTube Shorts · Facebook Reels · Stories · Threads · Pinterest
pending render
1:1 · Instagram feed · Facebook · X/Twitter · Bluesky · LinkedIn feed
pending render
16:9 · YouTube · X card · LinkedIn video · Blog (embed)
cuts · 9LinkedIn 1:1 · 120s · LinkedInDocX 1:1 · 120s · XThreadCardYouTube Shorts 9:16 · 60s · SceneReelInstagram (Reels · feed) 9:16 · 90s · StoryReelFacebook (Reels · feed) 9:16 · 90s · SceneReelThreads 1:1 · 90s · SceneReelTikTok 9:16 · 60s · TikTokNativePinterest 9:16 · 60s · PinterestPinBluesky 1:1 · 60s · SceneReel
storyboard → brief + scenesperformance · Strategy · ⟁ Mensor
Strategy is a set of nos
pending render
9:16 · TikTok · Instagram Reels · YouTube Shorts · Facebook Reels · Stories · Threads · Pinterest
pending render
1:1 · Instagram feed · Facebook · X/Twitter · Bluesky · LinkedIn feed
pending render
16:9 · YouTube · X card · LinkedIn video · Blog (embed)
cuts · 9LinkedIn 1:1 · 120s · LinkedInDocX 1:1 · 120s · XThreadCardYouTube Shorts 9:16 · 60s · SceneReelInstagram (Reels · feed) 9:16 · 90s · StoryReelFacebook (Reels · feed) 9:16 · 90s · SceneReelThreads 1:1 · 90s · SceneReelTikTok 9:16 · 60s · TikTokNativePinterest 9:16 · 60s · PinterestPinBluesky 1:1 · 60s · SceneReel
storyboard → brief + scenesstaff training · Build Log · ⟁ Magister
Build log: tracing the door
pending render
9:16 · TikTok · Instagram Reels · YouTube Shorts · Facebook Reels · Stories · Threads · Pinterest
pending render
1:1 · Instagram feed · Facebook · X/Twitter · Bluesky · LinkedIn feed
pending render
16:9 · YouTube · X card · LinkedIn video · Blog (embed)
cuts · 9LinkedIn 1:1 · 120s · LinkedInDocX 1:1 · 120s · XThreadCardYouTube Shorts 9:16 · 60s · SceneReelInstagram (Reels · feed) 9:16 · 90s · StoryReelFacebook (Reels · feed) 9:16 · 90s · SceneReelThreads 1:1 · 90s · SceneReelTikTok 9:16 · 60s · TikTokNativePinterest 9:16 · 60s · PinterestPinBluesky 1:1 · 60s · SceneReel
storyboard → brief + scenesEmail (Resend, owned list)
The day's note — EmailBlockStack · rendered at send
- header 600×300 [html/image] · logo + nav; links live; dark-mode safe
- hero 600×600 [gif/image/html-motion] · the week's 1:1 cut as a loop, first-frame poster fallback, alt text, hosted URL
- secondary 600×400 [html/image/gif] · the one promise in copy, single accent; optional
- tertiary 600×250 [html] · the DOOR - a bulletproof button to the segment's door with the UTM spine; never a generic 'learn more'
- footer 600×200 [html] · logo · links · unsubscribe · NAP
- From nameauthored the name the inbox shows BEFORE the subject, and the first thing a reader decides on. Keep it the same across sends — changing it costs the recognition that earns the open. Never 'noreply'.
- Subjectauthored ≤ 50 chars
- Preheaderauthored ≤ 90 chars; finishes the subject's sentence
- Bodyauthored the day's letter; reads-at-the-kitchen-table register
- CTA doorauthored a segment door id; the tertiary block renders it
- Hero assetauthored the hosted GIF URL + poster + alt text
- Plain-text twin derived from the body; every client gets one
rules · subject ≤ 50 · preheader ≤ 90 · from name set, and the same one as last send · dark mode tested · Outlook shows the poster (no GIF motion) · total HTML < 102 KB (Gmail clips) · plain-text twin present · list = contacts with a consent receipt only · send window = the recipient's morning in their zone, never one flat hour · List-Unsubscribe + List-Unsubscribe-Post on EVERY bulk send: `List-Unsubscribe: <https://…>, <mailto:…>` and `List-Unsubscribe-Post: List-Unsubscribe=One-Click`. Gmail and Yahoo have required one-click unsubscribe of bulk senders since February 2024; without the headers the mail is throttled or spam-foldered no matter how good the copy is. This is the HEADER, set at the send — NOT the same thing as the rule below, which is what happens after somebody clicks it. · unsubscribe honoured at the consent root · every link carries the UTM spine, not only the door — an untagged link in the body is a click the reporting never sees
test matrix · dark mode · Outlook desktop (poster) · Gmail mobile · Apple Mail (motion) · 102 KB clip check
acceptance · gate verify_channel_specs.py#CHANNEL-SPECS PASS · review by executive-manager
Blog (static .xyz + Duda .com)
The week's article — Article
- H1authored the episode's argument as a sentence; ≤ 70 chars
- Meta descriptionauthored ≤ 155 chars and UNIQUE across the blog — the line the search result shows, written as a promise, NOT the first 155 characters of the lede. Change it and the SERP snippet changes; leave it derived and two articles that open alike collide (the 2026-08-25 crawl reported description_duplicate on 8 URLs).
- Authorauthored the byline the page shows and the JSON-LD Person points at; must be a real person with a live author page (/blog/author/<slug>). An article with no named author is the E-E-A-T signal Google's quality guidance asks for and we do not send.
- Published dateauthored ISO date; renders as article:published_time and BlogPosting.datePublished, and orders the listing and the sitemap <lastmod>. Move it and the article moves in the feed.
- Updated dateauthored ISO date, only when the article actually changed; renders as BlogPosting.dateModified. Stamp it on an unchanged article and the freshness signal is a lie.
- OG image 1200×630 the chapter card; no typed name
- In-article hero 1600×900 optional
- 16:9 video embed the week's 16:9 cut, in-article
- Alt textauthored one line per in-article image, describing what the image SHOWS, not what it is called — the text a screen reader reads and the only thing an image search can read. An image authored with no alt text is not rendered.
- Headingsauthored one per chapter; the scan tells the story
- Canonical rel=canonical to the .xyz static page; syndication points back
- Internal linksauthored links to other articles or office pages, in the body, beyond the door CTA — a page nothing links to is an orphan and the crawler reports it as one (sitemap_orphan). Every link carries the UTM spine.
- Door linkauthored the segment door with the UTM spine, once, near the end
- Schema (JSON-LD) Organization + Person(author) + BlogPosting + BreadcrumbList, derived from the layers above. NO templated FAQPage/HowTo — those rich results were deprecated in May 2026 and FAQPage is only honest where a visible Q&A exists. Change the author, dates or description and this changes with them, because it reads them.
- Reading time derived
rules · h1 ≤ 70 · title UNIQUE across the blog (the ≤ 60-char SEO title, not just the h1 — two articles clamped to the same 60 characters are one page to a search engine) · meta description ≤ 155 and UNIQUE across the blog · author named, with a live author page · published date present; updated date only when the article changed · canonical present · one door link · at least one internal link in the body, beyond the door CTA · every image has alt text · JSON-LD present and derived from the authored layers (no hand-typed schema)
acceptance · gate verify_channel_specs.py#CHANNEL-SPECS PASS · review by creative-lead
brand · Email Hero GIF · ⟁ Signum
The part that corrects it
pending render
9:16 · TikTok · Instagram Reels · YouTube Shorts · Facebook Reels · Stories · Threads · Pinterest
pending render
1:1 · Instagram feed · Facebook · X/Twitter · Bluesky · LinkedIn feed
pending render
16:9 · YouTube · X card · LinkedIn video · Blog (embed)
cuts · 1+ Email (Resend, owned list)
storyboard → brief + scenesit dev · longform · ⟁ Faber
The board that replaced two subscriptions
pending render
16:9 · YouTube (long-form)
cuts · 2YouTube Shorts 9:16 · 60s · SceneReel+ Blog (static .xyz + Duda .com)
storyboard → brief + scenesmultimedia · Commercial Advertisement · ⟁ Lumen
A commercial is a promise
pending render
9:16 · TikTok · Instagram Reels · YouTube Shorts · Facebook Reels · Stories · Threads · Pinterest
pending render
1:1 · Instagram feed · Facebook · X/Twitter · Bluesky · LinkedIn feed
pending render
16:9 · YouTube · X card · LinkedIn video · Blog (embed)
cuts · 9LinkedIn 1:1 · 120s · LinkedInDocX 1:1 · 120s · XThreadCardYouTube Shorts 9:16 · 60s · SceneReelInstagram (Reels · feed) 9:16 · 90s · StoryReelFacebook (Reels · feed) 9:16 · 90s · SceneReelThreads 1:1 · 90s · SceneReelTikTok 9:16 · 60s · TikTokNativePinterest 9:16 · 60s · PinterestPinBluesky 1:1 · 60s · SceneReel
storyboard → brief + scenesstaff training · Growth & Performance Marketing · ⟁ Magister
Teach the loop, not tactics
pending render
9:16 · TikTok · Instagram Reels · YouTube Shorts · Facebook Reels · Stories · Threads · Pinterest
pending render
1:1 · Instagram feed · Facebook · X/Twitter · Bluesky · LinkedIn feed
pending render
16:9 · YouTube · X card · LinkedIn video · Blog (embed)
cuts · 9LinkedIn 1:1 · 120s · LinkedInDocX 1:1 · 120s · XThreadCardYouTube Shorts 9:16 · 60s · SceneReelInstagram (Reels · feed) 9:16 · 90s · StoryReelFacebook (Reels · feed) 9:16 · 90s · SceneReelThreads 1:1 · 90s · SceneReelTikTok 9:16 · 60s · TikTokNativePinterest 9:16 · 60s · PinterestPinBluesky 1:1 · 60s · SceneReel
storyboard → brief + scenesstrategic relations · Outbound at scale (Clay-style enrichment + AI sequencing) · ⟁ Nexus
Outbound without buying a list
pending render
9:16 · TikTok · Instagram Reels · YouTube Shorts · Facebook Reels · Stories · Threads · Pinterest
pending render
1:1 · Instagram feed · Facebook · X/Twitter · Bluesky · LinkedIn feed
pending render
16:9 · YouTube · X card · LinkedIn video · Blog (embed)
cuts · 9LinkedIn 1:1 · 120s · LinkedInDocX 1:1 · 120s · XThreadCardYouTube Shorts 9:16 · 60s · SceneReelInstagram (Reels · feed) 9:16 · 90s · StoryReelFacebook (Reels · feed) 9:16 · 90s · SceneReelThreads 1:1 · 90s · SceneReelTikTok 9:16 · 60s · TikTokNativePinterest 9:16 · 60s · PinterestPinBluesky 1:1 · 60s · SceneReel
storyboard → brief + scenesperformance · Analytics · ⟁ Mensor
Analytics is a wiring job
pending render
9:16 · TikTok · Instagram Reels · YouTube Shorts · Facebook Reels · Stories · Threads · Pinterest
pending render
1:1 · Instagram feed · Facebook · X/Twitter · Bluesky · LinkedIn feed
pending render
16:9 · YouTube · X card · LinkedIn video · Blog (embed)
cuts · 9LinkedIn 1:1 · 120s · LinkedInDocX 1:1 · 120s · XThreadCardYouTube Shorts 9:16 · 60s · SceneReelInstagram (Reels · feed) 9:16 · 90s · StoryReelFacebook (Reels · feed) 9:16 · 90s · SceneReelThreads 1:1 · 90s · SceneReelTikTok 9:16 · 60s · TikTokNativePinterest 9:16 · 60s · PinterestPinBluesky 1:1 · 60s · SceneReel
storyboard → brief + scenesit dev · Minus the Hype · ⟁ Faber
Viral is not a pipeline
pending render
9:16 · TikTok · Instagram Reels · YouTube Shorts · Facebook Reels · Stories · Threads · Pinterest
pending render
1:1 · Instagram feed · Facebook · X/Twitter · Bluesky · LinkedIn feed
pending render
16:9 · YouTube · X card · LinkedIn video · Blog (embed)
cuts · 9LinkedIn 1:1 · 120s · LinkedInDocX 1:1 · 120s · XThreadCardYouTube Shorts 9:16 · 60s · SceneReelInstagram (Reels · feed) 9:16 · 90s · StoryReelFacebook (Reels · feed) 9:16 · 90s · SceneReelThreads 1:1 · 90s · SceneReelTikTok 9:16 · 60s · TikTokNativePinterest 9:16 · 60s · PinterestPinBluesky 1:1 · 60s · SceneReel
storyboard → brief + scenesEmail (Resend, owned list)
The day's note — EmailBlockStack · rendered at send
- header 600×300 [html/image] · logo + nav; links live; dark-mode safe
- hero 600×600 [gif/image/html-motion] · the week's 1:1 cut as a loop, first-frame poster fallback, alt text, hosted URL
- secondary 600×400 [html/image/gif] · the one promise in copy, single accent; optional
- tertiary 600×250 [html] · the DOOR - a bulletproof button to the segment's door with the UTM spine; never a generic 'learn more'
- footer 600×200 [html] · logo · links · unsubscribe · NAP
- From nameauthored the name the inbox shows BEFORE the subject, and the first thing a reader decides on. Keep it the same across sends — changing it costs the recognition that earns the open. Never 'noreply'.
- Subjectauthored ≤ 50 chars
- Preheaderauthored ≤ 90 chars; finishes the subject's sentence
- Bodyauthored the day's letter; reads-at-the-kitchen-table register
- CTA doorauthored a segment door id; the tertiary block renders it
- Hero assetauthored the hosted GIF URL + poster + alt text
- Plain-text twin derived from the body; every client gets one
rules · subject ≤ 50 · preheader ≤ 90 · from name set, and the same one as last send · dark mode tested · Outlook shows the poster (no GIF motion) · total HTML < 102 KB (Gmail clips) · plain-text twin present · list = contacts with a consent receipt only · send window = the recipient's morning in their zone, never one flat hour · List-Unsubscribe + List-Unsubscribe-Post on EVERY bulk send: `List-Unsubscribe: <https://…>, <mailto:…>` and `List-Unsubscribe-Post: List-Unsubscribe=One-Click`. Gmail and Yahoo have required one-click unsubscribe of bulk senders since February 2024; without the headers the mail is throttled or spam-foldered no matter how good the copy is. This is the HEADER, set at the send — NOT the same thing as the rule below, which is what happens after somebody clicks it. · unsubscribe honoured at the consent root · every link carries the UTM spine, not only the door — an untagged link in the body is a click the reporting never sees
test matrix · dark mode · Outlook desktop (poster) · Gmail mobile · Apple Mail (motion) · 102 KB clip check
acceptance · gate verify_channel_specs.py#CHANNEL-SPECS PASS · review by executive-manager
Blog (static .xyz + Duda .com)
The week's article — Article
- H1authored the episode's argument as a sentence; ≤ 70 chars
- Meta descriptionauthored ≤ 155 chars and UNIQUE across the blog — the line the search result shows, written as a promise, NOT the first 155 characters of the lede. Change it and the SERP snippet changes; leave it derived and two articles that open alike collide (the 2026-08-25 crawl reported description_duplicate on 8 URLs).
- Authorauthored the byline the page shows and the JSON-LD Person points at; must be a real person with a live author page (/blog/author/<slug>). An article with no named author is the E-E-A-T signal Google's quality guidance asks for and we do not send.
- Published dateauthored ISO date; renders as article:published_time and BlogPosting.datePublished, and orders the listing and the sitemap <lastmod>. Move it and the article moves in the feed.
- Updated dateauthored ISO date, only when the article actually changed; renders as BlogPosting.dateModified. Stamp it on an unchanged article and the freshness signal is a lie.
- OG image 1200×630 the chapter card; no typed name
- In-article hero 1600×900 optional
- 16:9 video embed the week's 16:9 cut, in-article
- Alt textauthored one line per in-article image, describing what the image SHOWS, not what it is called — the text a screen reader reads and the only thing an image search can read. An image authored with no alt text is not rendered.
- Headingsauthored one per chapter; the scan tells the story
- Canonical rel=canonical to the .xyz static page; syndication points back
- Internal linksauthored links to other articles or office pages, in the body, beyond the door CTA — a page nothing links to is an orphan and the crawler reports it as one (sitemap_orphan). Every link carries the UTM spine.
- Door linkauthored the segment door with the UTM spine, once, near the end
- Schema (JSON-LD) Organization + Person(author) + BlogPosting + BreadcrumbList, derived from the layers above. NO templated FAQPage/HowTo — those rich results were deprecated in May 2026 and FAQPage is only honest where a visible Q&A exists. Change the author, dates or description and this changes with them, because it reads them.
- Reading time derived
rules · h1 ≤ 70 · title UNIQUE across the blog (the ≤ 60-char SEO title, not just the h1 — two articles clamped to the same 60 characters are one page to a search engine) · meta description ≤ 155 and UNIQUE across the blog · author named, with a live author page · published date present; updated date only when the article changed · canonical present · one door link · at least one internal link in the body, beyond the door CTA · every image has alt text · JSON-LD present and derived from the authored layers (no hand-typed schema)
acceptance · gate verify_channel_specs.py#CHANNEL-SPECS PASS · review by creative-lead
brand · Email Hero GIF · ⟁ Signum
An engine, not a feed
pending render
9:16 · TikTok · Instagram Reels · YouTube Shorts · Facebook Reels · Stories · Threads · Pinterest
pending render
1:1 · Instagram feed · Facebook · X/Twitter · Bluesky · LinkedIn feed
pending render
16:9 · YouTube · X card · LinkedIn video · Blog (embed)
cuts · 1+ Email (Resend, owned list)
storyboard → brief + scenesstrategic relations · longform · ⟁ Nexus
Thirteen doors, one machine underneath
pending render
16:9 · YouTube (long-form)
cuts · 2YouTube Shorts 9:16 · 60s · SceneReel+ Blog (static .xyz + Duda .com)
storyboard → brief + scenesbrand · SMS GIF · ⟁ Signum
The social engine, in full
pending render
9:16 · TikTok · Instagram Reels · YouTube Shorts · Facebook Reels · Stories · Threads · Pinterest
pending render
1:1 · Instagram feed · Facebook · X/Twitter · Bluesky · LinkedIn feed
pending render
16:9 · YouTube · X card · LinkedIn video · Blog (embed)
cuts · 1+ SMS / MMS (Twilio)
storyboard → brief + scenessocial · Social Strategy · ⟁ Nuntius
The plan before the posts
pending render
9:16 · TikTok · Instagram Reels · YouTube Shorts · Facebook Reels · Stories · Threads · Pinterest
pending render
1:1 · Instagram feed · Facebook · X/Twitter · Bluesky · LinkedIn feed
pending render
16:9 · YouTube · X card · LinkedIn video · Blog (embed)
cuts · 9LinkedIn 1:1 · 120s · LinkedInDocX 1:1 · 120s · XThreadCardYouTube Shorts 9:16 · 60s · SceneReelInstagram (Reels · feed) 9:16 · 90s · StoryReelFacebook (Reels · feed) 9:16 · 90s · SceneReelThreads 1:1 · 90s · SceneReelTikTok 9:16 · 60s · TikTokNativePinterest 9:16 · 60s · PinterestPinBluesky 1:1 · 60s · SceneReel
storyboard → brief + scenesstaff training · Data & Analytics for Marketers · ⟁ Magister
Numbers your team can defend
pending render
9:16 · TikTok · Instagram Reels · YouTube Shorts · Facebook Reels · Stories · Threads · Pinterest
pending render
1:1 · Instagram feed · Facebook · X/Twitter · Bluesky · LinkedIn feed
pending render
16:9 · YouTube · X card · LinkedIn video · Blog (embed)
cuts · 9LinkedIn 1:1 · 120s · LinkedInDocX 1:1 · 120s · XThreadCardYouTube Shorts 9:16 · 60s · SceneReelInstagram (Reels · feed) 9:16 · 90s · StoryReelFacebook (Reels · feed) 9:16 · 90s · SceneReelThreads 1:1 · 90s · SceneReelTikTok 9:16 · 60s · TikTokNativePinterest 9:16 · 60s · PinterestPinBluesky 1:1 · 60s · SceneReel
storyboard → brief + scenesit dev · Custom CRM (Airtable, Claude-run) · ⟁ Faber
A custom CRM keeps contacts, stages, and interactions
pending render
9:16 · TikTok · Instagram Reels · YouTube Shorts · Facebook Reels · Stories · Threads · Pinterest
pending render
1:1 · Instagram feed · Facebook · X/Twitter · Bluesky · LinkedIn feed
pending render
16:9 · YouTube · X card · LinkedIn video · Blog (embed)
cuts · 9LinkedIn 1:1 · 120s · LinkedInDocX 1:1 · 120s · XThreadCardYouTube Shorts 9:16 · 60s · SceneReelInstagram (Reels · feed) 9:16 · 90s · StoryReelFacebook (Reels · feed) 9:16 · 90s · SceneReelThreads 1:1 · 90s · SceneReelTikTok 9:16 · 60s · TikTokNativePinterest 9:16 · 60s · PinterestPinBluesky 1:1 · 60s · SceneReel
storyboard → brief + scenesperformance · Email · ⟁ Mensor
The channel you actually own
pending render
9:16 · TikTok · Instagram Reels · YouTube Shorts · Facebook Reels · Stories · Threads · Pinterest
pending render
1:1 · Instagram feed · Facebook · X/Twitter · Bluesky · LinkedIn feed
pending render
16:9 · YouTube · X card · LinkedIn video · Blog (embed)
cuts · 9LinkedIn 1:1 · 120s · LinkedInDocX 1:1 · 120s · XThreadCardYouTube Shorts 9:16 · 60s · SceneReelInstagram (Reels · feed) 9:16 · 90s · StoryReelFacebook (Reels · feed) 9:16 · 90s · SceneReelThreads 1:1 · 90s · SceneReelTikTok 9:16 · 60s · TikTokNativePinterest 9:16 · 60s · PinterestPinBluesky 1:1 · 60s · SceneReel
storyboard → brief + scenesperformance · Receipts · ⟁ Mensor
13 flows in production
pending render
9:16 · TikTok · Instagram Reels · YouTube Shorts · Facebook Reels · Stories · Threads · Pinterest
pending render
1:1 · Instagram feed · Facebook · X/Twitter · Bluesky · LinkedIn feed
pending render
16:9 · YouTube · X card · LinkedIn video · Blog (embed)
cuts · 9LinkedIn 1:1 · 120s · LinkedInDocX 1:1 · 120s · XThreadCardYouTube Shorts 9:16 · 60s · SceneReelInstagram (Reels · feed) 9:16 · 90s · StoryReelFacebook (Reels · feed) 9:16 · 90s · SceneReelThreads 1:1 · 90s · SceneReelTikTok 9:16 · 60s · TikTokNativePinterest 9:16 · 60s · PinterestPinBluesky 1:1 · 60s · SceneReel
storyboard → brief + scenesEmail (Resend, owned list)
The day's note — EmailBlockStack · rendered at send
- header 600×300 [html/image] · logo + nav; links live; dark-mode safe
- hero 600×600 [gif/image/html-motion] · the week's 1:1 cut as a loop, first-frame poster fallback, alt text, hosted URL
- secondary 600×400 [html/image/gif] · the one promise in copy, single accent; optional
- tertiary 600×250 [html] · the DOOR - a bulletproof button to the segment's door with the UTM spine; never a generic 'learn more'
- footer 600×200 [html] · logo · links · unsubscribe · NAP
- From nameauthored the name the inbox shows BEFORE the subject, and the first thing a reader decides on. Keep it the same across sends — changing it costs the recognition that earns the open. Never 'noreply'.
- Subjectauthored ≤ 50 chars
- Preheaderauthored ≤ 90 chars; finishes the subject's sentence
- Bodyauthored the day's letter; reads-at-the-kitchen-table register
- CTA doorauthored a segment door id; the tertiary block renders it
- Hero assetauthored the hosted GIF URL + poster + alt text
- Plain-text twin derived from the body; every client gets one
rules · subject ≤ 50 · preheader ≤ 90 · from name set, and the same one as last send · dark mode tested · Outlook shows the poster (no GIF motion) · total HTML < 102 KB (Gmail clips) · plain-text twin present · list = contacts with a consent receipt only · send window = the recipient's morning in their zone, never one flat hour · List-Unsubscribe + List-Unsubscribe-Post on EVERY bulk send: `List-Unsubscribe: <https://…>, <mailto:…>` and `List-Unsubscribe-Post: List-Unsubscribe=One-Click`. Gmail and Yahoo have required one-click unsubscribe of bulk senders since February 2024; without the headers the mail is throttled or spam-foldered no matter how good the copy is. This is the HEADER, set at the send — NOT the same thing as the rule below, which is what happens after somebody clicks it. · unsubscribe honoured at the consent root · every link carries the UTM spine, not only the door — an untagged link in the body is a click the reporting never sees
test matrix · dark mode · Outlook desktop (poster) · Gmail mobile · Apple Mail (motion) · 102 KB clip check
acceptance · gate verify_channel_specs.py#CHANNEL-SPECS PASS · review by executive-manager
SMS / MMS (Twilio)
The day's text — SmsMms · rendered at send
- Bodyauthored ≤ 160 chars including the opt-out — but that is the GSM-7 limit. One emoji or one curly apostrophe flips the message to UCS-2 and the real limit is 70. One idea, one link.
- MMS loop 720×720 the 1:1 cut as a short loop; a still if the carrier strips motion
- Linkauthored one shortened link with the UTM spine, to a door
rules · body ≤ 160 incl. opt-out · encoding: GSM-7 → 160 in one message, 153 per segment when concatenated; UCS-2 → 70 and 67. One emoji or one curly apostrophe (’ “ ” — …) flips the whole message to UCS-2 and drops the limit 160 → 70 · segments: 1 — past the single-message limit for its encoding the message is billed as 2+ segments and any carrier that does not reassemble truncates it · HELP and STOP both answered — US carriers (CTIA messaging principles) require the HELP keyword alongside opt-out, not STOP alone · quiet hours (recipient zone) · sender id registered · 2 per week (Tue · Fri) · list = receipts only
acceptance · gate verify_channel_specs.py#CHANNEL-SPECS PASS · review by executive-manager
Blog (static .xyz + Duda .com)
The week's article — Article
- H1authored the episode's argument as a sentence; ≤ 70 chars
- Meta descriptionauthored ≤ 155 chars and UNIQUE across the blog — the line the search result shows, written as a promise, NOT the first 155 characters of the lede. Change it and the SERP snippet changes; leave it derived and two articles that open alike collide (the 2026-08-25 crawl reported description_duplicate on 8 URLs).
- Authorauthored the byline the page shows and the JSON-LD Person points at; must be a real person with a live author page (/blog/author/<slug>). An article with no named author is the E-E-A-T signal Google's quality guidance asks for and we do not send.
- Published dateauthored ISO date; renders as article:published_time and BlogPosting.datePublished, and orders the listing and the sitemap <lastmod>. Move it and the article moves in the feed.
- Updated dateauthored ISO date, only when the article actually changed; renders as BlogPosting.dateModified. Stamp it on an unchanged article and the freshness signal is a lie.
- OG image 1200×630 the chapter card; no typed name
- In-article hero 1600×900 optional
- 16:9 video embed the week's 16:9 cut, in-article
- Alt textauthored one line per in-article image, describing what the image SHOWS, not what it is called — the text a screen reader reads and the only thing an image search can read. An image authored with no alt text is not rendered.
- Headingsauthored one per chapter; the scan tells the story
- Canonical rel=canonical to the .xyz static page; syndication points back
- Internal linksauthored links to other articles or office pages, in the body, beyond the door CTA — a page nothing links to is an orphan and the crawler reports it as one (sitemap_orphan). Every link carries the UTM spine.
- Door linkauthored the segment door with the UTM spine, once, near the end
- Schema (JSON-LD) Organization + Person(author) + BlogPosting + BreadcrumbList, derived from the layers above. NO templated FAQPage/HowTo — those rich results were deprecated in May 2026 and FAQPage is only honest where a visible Q&A exists. Change the author, dates or description and this changes with them, because it reads them.
- Reading time derived
rules · h1 ≤ 70 · title UNIQUE across the blog (the ≤ 60-char SEO title, not just the h1 — two articles clamped to the same 60 characters are one page to a search engine) · meta description ≤ 155 and UNIQUE across the blog · author named, with a live author page · published date present; updated date only when the article changed · canonical present · one door link · at least one internal link in the body, beyond the door CTA · every image has alt text · JSON-LD present and derived from the authored layers (no hand-typed schema)
acceptance · gate verify_channel_specs.py#CHANNEL-SPECS PASS · review by creative-lead
brand · Email Hero GIF · ⟁ Signum
Demand you can trace
pending render
9:16 · TikTok · Instagram Reels · YouTube Shorts · Facebook Reels · Stories · Threads · Pinterest
pending render
1:1 · Instagram feed · Facebook · X/Twitter · Bluesky · LinkedIn feed
pending render
16:9 · YouTube · X card · LinkedIn video · Blog (embed)
cuts · 1+ Email (Resend, owned list)
storyboard → brief + scenesit dev · longform · ⟁ Faber
Friday reads the board
pending render
16:9 · YouTube (long-form)
cuts · 2YouTube Shorts 9:16 · 60s · SceneReel+ Blog (static .xyz + Duda .com)
storyboard → brief + scenessocial · Content Creation · ⟁ Nuntius
Blank page to repeatable system
pending render
9:16 · TikTok · Instagram Reels · YouTube Shorts · Facebook Reels · Stories · Threads · Pinterest
pending render
1:1 · Instagram feed · Facebook · X/Twitter · Bluesky · LinkedIn feed
pending render
16:9 · YouTube · X card · LinkedIn video · Blog (embed)
cuts · 9LinkedIn 1:1 · 120s · LinkedInDocX 1:1 · 120s · XThreadCardYouTube Shorts 9:16 · 60s · SceneReelInstagram (Reels · feed) 9:16 · 90s · StoryReelFacebook (Reels · feed) 9:16 · 90s · SceneReelThreads 1:1 · 90s · SceneReelTikTok 9:16 · 60s · TikTokNativePinterest 9:16 · 60s · PinterestPinBluesky 1:1 · 60s · SceneReel
storyboard → brief + scenesstaff training · AI & Automation for
GTM · ⟁ Magister
Automation that touches revenue
pending render
9:16 · TikTok · Instagram Reels · YouTube Shorts · Facebook Reels · Stories · Threads · Pinterest
pending render
1:1 · Instagram feed · Facebook · X/Twitter · Bluesky · LinkedIn feed
pending render
16:9 · YouTube · X card · LinkedIn video · Blog (embed)
cuts · 9LinkedIn 1:1 · 120s · LinkedInDocX 1:1 · 120s · XThreadCardYouTube Shorts 9:16 · 60s · SceneReelInstagram (Reels · feed) 9:16 · 90s · StoryReelFacebook (Reels · feed) 9:16 · 90s · SceneReelThreads 1:1 · 90s · SceneReelTikTok 9:16 · 60s · TikTokNativePinterest 9:16 · 60s · PinterestPinBluesky 1:1 · 60s · SceneReel
storyboard → brief + scenesmultimedia ·
R3F / three.js — the 3D web (the Lab + the Signal Field) · ⟁ Lumen
3D on the web, no plugin
pending render
9:16 · TikTok · Instagram Reels · YouTube Shorts · Facebook Reels · Stories · Threads · Pinterest
pending render
1:1 · Instagram feed · Facebook · X/Twitter · Bluesky · LinkedIn feed
pending render
16:9 · YouTube · X card · LinkedIn video · Blog (embed)
cuts · 9LinkedIn 1:1 · 120s · LinkedInDocX 1:1 · 120s · XThreadCardYouTube Shorts 9:16 · 60s · SceneReelInstagram (Reels · feed) 9:16 · 90s · StoryReelFacebook (Reels · feed) 9:16 · 90s · SceneReelThreads 1:1 · 90s · SceneReelTikTok 9:16 · 60s · TikTokNativePinterest 9:16 · 60s · PinterestPinBluesky 1:1 · 60s · SceneReel
storyboard → brief + scenesperformance · Mobile App · ⟁ Mensor
An app is a retention bet
pending render
9:16 · TikTok · Instagram Reels · YouTube Shorts · Facebook Reels · Stories · Threads · Pinterest
pending render
1:1 · Instagram feed · Facebook · X/Twitter · Bluesky · LinkedIn feed
pending render
16:9 · YouTube · X card · LinkedIn video · Blog (embed)
cuts · 9LinkedIn 1:1 · 120s · LinkedInDocX 1:1 · 120s · XThreadCardYouTube Shorts 9:16 · 60s · SceneReelInstagram (Reels · feed) 9:16 · 90s · StoryReelFacebook (Reels · feed) 9:16 · 90s · SceneReelThreads 1:1 · 90s · SceneReelTikTok 9:16 · 60s · TikTokNativePinterest 9:16 · 60s · PinterestPinBluesky 1:1 · 60s · SceneReel
storyboard → brief + scenesstrategic relations · Field Notes · ⟁ Nexus
A late reply costs more
pending render
9:16 · TikTok · Instagram Reels · YouTube Shorts · Facebook Reels · Stories · Threads · Pinterest
pending render
1:1 · Instagram feed · Facebook · X/Twitter · Bluesky · LinkedIn feed
pending render
16:9 · YouTube · X card · LinkedIn video · Blog (embed)
cuts · 9LinkedIn 1:1 · 120s · LinkedInDocX 1:1 · 120s · XThreadCardYouTube Shorts 9:16 · 60s · SceneReelInstagram (Reels · feed) 9:16 · 90s · StoryReelFacebook (Reels · feed) 9:16 · 90s · SceneReelThreads 1:1 · 90s · SceneReelTikTok 9:16 · 60s · TikTokNativePinterest 9:16 · 60s · PinterestPinBluesky 1:1 · 60s · SceneReel
storyboard → brief + scenesEmail (Resend, owned list)
The day's note — EmailBlockStack · rendered at send
- header 600×300 [html/image] · logo + nav; links live; dark-mode safe
- hero 600×600 [gif/image/html-motion] · the week's 1:1 cut as a loop, first-frame poster fallback, alt text, hosted URL
- secondary 600×400 [html/image/gif] · the one promise in copy, single accent; optional
- tertiary 600×250 [html] · the DOOR - a bulletproof button to the segment's door with the UTM spine; never a generic 'learn more'
- footer 600×200 [html] · logo · links · unsubscribe · NAP
- From nameauthored the name the inbox shows BEFORE the subject, and the first thing a reader decides on. Keep it the same across sends — changing it costs the recognition that earns the open. Never 'noreply'.
- Subjectauthored ≤ 50 chars
- Preheaderauthored ≤ 90 chars; finishes the subject's sentence
- Bodyauthored the day's letter; reads-at-the-kitchen-table register
- CTA doorauthored a segment door id; the tertiary block renders it
- Hero assetauthored the hosted GIF URL + poster + alt text
- Plain-text twin derived from the body; every client gets one
rules · subject ≤ 50 · preheader ≤ 90 · from name set, and the same one as last send · dark mode tested · Outlook shows the poster (no GIF motion) · total HTML < 102 KB (Gmail clips) · plain-text twin present · list = contacts with a consent receipt only · send window = the recipient's morning in their zone, never one flat hour · List-Unsubscribe + List-Unsubscribe-Post on EVERY bulk send: `List-Unsubscribe: <https://…>, <mailto:…>` and `List-Unsubscribe-Post: List-Unsubscribe=One-Click`. Gmail and Yahoo have required one-click unsubscribe of bulk senders since February 2024; without the headers the mail is throttled or spam-foldered no matter how good the copy is. This is the HEADER, set at the send — NOT the same thing as the rule below, which is what happens after somebody clicks it. · unsubscribe honoured at the consent root · every link carries the UTM spine, not only the door — an untagged link in the body is a click the reporting never sees
test matrix · dark mode · Outlook desktop (poster) · Gmail mobile · Apple Mail (motion) · 102 KB clip check
acceptance · gate verify_channel_specs.py#CHANNEL-SPECS PASS · review by executive-manager
Blog (static .xyz + Duda .com)
The week's article — Article
- H1authored the episode's argument as a sentence; ≤ 70 chars
- Meta descriptionauthored ≤ 155 chars and UNIQUE across the blog — the line the search result shows, written as a promise, NOT the first 155 characters of the lede. Change it and the SERP snippet changes; leave it derived and two articles that open alike collide (the 2026-08-25 crawl reported description_duplicate on 8 URLs).
- Authorauthored the byline the page shows and the JSON-LD Person points at; must be a real person with a live author page (/blog/author/<slug>). An article with no named author is the E-E-A-T signal Google's quality guidance asks for and we do not send.
- Published dateauthored ISO date; renders as article:published_time and BlogPosting.datePublished, and orders the listing and the sitemap <lastmod>. Move it and the article moves in the feed.
- Updated dateauthored ISO date, only when the article actually changed; renders as BlogPosting.dateModified. Stamp it on an unchanged article and the freshness signal is a lie.
- OG image 1200×630 the chapter card; no typed name
- In-article hero 1600×900 optional
- 16:9 video embed the week's 16:9 cut, in-article
- Alt textauthored one line per in-article image, describing what the image SHOWS, not what it is called — the text a screen reader reads and the only thing an image search can read. An image authored with no alt text is not rendered.
- Headingsauthored one per chapter; the scan tells the story
- Canonical rel=canonical to the .xyz static page; syndication points back
- Internal linksauthored links to other articles or office pages, in the body, beyond the door CTA — a page nothing links to is an orphan and the crawler reports it as one (sitemap_orphan). Every link carries the UTM spine.
- Door linkauthored the segment door with the UTM spine, once, near the end
- Schema (JSON-LD) Organization + Person(author) + BlogPosting + BreadcrumbList, derived from the layers above. NO templated FAQPage/HowTo — those rich results were deprecated in May 2026 and FAQPage is only honest where a visible Q&A exists. Change the author, dates or description and this changes with them, because it reads them.
- Reading time derived
rules · h1 ≤ 70 · title UNIQUE across the blog (the ≤ 60-char SEO title, not just the h1 — two articles clamped to the same 60 characters are one page to a search engine) · meta description ≤ 155 and UNIQUE across the blog · author named, with a live author page · published date present; updated date only when the article changed · canonical present · one door link · at least one internal link in the body, beyond the door CTA · every image has alt text · JSON-LD present and derived from the authored layers (no hand-typed schema)
acceptance · gate verify_channel_specs.py#CHANNEL-SPECS PASS · review by creative-lead
