Open-source platform for 3D AI agents. Turn text or a photo into a rigged, animated GLB avatar, give it an LLM brain, memory and a wallet, and embed it anywhere with one web component. Remote MCP server, x402 payments, Three.js, browser-native.
JavaScript 3d-generationai-agentsanimationavatardigital-humangenerative-aiglbgltfimage-to-3dllmmcpmcp-servermodel-context-protocolsolanatext-to-3dthreejsweb-componentswebglwebxrx402
docs(demo): publish the product-demo filming guide as a real docs page
nirholas0f75c2cf13a9
diff --git a/CHANGELOG.md b/CHANGELOG.mdindex 1d703119f..5089a92c0 100644--- a/CHANGELOG.md+++ b/CHANGELOG.md@@ -4,6 +4,10 @@Public history for [three.ws](https://three.ws), newest first. New pages come from `added` dates in data/pages.json; everything else is curated in data/changelog.json. Also available as [JSON](https://three.ws/changelog.json) and [RSS](https://three.ws/changelog.xml), live at [three.ws/changelog](https://three.ws/changelog).+## 2026-09-05++- **Filming the product demo** (`/docs/product-demo`): How the narrated walkthrough of every three.ws feature is filmed on the live site: the route is generated from the Feature Tour curriculum, so a page that ships tomorrow films itself, and each chapter can be re-shot on its own.+## 2026-09-04- **Trader Wrapped: your season on pump.fun** (`/wrapped`): The season recap for any verified pump.fun trading agent on three.ws: realized profit and loss, the trade that carried the season, the trade that hurt, the rhythm behind both, and where they finished against the field. Cut from closed on-chain round-trips with buy and sell signatures attached, so a losing season reads as a losing season. Swipeable, shareable, no account and no wallet.diff --git a/data/pages.json b/data/pages.jsonindex 8fdc67ebf..954011f5a 100644--- a/data/pages.json+++ b/data/pages.json@@ -3539,6 +3539,12 @@"description": "The release runbook for the three.ws Seeker app: Publisher Portal setup, the release keystore, building and verifying a signed APK, and submitting it for review.","added": "2026-08-28"},+ {+ "path": "/docs/product-demo",+ "title": "Filming the product demo",+ "description": "How the narrated walkthrough of every three.ws feature is filmed on the live site: the route is generated from the Feature Tour curriculum, so a page that ships tomorrow films itself, and each chapter can be re-shot on its own.",+ "added": "2026-09-05"+ },{"path": "/docs/seeker-video","title": "Filming three.ws on a Seeker without a Seeker",diff --git a/docs/product-demo.md b/docs/product-demo.mdindex 821222f9e..860860e2e 100644--- a/docs/product-demo.md+++ b/docs/product-demo.md@@ -83,11 +83,23 @@ settling after a search. Stepped frames freeze all of that, and nearly every routhe host cursor over a real session. It reports the interaction; it never stands in for one. Samefor the click ring.-**The voice is the platform's own.** Narration is synthesized through-[`/api/tts/speak`](./api-reference.md), the free NVIDIA Magpie lane, so three.ws narrates three.ws.-Clips are cached on their text under `marketing/product-demo/.raw/voice/`, so re-recording one-chapter costs no synthesis and gets exactly the audio the full run would have given it. Captions-carry the same words for anyone watching without sound.+**The voice is the platform's own.** Narration is synthesized through the site's own TTS lane, so+three.ws narrates three.ws. The default is `/api/tts/edge` (Microsoft Edge Neural voices, proxied+and cached in R2 by the platform), because it allows 20 lines a minute for a signed-in caller and a+full film has close to three hundred of them. `--narrator=speak` switches to the free NVIDIA Magpie+lane behind `/api/tts/speak`, which is better suited to a handful of lines: it allows 40 an hour.+Both lanes need the QA session, so `--authed` is not optional when there is a voice track.++Every line is synthesized **before** the camera rolls. Filming is real time, so a line fetched+mid-take is dead air on screen: the first cut of this film opened on 52 seconds of silence because+its longest line was being synthesized while the page sat there. The warm-up collects the whole+script (chapter intros, every stop's line, and the `beat()` literals inside the acts), synthesizes+what is missing, and caches it on disk under `marketing/product-demo/.raw/voice/`. A rerun pays none+of that twice, and a single re-shot chapter gets exactly the audio the full run gave it.++Captions carry the same words for anyone watching without sound. What is written and what is spoken+are not the same string, though: a caption reads `three.ws` and `USDC`, and the synthesizer is handed+`three dot w s` and `U S D C`.The narration track is laid down as a single exact concatenation of speech and silence at theoffsets each line was spoken at, then muxed with the video. Nothing is mixed, so an hour-long film@@ -104,7 +116,8 @@ stays sample accurate end to end.| `--authed` | Replay the QA session, so signed-in surfaces are on screen || `--origin=http://localhost:3000` | Film a dev server instead of production || `--out=<dir>` | Write somewhere else |-| `--voice=<id>` | Any voice from `/api/tts/voices` (default `nova`) |+| `--narrator=edge\|speak` | Which TTS lane to synthesize on (default `edge`) |+| `--voice=<id>` | Voice for that lane (default `en-US-AndrewMultilingualNeural`; the `speak` lane takes ids from `/api/tts/voices`) || `--no-voice` | Captions only, no narration track || `--reuse` | Keep chapter mp4s that already exist, and film the rest || `--strict` | A failed stop fails the run |@@ -115,12 +128,16 @@ stays sample accurate end to end.- **`--authed` needs a session.** `npm run audit:web:login` mints one into `.auth/audit-state.json`from the QA credentials in `.env`. Without it, the signed-in surfaces (x402 Studio, profile,- wallet) show their sign-in wall, and `/create/prompt` cannot start a real generation.+ wallet) show their sign-in wall, `/create/prompt` cannot start a real generation, and the+ narration cannot be synthesized at all: the edge lane answers an anonymous caller with a 401, and+ the `speak` lane drops to ten lines an hour.- **`ffmpeg` and `ffprobe` must be on `PATH`** (`sudo apt-get install -y ffmpeg`). Playwright shipsits own ffmpeg, but that build is VP8-only with no filters, so it can do neither the H.264 encodenor the audio mux.- **Check the disk.** A full run writes a raw webm per chapter before encoding it. Reclaim spacefirst with `npm run clean:worktrees -- --apply` if the workspace is tight.+- **The first run pays for the narration.** Warming close to three hundred lines at the edge lane's+ 20 a minute takes about 15 minutes before any filming starts. Later runs skip it.- **A full run takes about as long as the film.** It is a real-time recording of a real site, sobudget roughly an hour of wall clock for the full route, and film it in chapters (`--sections=`,then `--reuse`) if you would rather not hold one process open that long.diff --git a/docs/start-here.md b/docs/start-here.mdindex 359272d27..611051ff3 100644--- a/docs/start-here.md+++ b/docs/start-here.md@@ -187,6 +187,7 @@ Deeper references that don't fit a track above but answer real questions:- [Publishing to the Solana dApp Store](./seeker-publishing.md): the release runbook for the Seeker app, from the Publisher Portal setup and the release keystore through building, verifying, and submitting a signed APK- [Submission day: getting three.ws onto the Seeker dApp Store](./seeker-submission-day.md): the owner's step-by-step, with every portal field, the listing copy to paste, and the five screenshots to capture on the phone- [Filming three.ws on a Seeker without a Seeker](./seeker-video.md): how to record a Seeker screen-recording of the app with no device, why the TWA makes that a real capture rather than a mock-up, and what still has to come from an emulator+- [Filming the product demo](./product-demo.md): the narrated walkthrough of every feature on the live site, how the route is generated from the Feature Tour curriculum so a new page films itself, and how to re-shoot a single chapter- [three.ws on iOS](./ios-app.md): the App Store app, what it adds on top of the website (native share sheet, universal links, wallet deep links, offline shell), and how the web half of it ships on every deploy- [Free LLM providers](./free-llm-providers.md): the failover chain of a dozen free AI providers behind every text completion, what each free tier gives, and how to add the next rung- [Tokens API on three.ws](./tokens-xyz.md): the Solana Foundation asset layer that tells us which mints are the same asset, why it sits second in the market-data cascade, and the one env var that turns it ondiff --git a/public/changelog.json b/public/changelog.jsonindex 09ede3c9a..ea74aefba 100644--- a/public/changelog.json+++ b/public/changelog.json@@ -1,11 +1,21 @@{- "generated_at": "2026-09-05T00:10:33.207Z",+ "generated_at": "2026-09-05T03:37:39.334Z","generated_by": "scripts/build-page-index.mjs from data/pages.json + data/changelog.json","site": {"name": "three.ws","url": "https://three.ws"},"entries": [+ {+ "date": "2026-09-05",+ "type": "launch",+ "title": "Filming the product demo",+ "summary": "How the narrated walkthrough of every three.ws feature is filmed on the live site: the route is generated from the Feature Tour curriculum, so a page that ships tomorrow films itself, and each chapter can be re-shot on its own.",+ "link": "/docs/product-demo",+ "tags": [+ "launch"+ ]+ },{"date": "2026-09-04","type": "launch",diff --git a/public/changelog.xml b/public/changelog.xmlindex 16063b38a..efea26679 100644--- a/public/changelog.xml+++ b/public/changelog.xml@@ -6,6 +6,14 @@<atom:link href="https://three.ws/changelog.xml" rel="self" type="application/rss+xml"/><description>What's new on three.ws: features, improvements, and releases, newest first.</description><language>en</language>+ <item>+ <title>Filming the product demo</title>+ <link>https://three.ws/docs/product-demo</link>+ <guid isPermaLink="false">2026-09-05:Filming the product demo</guid>+ <pubDate>Sat, 05 Sep 2026 12:00:00 GMT</pubDate>+ <category>launch</category>+ <description>How the narrated walkthrough of every three.ws feature is filmed on the live site: the route is generated from the Feature Tour curriculum, so a page that ships tomorrow films itself, and each chapter can be re-shot on its own.</description>+ </item><item><title>Trader Wrapped: your season on pump.fun</title><link>https://three.ws/wrapped</link>diff --git a/public/features.json b/public/features.jsonindex 547fa159d..834e6a44e 100644--- a/public/features.json+++ b/public/features.json@@ -1,5 +1,5 @@{- "generated_at": "2026-09-05T00:10:33.182Z",+ "generated_at": "2026-09-05T03:37:39.322Z","generated_by": "scripts/build-page-index.mjs from data/pages.json","site": {"name": "three.ws",@@ -4388,6 +4388,16 @@"tags": [],"showcase": false},+ {+ "path": "/docs/product-demo",+ "title": "Filming the product demo",+ "description": "How the narrated walkthrough of every three.ws feature is filmed on the live site: the route is generated from the Feature Tour curriculum, so a page that ships tomorrow films itself, and each chapter can be re-shot on its own.",+ "added": "2026-09-05",+ "auth": null,+ "indexable": true,+ "tags": [],+ "showcase": false+ },{"path": "/docs/seeker-video","title": "Filming three.ws on a Seeker without a Seeker",diff --git a/public/llms-full.txt b/public/llms-full.txtindex 8301b671b..1426c845f 100644--- a/public/llms-full.txt+++ b/public/llms-full.txt@@ -2662,6 +2662,12 @@ URL: https://three.ws/docs/seeker-publishingThe release runbook for the three.ws Seeker app: Publisher Portal setup, the release keystore, building and verifying a signed APK, and submitting it for review.+### Filming the product demo++URL: https://three.ws/docs/product-demo++How the narrated walkthrough of every three.ws feature is filmed on the live site: the route is generated from the Feature Tour curriculum, so a page that ships tomorrow films itself, and each chapter can be re-shot on its own.+### Filming three.ws on a Seeker without a SeekerURL: https://three.ws/docs/seeker-videodiff --git a/public/llms.txt b/public/llms.txtindex 945716177..a3fd693ea 100644--- a/public/llms.txt+++ b/public/llms.txt@@ -480,6 +480,7 @@ Docs, tutorials, and reference.- [Docs · Agent Monitor](https://three.ws/docs/monitor): What each panel on /monitor reads and how often, every control on the board, how a failed panel degrades alone, and how to add a panel of your own.- [three.ws on Solana Seeker](https://three.ws/docs/seeker-app): What the Seeker app adds on top of the website: Seed Vault sign-in, share-sheet capture, an offline shell, home-screen shortcuts, and Seeker Genesis Token verification.- [Publishing to the Solana dApp Store](https://three.ws/docs/seeker-publishing): The release runbook for the three.ws Seeker app: Publisher Portal setup, the release keystore, building and verifying a signed APK, and submitting it for review.+- [Filming the product demo](https://three.ws/docs/product-demo): How the narrated walkthrough of every three.ws feature is filmed on the live site: the route is generated from the Feature Tour curriculum, so a page that ships tomorrow films itself, and each chapter can be re-shot on its own.- [Filming three.ws on a Seeker without a Seeker](https://three.ws/docs/seeker-video): How to record a Seeker screen recording of the app with no device: why the Trusted Web Activity makes a browser capture at the real panel geometry a genuine capture, and which moments still have to come from an Android emulator.- [Submission day: three.ws on the Seeker dApp Store](https://three.ws/docs/seeker-submission-day): The owner's step-by-step for submission day: funding the publisher wallet, every Publisher Portal field with the listing copy to paste, the five screenshots to capture on a Seeker, and the submit command.- [three.ws on iOS](https://three.ws/docs/ios-app): What the App Store app adds on top of the website: the native share sheet, universal links, wallet deep links back to the page you left, real permission prompts, and an offline screen that recovers on its own.diff --git a/public/sitemap/index.html b/public/sitemap/index.htmlindex 75f4877cc..d3027a99c 100644--- a/public/sitemap/index.html+++ b/public/sitemap/index.html@@ -88,7 +88,7 @@<main class="sm-wrap"><div class="sm-hero"><h1>Sitemap</h1>- <p>All 907 pages on three.ws, grouped by purpose. Looking for the machine-readable versions?</p>+ <p>All 908 pages on three.ws, grouped by purpose. Looking for the machine-readable versions?</p><div class="sm-formats"><a href="/sitemap.xml"><code>sitemap.xml</code> · for search engines</a><a href="/llms.txt"><code>llms.txt</code> · for AI agents</a>@@ -100,7 +100,7 @@</div><div class="sm-filter"><svg viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" aria-hidden="true"><circle cx="11" cy="11" r="7"/><path d="m21 21-4.3-4.3"/></svg>- <input id="sm-filter-input" type="search" placeholder="Filter 907 pages by name, path, or description…" aria-label="Filter pages" autocomplete="off" spellcheck="false" />+ <input id="sm-filter-input" type="search" placeholder="Filter 908 pages by name, path, or description…" aria-label="Filter pages" autocomplete="off" spellcheck="false" /><kbd aria-hidden="true">/</kbd></div><p class="sm-filter-count" id="sm-filter-count" role="status" aria-live="polite"></p>@@ -108,6 +108,14 @@<h2 id="sm-new-title">Newest<a class="sm-new-more" href="/changelog">full changelog →</a></h2><p class="sm-section-desc">The 9 most recently launched pages, straight to the live surface.</p><ul class="sm-list">+ <li>+ <a href="/docs/product-demo">+ <span class="sm-new-date">Sep 5, 2026</span>+ <span class="sm-title">Filming the product demo</span>+ <span class="sm-path">/docs/product-demo</span>+ <span class="sm-desc">How the narrated walkthrough of every three.ws feature is filmed on the live site: the route is generated from the Feature Tour curriculum, so a page that ships tomorrow films itself, and each chapter can be re-shot on its own.</span>+ </a>+ </li><li><a href="/wrapped"><span class="sm-new-date">Sep 4, 2026</span>@@ -172,14 +180,6 @@<span class="sm-desc">Give your existing Home Assistant voice assistant a face. Pair a three.ws satellite and the same pipeline you already use gains a 3D agent that lip-syncs its answers and reacts, on any screen in the house. Home Assistant keeps the wake word, the speech recognition and the answer; closing the page never stops the voice working.</span></a></li>- <li>- <a href="/docs/home-voice">- <span class="sm-new-date">Sep 3, 2026</span>- <span class="sm-title">Docs · The browser voice loop</span>- <span class="sm-path">/docs/home-voice</span>- <span class="sm-desc">How hands-free works for a connected home: a wake word matched by a model running in your own tab, an interruption that stops the agent mid-sentence, a pause that does not truncate your command, and a spoken confirmation narrow enough that a background yes can never unlock a front door. Includes the measured latency of every leg and how to mount the loop on your own surface.</span>- </a>- </li></ul></section><nav class="sm-toc" aria-label="Sections">@@ -2477,7 +2477,7 @@<section class="sm-section" id="learn"><header>- <h2>Learn<span class="sm-count" data-count>417</span></h2>+ <h2>Learn<span class="sm-count" data-count>418</span></h2><p class="sm-section-desc">Docs, tutorials, and reference.</p></header><ul class="sm-list">@@ -3286,6 +3286,13 @@<span class="sm-desc">The release runbook for the three.ws Seeker app: Publisher Portal setup, the release keystore, building and verifying a signed APK, and submitting it for review.</span></a></li>+ <li>+ <a href="/docs/product-demo">+ <span class="sm-title">Filming the product demo</span>+ <span class="sm-path">/docs/product-demo</span>+ <span class="sm-desc">How the narrated walkthrough of every three.ws feature is filmed on the live site: the route is generated from the Feature Tour curriculum, so a page that ships tomorrow films itself, and each chapter can be re-shot on its own.</span>+ </a>+ </li><li><a href="/docs/seeker-video"><span class="sm-title">Filming three.ws on a Seeker without a Seeker</span>diff --git a/scripts/make-product-demo.mjs b/scripts/make-product-demo.mjsindex 813e8783b..21a57ddc0 100644--- a/scripts/make-product-demo.mjs+++ b/scripts/make-product-demo.mjs@@ -17,8 +17,9 @@* broken, that shows up as a skipped stop in the run report instead of a pretty* lie in the film.*- * The voice is the platform's own TTS lane (/api/tts/speak, free NVIDIA Magpie),- * so three.ws narrates three.ws. Captions carry the same words.+ * The voice is the platform's own TTS lane, so three.ws narrates three.ws, and+ * captions carry the same words. Every line is synthesized before the camera+ * rolls: filming is real time, so a line fetched mid-take is dead air.** Usage:* npm run demo:video # every feature, all chapters@@ -27,7 +28,7 @@* npm run demo:video -- --dry-run # print the route and exit** Flags:- * --route=full|highlights|quick which stops (default full: every feature)+ * --route=full|highlights which stops (default full: every feature)* --sections=a,b only these chapters (default: all, in order)* --limit=n first n stops per chapter, for a smoke test* --authed replay .auth/audit-state.json (signed-in surfaces)@@ -119,11 +120,6 @@ function lineFor(stop) {/* ── acts ───────────────────────────────────────────────────────────────── */-/*- * A hand-written act for a flagship surface. Each one is a real interaction- * with the real page: nothing here fakes a result, and a selector that has gone- * missing surfaces as a skipped stop rather than a still frame.- *//** A hand-written act for a flagship surface: the real interaction a presenter* would perform, with the lines they would say while performing it. `beat`@@ -261,7 +257,7 @@ const ACTS = {'/launch': async (p, { beat }) => {await p.readThrough({ budgetMs: 5000 });- await beat('An agent can have its own coin, minted on pump dot fun from inside the platform, with the agent as the thing it is attached to.');+ await beat('An agent can have its own coin, minted in one flow from inside the platform, with the agent as the thing it is attached to.');},'/markets': async (p, { beat }) => {