maya-asset-sync git:20260829.f5f5fcaA

Immutable. This exact content never changes and is served at /api/v1/blob/c0ccc1d01df0f473.

---
name: maya-asset-sync
description: Consume and publish content-addressed USD revisions with native-editable or fidelity-first Maya modes.
license: MIT
metadata:
  dcc-mcp:
    dcc: maya
    layer: domain
    stage: interchange
    version: 1.0.0
    tags: [maya, usd, asset-sync, animation-curves, skeleton, materials, lookdev]
    search-hint: "sync asset, Houdini to Maya, editable animation curves, skeleton USD, material sync"
    tools: tools.yaml
---

# maya-asset-sync

Typed cross-DCC revision sync using the shared `dcc-mcp-core.asset_sync` contract.
Filesystem roots are operator-owned environment configuration.

`sync_usd_revision` offers two deliberate editability modes:

- `native`: MayaUSD imports hierarchy, joints, animation as native Maya curves,
  geometry and shader networks for direct editing.
- `usd_proxy`: a `mayaUsdProxyShape` references the immutable layer and retains
  maximum USD composition fidelity for non-destructive layer edits.

The result reports native animCurve, joint, NURBS curve, material, texture and
bounding-box evidence so callers can verify what remained controllable. Native
material evidence also identifies imported Arnold `standardSurface` PBR
materials, their metalness, specular roughness, IOR, transmission, coat, and
connected shader inputs instead of treating a material count as proof of
lookdev fidelity.

Image-texture evidence is path- and color-management-aware. Each bounded
`image_textures` record reports the node and node type, Maya-resolved path and
path attribute, resolved existence, color space, string absoluteness, an
operator-project-relative path when the resolved dependency is under the active
workspace, whether the node came from this import, and any material inputs
reachable through a bounded downstream shading graph. Maya may expand a
portable project path after scene open, so use `under_workspace` and
`workspace_relative_path` rather than treating `is_absolute` alone as a
portability verdict. `file_textures` and
`missing_textures` remain available with their legacy behavior; use
`image_texture_evidence_total`, `image_texture_evidence_limit`, and
`image_texture_evidence_truncated` to audit whether the detailed evidence is
complete.

`rig_expectation` makes rig preservation auditable instead of best-effort:

- `auto` preflights the USD and requires Maya joints whenever a standard
  `UsdSkelSkeleton` is present.
- `skeleton` requires both source `UsdSkel` data and imported Maya joints.
- `skinned` additionally requires authored joint indices/weights and imported
  Maya `skinCluster` nodes.
- `ignore` keeps the legacy permissive behavior for intentionally rigid assets.

Native controller and constraint editability is reported additively under
`evidence.rig_editability`; every legacy evidence field and `editable_set`
retains its existing meaning. A transform counts as a controller only when it
has a valid explicit `dccMcpControllerRole` string tag and a NURBS curve shape.
This avoids guessing from node names or counting groom and guide curves as rig
controls. Controller and native Maya constraint records are deterministically
sorted and bounded; inspect each collection's `total`, `limit`, and `truncated`
fields before treating the record list as complete.

`required_constrained_controller_roles` is an optional fail-closed acceptance
gate for `native` sync. Its default empty array preserves the legacy permissive
behavior. When roles are supplied, every role must identify exactly one
keyable, unlocked NURBS controller and that controller must drive at least one
editable native Maya constraint. Missing, duplicate, locked, or unconstrained
roles return a typed error with the same evidence block. Standard USD/UsdSkel
does not itself guarantee Maya controller shapes or constraint graphs, so only
use this gate when the authored/imported asset carries the explicit role tags
and native rig data required by the pipeline contract.

Constraint evidence preserves Maya's positional target-to-weight-alias mapping.
A controller relation is editable only when its own weight alias can be read and
is unlocked. The sampled weight and `active` flag remain diagnostic evidence;
an unlocked animated weight at zero on the current frame does not make the rig
non-editable.