docs(models): HY-Motion 1.0 decision record — rejected on license (#793)

[fernandotonon]

Resolves #793 the way #408 (RigNet) and the #830 UniRig-skin-head evaluations were resolved: as a documented decision record in THIRD_PARTY_AI_MODELS.md.

Evaluation outcome

Feasibility was not the blocker. The technical plan in #793 (ONNX export of the 0.46B Lite DiT with the flow-matching sampler loop in C++, int8/fp16 quantization, SMPL→22-joint canonical adapter) mirrors integrations already shipped here (UniRig, TripoSG, SkinTokens).

The license is disqualifying on three independent grounds (Tencent HY-MOTION 1.0 Community License, reviewed against the verbatim LICENSE.txt on the HF repo):

1. Territory exclusion — "'Territory' shall mean the worldwide territory, excluding the territory of the European Union, United Kingdom and South Korea"; the agreement "DOES NOT APPLY" there. QtMeshEditor distributes worldwide — the same ground on which Hunyuan3D was rejected for Epic: AI — Image-to-3D mesh generation (TripoSR via ONNX) #764.
2. Outputs are territory-restricted too — "You must not use, reproduce, modify, distribute, or display the … Output or results … outside the Territory." This kills even the issue's opt-in-download escape hatch: an asset editor cannot hand users generated animations they may not legally use or display in the EU/UK/South Korea.
3. 1 million MAU cap with discretionary relicensing — 10× stricter than Hunyuan3D's 100M.

The template clip library stays the default, our from-scratch CVAE stays the experimental opt-in, and the #793 export plan remains on file for any permissively-licensed successor (or a Tencent relicense, which has precedent with some Hunyuan variants).

Closes #793

🤖 Generated with Claude Code

[coderabbitai]

Warning

Review limit reached

@fernandotonon, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 44 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: d0ac06dd-8e92-4038-8574-09285ebbb8c7

📥 Commits

Reviewing files that changed from the base of the PR and between fe0deff and 3120d92.

📒 Files selected for processing (1)

• THIRD_PARTY_AI_MODELS.md

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch docs/hy-motion-793-decision

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud