---
title: "Overview"
description: "Every Rigyd asset is checked against the SimReady Foundation specification before it ships. Here is what that means."
---

import { Aside } from '@astrojs/starlight/components';

Every asset that comes out of a Rigyd conversion is checked against the [SimReady Foundation specification](https://nvidia.github.io/simready-foundation/) before the job is marked `completed`. We do not ship a "SimReady" label on assets that do not actually meet the spec.

If you have ever opened a USD in Isaac Sim and watched it fall through the floor, intersect itself, or refuse to articulate, you already know what this is for. Validation is the line between "loads in a viewer" and "drops into a simulator and behaves."

## What we conform to

The [SimReady Foundation](https://nvidia.github.io/simready-foundation/) is an open specification layer on top of [OpenUSD](https://openusd.org/) that defines exactly what a simulation-ready asset must contain — naming and folder structure, units, hierarchy, geometry, visual and non-visual materials, semantic labels, rigid-body and collision physics, joints and articulation, and runtime-specific requirements for [PhysX](https://docs.omniverse.nvidia.com/extensions/latest/ext_physics.html) and [NVIDIA Isaac Sim](https://developer.nvidia.com/isaac/sim). The foundation packages these requirements into [features](https://nvidia.github.io/simready-foundation/guides/features/features.html) and rolls them up into [profiles](https://nvidia.github.io/simready-foundation/guides/profiles/profiles.html) — concrete bundles you can target.

Rigyd's validator implements the full requirement registry — every code from `NP.001` (prim naming) through `RC.009` (root joint pinned per robot type) — and runs it on every successful conversion. A conversion is only `completed` when the asset clears the profile we are targeting for that asset class.

<Aside type="caution" title="Opting out">
  Validation is on by default. If you are intentionally submitting an asset you know will not conform — a debug fixture, a partial mesh you want to inspect mid-pipeline — set `skip_validation: true` on the [3D](/conversions/3d-to-simready), [2D](/conversions/2d-to-simready), or [Text](/conversions/text-to-simready) → SimReady request. The asset will still be exported as USD; it just will not have been checked against the spec, and you should not assume it will load cleanly in a simulator. Assets that bypass validation are not "SimReady" in the spec sense — they are USD files that happen to come out of the SimReady pipeline.
</Aside>

## Where to go next

- [What's covered today](/simready-validation/coverage) — the profile we target and the spec areas it enforces.
- [What's coming next](/simready-validation/roadmap) — how our coverage tracks the SimReady Foundation's published profile families.
- [Full requirement coverage](/simready-validation/full-coverage) — every requirement code in the spec and our current status against it.