Eight ShortFlix variants ship a PWA. This one ships a 4 KB <script>. The same four agents (curator · unified-search · trend-safety · orchestrator) run on Cloud Run; the surface is whatever blog, Notion page, Substack issue or company wiki already has an audience. We embed there, with a signed widget, and read taste signals back through a postMessage hook the host controls.
// 1. Drop this into any host page (Notion, Substack, MDX blog, company wiki) <script src="https://cdn.shortflix.app/embed.js" data-token="sf_pub_8a7f...c14" data-curator="@jisu" data-tags="hands,silentCrafts,under60s" data-count="6" data-theme="light"></script> <div id="shortflix-embed"></div>
# cloud run service · ADK orchestrator · 4 agents POST /v1/embed/curate → orchestrator ├─ unified_search (mcp.rapidapi.yt|ig|tt) ├─ trend_safety (gemini + vertex_search) └─ curator (gemini-2.0-flash · novelty) ← 6 cards · per-card "why" · embed-safe URLs latency p50=1.18s · p95=1.94s · cost $0.041 / call
Maya A. · 6 May 2026 · 4 min read
I've been writing about the weight of craft for three years and I have never seen anything quite like Tunde's workshop. He welds at night because the city is quieter and because the sparks read better against the dark.
Reading order matters: Tunde first, because the silence in his workshop is the same silence that the Icelandic fishermen keep on the boats…
Eight other ShortFlix variants compete with a PWA the user has to install. The Embed SDK lets ShortFlix appear inside the surfaces the user is already on — and judges can see, on the demo, six different host pages syndicating the same four agents.
The widget is dumb on purpose; everything (novelty re-rank, ToS guard, cross-platform fanout) lives in the agents. A single-agent baseline cannot ship as a 4 KB embed without losing the trend-safety guard.
Demo video opens with the host's blog, scrolls past the embed, then cuts to the orchestrator dashboard showing the same call. One narrative thread; two surfaces; no app install.