A USD handoff is a composition contract, not universal compatibility

Agree what the receiver is meant to compose

USD is designed to describe and compose scenes from elemental assets, but it does not mean every application interprets every schema, material network, or custom extension the same way. The OpenUSD introduction explains that sublayers stack ordered opinions, references assemble prims, and payloads allow deferred loading. Those are scene-description mechanisms, not a certification that the target will reproduce a source application’s appearance or tools.

Make the root layer an explicit entry point. Include a short README naming the root file, default prim, units, up axis, frames per second, frame range, color expectations, required plugins/schemas, and the one or two views that are acceptance targets. Do not ask a receiving artist to discover which of six similarly named files is the real show root.

Choose composition with intent

Use sublayers when ordered overrides in a shared namespace are the point; use references when you need to bring an asset or subscene under a target prim; use payloads when the working set should be selectively loaded. Those choices have consequences for override strength and load behavior. The OpenUSD FAQ notes, for example, that references and sublayers have different strength behavior and that a payload can remain untraversed when a stage opens with a no-payload load set.

Test interchange, not a slogan

Run the package from a clean location on the target application/version. Check missing dependencies, prim paths, transforms, animation timing, variants, materials, cameras, and active payloads. If the target substitutes or drops a feature, record the result as an interoperability exception. Unreal itself labels its USD documentation as Beta and its USD guide frames the system as interchange for complex scenes—not a blanket guarantee of equivalence.

Illustrative example: a city scene uses payloads for blocks outside the camera. The handoff specifies that the acceptance shot opens only Blocks A–C and that Block D is deliberately unloaded. If the receiver sees an empty district, they can distinguish intended working-set behavior from a broken path.

Handoff checklist

• Package only declared dependencies; do not rely on sender-local absolute paths.
• Declare the authoritative root and edit target for any requested change.
• State which material, renderer, or custom schemas are outside the tested scope.
• Keep a receiving-side result: pass, pass with exceptions, or fail with reproducible steps.

This is an Atlas process for reducing ambiguity. It deliberately avoids saying USD is “universal”; the receiver still needs to validate the exact intended exchange.