Model Capabilities and Mapping
A model package must describe the concrete facts of its selected Live2D or VRM backend. Avatar validates those facts before admitting any route. A file's presence on disk, a loose confidence score, or creator-supplied JavaScript does not establish support.
Capability Profile
Follow the backend capability profile schema:
profile_id,backend_kind, andmodel_fingerprintidentify the profile and model.generated_motiondeclares disjoint supported and unsupported routes plus safety limits.- A VRM profile records humanoid bones, expression presets, look-at targets, and pose limits.
- A Live2D profile records motion groups, expression IDs, and parameter IDs.
Declare only the capabilities that the model actually possesses. A missing or mismatched profile, as well as unsupported route targets, will fail closed.
Mapping Sidecar
The current generated-motion catalog targets VRM, and its sidecar parser requires backend_kind=vrm. Live2D uses built-in mapping from its own motion groups, expressions, and parameter facts rather than gaining routes through these VRM sidecars.
A sidecar associates one admitted Avatar route with validated model targets. It uses route_id, the matching profile_id, confidence and threshold, source classification, confirmation, and target fields. It does not contain keyframes or a fallback route. See Generated Motion Provider for the exact fields and a structural example.
For an LLM-derived name mapping, manual confirmation is required before admission. Confidence must meet the configured threshold; it is not a tie-breaker among candidates.
Check a Model Change
- Match the model fingerprint and backend kind to its capability profile.
- Check each claimed route against the current route catalog and model facts.
- Validate any sidecar against the closed schema and matching profile.
- Run the full Avatar presentation path for the changed behavior, and inspect the returned failure diagnostics if unsupported.
Local diagnostics help inspect a selected model, but fixture output alone does not establish live product readiness. See Backend Diagnostics and Visual Acceptance.