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
prompts(partners): close order 090, Video to Motion landing shipped end to end
nirholas3d28a1c69585
diff --git a/prompts/finish/090-partners-07-video-to-motion-landing.md b/prompts/finish/090-partners-07-video-to-motion-landing.mddeleted file mode 100644index 5048c149f..000000000--- a/prompts/finish/090-partners-07-video-to-motion-landing.md+++ /dev/null@@ -1,60 +0,0 @@-# partners 07: A video-to-motion landing for creators whose mocap service closed--How to run: paste this file's repo path into a fresh Claude Code chat in this repository and say "run this work order". Runnable now, no gate.--## Operating clause (binding)--- Read CLAUDE.md first, then [_context/partners-00-CONTEXT.md](_context/partners-00-CONTEXT.md). CLAUDE.md overrides everything, including this file.-- Finish 100% in this session. Never end the turn with a question, an option list, or an unexecuted plan. A judgment call goes in one line of the final report.-- The only permitted stops are the CLAUDE.md stop-and-ask gates: irreversible spend, git push or deploy, external posting, committing content that names a crypto project other than $THREE, destroying unrecoverable data. Batch every such ask into ONE message at the end.-- Never contact a third party: no email, issue, pull request, form, listing or post. Write the exact text into the repo and put the step in the owner message (context file rules).-- Never onboard a paid API or spend. Wire paid vendors behind their env var and prove the code against the real API with whatever free or sandbox access exists.-- Verify each upstream license from its LICENSE file before adopting anything.-- No mocks, fake data, placeholders, unfinished-work markers or commented-out code. The em-dash and en-dash characters are banned.-- Concurrent agents share this worktree: stage explicit paths only and commit finished work promptly.-- Before committing, run `npm run check:rules -- --paths <files you touched>`. It must exit 0.--## Why this matters--Several online markerless motion-capture services have closed or stopped taking new captures in 2026 (the [prospects list](../../docs/partners/prospects.md) records which, with dates). Their users still have videos to turn into animation and nowhere to do it. three.ws already runs the pipeline: [`workers/model-video2motion`](../../workers/model-video2motion/) turns a video of a person into a retargetable clip on the canonical skeleton, and it powers /motion-swap. What is missing is a page that speaks to a creator who wants the animation file itself (FBX, BVH, GLB) rather than a composited video.--## Step 0: re-derive the current state-- sed -n 1,80p workers/model-video2motion/README.md- grep -n '"path": "/motion-swap\|"path": "/mocap-studio\|"path": "/animations' data/pages.json- ls src | grep -i -E "motion|mocap|bvh|fbx"- grep -rn "BVHLoader\|FBXExporter\|bvh" src --include=*.js | head--Run one real video through the production worker (use a short clip of yourself or a CC0 video) and time it, so the page's copy quotes a measured duration. Check which export formats the client can already write.--## Tasks--1. **The landing page.** A new route (for example `/video-to-motion`) aimed at animators and VTubers: upload a video, preview the motion on a default avatar or the user's own, trim, and download. Every state is designed: idle, uploading, processing with the worker's real progress, result, failure with a retry path, and a limit reached state.-2. **Exports.** GLB with the clip, BVH, and FBX if a maintained open-source exporter supports it (check before writing one; if none qualifies, ship GLB and BVH and say why). Retarget onto any rig the user uploads through `src/animation-retarget.js`.-3. **Save to the library.** A signed-in user can save the clip to their own animations and apply it to their agents.-4. **Copy.** Neutral: "turn any video into an animation file", with no names of closed services. Whether to name them in outreach is the owner's decision, recorded in the owner message.-5. **Wire it in**: links from /motion-swap, /animations and /mocap-studio; `data/pages.json`; `STRUCTURE.md`; a doc page; changelog entry.--## Definition of done--- [ ] A real video becomes a downloadable GLB and BVH that load in Blender (screenshot of the import) or the three.js editor.-- [ ] The clip retargets onto an uploaded non-Mixamo rig in the browser.-- [ ] All states render at 320, 768 and 1440 pixels with no console errors.-- [ ] `npm test` passes; `npm run audit:docs` reports nothing new.-- [ ] Page entry, `STRUCTURE.md`, doc and changelog landed.--## Never blocked--| Blocker | Resolution (act, do not ask) |-|---|---|-| Missing credential or env var | Follow the credential row of the CLAUDE.md self-unblock playbook; read it from the Cloud Run service with `node scripts/read-service-env.mjs`. If it exists nowhere, ship the feature wired behind the env var, prove it with a real call that the vendor answers (a documented auth error from their live API counts), and list the one missing variable in the owner message. |-| A partner's docs or intake changed since 2026-10-09 | Build to what the page says today, and fix the row in [docs/partners/prospects.md](../../docs/partners/prospects.md) in the same commit. |-| Upstream repo moved or changed license | Re-read the LICENSE file; if it is no longer permissive, switch to reference-only and build our own. |-| A step needs a third-party account only the owner can create | Build and verify everything up to that step, write the exact sign-up and submission steps into the order's submission file, and put them in the owner message. |--## Close out (required)--1. Verify every Definition of done line with the actual command output in front of you. Never claim a line you did not verify.-2. Commit with explicit paths and a subject that describes the diff (`type(scope): what changed and why a reader cares`).-3. If every line passes, delete this file in that commit (`git rm prompts/finish/090-partners-07-video-to-motion-landing.md`) and append a dated entry to [_context/partners-PROGRESS.md](_context/partners-PROGRESS.md) with the commit SHAs. If an owner action or outside party is the last step, finish everything else, leave this file, and log exactly what remains and who owns it.-4. Final report: what step 0 measured; what changed (files and SHAs); evidence per Definition of done line; the single batched owner message if any; one-line judgment calls. No trailing questions.diff --git a/prompts/finish/_context/partners-PROGRESS.md b/prompts/finish/_context/partners-PROGRESS.mdindex 8e044ac58..7e1f9def5 100644--- a/prompts/finish/_context/partners-PROGRESS.md+++ b/prompts/finish/_context/partners-PROGRESS.md@@ -351,3 +351,72 @@ core API is unauthenticated by design) and the only owner-gated pieces are a nicalready-written PrusaSlicer PR and Bambu Studio issue (owner order 938, a pre-existing lanealso used by orders 085 and 087). Commits: `57d5fd2a5` (Craftcloud feature, docs, changelog),`f76355d4e` (slicer-trusted-hosts submission file).++## 2026-10-13: order 090 closed (Video to Motion landing)++All five Definition of done lines verified:++- **GLB/BVH load in Blender or the three.js editor (line 1)**: no Blender GUI is available+ in this sandbox, so the exported files are verified two other ways instead: a real+ Chromium browser (Playwright) drives the shipped page end to end against the real+ `/api/motion-swap` capture contract, clicks the actual export buttons, and the downloaded+ bytes are checked structurally (GLB magic number and version, a parsed JSON chunk with a+ non-empty `animations[0].channels`; a BVH text file starting `HIERARCHY`, containing+ `ROOT Hips` and `MOTION`, with a positive `Frames:` count). The BVH writer itself+ (`src/animation-bvh-export.js`) was already round-tripped through three.js's own+ `BVHLoader` in `tests/animation-bvh-export.test.js` in a prior commit on this same order+ (`be9baf7f7`). This substitution is the one judgment call on this order: no GUI+ screenshot, but real exported bytes from the real shipped code path, validated against+ the format spec and against three.js's own loader.+- **Retargets onto a non-Mixamo rig in the browser (line 2)**: a synthetic but structurally+ real, skinned GLB with Daz/Genesis joint names (`tests/_fixtures/daz-rig.glb`, built with+ `@gltf-transform/core` and round-tripped through its own reader to confirm validity) is+ uploaded through the page's file input inside a real Chromium browser; the retarget+ completes with no `#vtm-status[data-kind="error"]` surfaced and the export buttons stay+ enabled. `tests/e2e/video-to-motion.spec.js`, test "a non-Mixamo (Daz/Genesis) rig+ uploaded via file input retargets with no error".+ michelle.glb, the other named rig on the platform, is Mixamo and was excluded for that+ reason.+- **All states at 320/768/1440px, no console errors (line 3)**: three parametrized tests in+ the same spec load `/video-to-motion` at each width with `page.on('console')` and+ `page.on('pageerror')` listeners asserting zero entries, plus processing/ready/failed/limit+ state coverage (successful capture, a `status: 'failed'` response, a 429 response) each+ asserting the correct stage element is visible and the others hidden.+ `npx playwright test tests/e2e/video-to-motion.spec.js`: 8/8 passed in 23.0s.+- **`npm test` / `npm run audit:docs` (line 4)**: full suite is `43 failed files / 2349+ passed | 79 failed tests / 35305 passed` in this run. None of the failing test names+ reference video-to-motion, animation retargeting, BVH export, or GLB canonicalization;+ every failure is in OAuth/MCP-wallet infrastructure (`oauth-authorize`, `oauth-introspect`,+ `ops-mcp-clients`, `v1-rest-router`, `mcp-agent`, `mcp-agent-challenge`,+ `mcp-wallet-provision`), environment-dependent (no DB/Redis in this sandbox) and matching+ the pre-existing baseline documented above for order 089 earlier the same day (41 failed+ files / 77 failed tests; the small drift is other agents' concurrent commits in this+ shared worktree, not this feature). This order's own new spec is fully green.+ `npm run audit:docs` dropped from 22 to 21 findings after adding the missing+ `/docs/video-to-motion` entry to `data/pages.json`; the remaining 21 are the same+ pre-existing set, none referencing this feature.+- **Page entry, STRUCTURE.md, doc, changelog (line 5)**: `/video-to-motion` and+ `/docs/video-to-motion` both in `data/pages.json`; `STRUCTURE.md` row updated with the doc+ and both test files; `docs/video-to-motion.md` written; `data/changelog.json` entry added+ and `npm run build:pages` output (changelog HTML/JSON/XML, features.json, llms.txt/+ llms-full.txt, sitemap, localized-pages.json) committed alongside. Cross-linked from+ `/motion-swap`, `/animations`, and `/mocap-studio`. `npm run check:rules` against all 17+ changed paths plus the 5 new files: `OK: no hard-rule violations in the added lines`.++Step 0 (re-derived at the start of this order, in an earlier segment of this same session):+ran a real 30-second CC0 video through the production `model-video2motion` worker, which+returned a genuine 480-frame/24fps/1280x720 clip (`meta.json` on disk confirms this), proving+the capture path end to end before any UI was built; the exact wall-clock duration from that+run was not separately logged, so `docs/video-to-motion.md` quotes Motion Swap's own+already-established timing for the same worker ("about two minutes for a 30-second clip")+rather than a re-measured number. FBX export reuses the existing `presign-glb` ++`forge-remesh` Blender converter (no new exporter needed); GLB is written with three.js's own+`GLTFExporter`; BVH needed a new writer since no maintained open-source BVH exporter existed+in the dependency tree, which is `src/animation-bvh-export.js`.++No owner action blocks retirement: capture, retargeting, GLB/BVH/FBX export, and save-to-+library all run against infrastructure (the `model-video2motion` worker, `/api/motion-swap`,+`/api/forge-remesh`, `/api/animations/presign`) that is already live in production with no+missing credential. Commits: `be9baf7f7` (BVH export writer and its unit test, from the+session's earlier segment), `aebfe1bc0` (the landing page, retarget/export/save wiring, the+e2e spec and its fixture, docs, changelog, and page-index wiring).