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
style(structure): drop the banned em-dash from the marketing assets row
nirholas81f798f106b7
diff --git a/STRUCTURE.md b/STRUCTURE.mdindex 641fab65f..6bb054723 100644--- a/STRUCTURE.md+++ b/STRUCTURE.md@@ -452,7 +452,7 @@ array. Runbook: [docs/contributing.md](docs/contributing.md#publishing-packages-- **API endpoints** — [api/](api) (serverless-style handlers, served in production by the [server/](server) Cloud Run container), [workers/](workers) (long-running workers)- **Examples & demos** — [examples/](examples), [multiplayer/](multiplayer)- **Announcement pipeline**: [docs/announcements/](docs/announcements/README.md) (one pack per feature: the claim and its evidence, the postable text, the media by shot id, the Telegram variant), [data/announcements.json](data/announcements.json) (the ledger: every shipped surface, whether it was ever announced, its score and its stage), [data/announce-media.json](data/announce-media.json) (media recipes captured from the live product into `public/announce/`), [docs/announce-voice.md](docs/announce-voice.md) (the voice contract, derived from the engagement archive). `npm run announce:rank` ranks the backlog, `npm run announce:media` captures the frames, `npm run check:announce` gates a pack. Nothing here posts: publishing stays owner-gated.-- **Marketing assets** — [marketing/](marketing/README.md) (produced promo videos + re-render scripts, e.g. [marketing/imessage-video/](marketing/imessage-video); source-of-truth assets, not shipped to production). The narrated product demo lives in [marketing/product-demo/](marketing/product-demo/README.md): [scripts/make-product-demo.mjs](scripts/make-product-demo.mjs) (`npm run demo:video`) films a presenter walking every feature page on the live site, chaptered, with narration from the platform's own TTS lane. Its route is the Feature Tour curriculum, so a new page is in the next recording without editing a script. Docs: [docs/product-demo.md](docs/product-demo.md)+- **Marketing assets**: [marketing/](marketing/README.md) (produced promo videos + re-render scripts, e.g. [marketing/imessage-video/](marketing/imessage-video); source-of-truth assets, not shipped to production). The narrated product demo lives in [marketing/product-demo/](marketing/product-demo/README.md): [scripts/make-product-demo.mjs](scripts/make-product-demo.mjs) (`npm run demo:video`) films a presenter walking every feature page on the live site, chaptered, with narration from the platform's own TTS lane. Its route is the Feature Tour curriculum, so a new page is in the next recording without editing a script. Docs: [docs/product-demo.md](docs/product-demo.md)- **Platform agents (server-side)**: [agents/](agents/README.md) (endpoint-shopper, fact-checker, tutor, unstoppable, x402-buildout: library modules imported by `api/` handlers, each with its own README)- **Site data files**: [data/](data/README.md) (pages.json, changelog.json, skills seed, RSS items: what each file drives and which script regenerates it)- **Repository guards**: [data/guards.json](data/guards.json) is the registry of every mechanical check and the stage it runs in (prebuild, gate, deploy build, pre-push, on demand). [scripts/audit-guards.mjs](scripts/audit-guards.mjs) proves each entry is real and each stage claim is true, [scripts/build-guards.mjs](scripts/build-guards.mjs) publishes it to `public/guards.json`, [pages/guards.html](pages/guards.html) renders it at `/guards`, and [docs/guards.md](docs/guards.md) plus [docs/tutorials/write-a-guard.md](docs/tutorials/write-a-guard.md) document it. There is no CI here, so this is the enforcement layer.