SimReady Conform FET_004_STANDARD
Purpose
Use this exact feature skill when the selected profile, validation report, or user request names FET_004_STANDARD. It repairs or stages simulate multi-body physics conformance without drifting into another runtime contract.
Default to FET_004_STANDARD@0.2.0 when the user asks for this feature without a version. Use an older integer version only when the profile, validation report, or user explicitly pins it. If the report names a different FET_###_RUNTIME feature, switch to that feature's matching skill before editing.
Source of Truth
Before changing an asset or package, read:
nv_core/tiers/simready_foundation_tier_core/simready/foundation/tier_core/features/FET_004_STANDARD-0.1.0.json
nv_core/tiers/simready_foundation_tier_core/simready/foundation/tier_core/features/FET_004_STANDARD-0.2.0.json
nv_core/tiers/simready_foundation_tier_core/simready/foundation/tier_core/features/FET_004_STANDARD.md
Treat the selected JSON manifest as authoritative for dependencies and requirement IDs. Use the feature markdown for human-readable contract details, requirement links, samples, benchmarks, and adapters.
Feature Versions
| Version |
Dependencies |
Requirements |
0.1.0 |
FET_003_STANDARD@0.1.0 |
JT.001, JT.002, JT.003, JT.ART.002, JT.ART.003, JT.ART.004, RB.MB.001 |
0.2.0 |
FET_003_STANDARD@0.2.0 |
JT.001, JT.002, JT.003, JT.ART.002, JT.ART.003, JT.ART.004, RB.MB.001 |
Workflow
- Confirm the input exists and identify the exact selected feature/version from the profile TOML, validation report, or user request.
- Load the selected
FET_004_STANDARD manifest and the feature markdown before editing.
- Load requirement docs linked from the feature markdown for every reported failing requirement.
- Create or use a staged output location unless the user explicitly asks for in-place edits.
- Repair only the requirements listed by the selected
FET_004_STANDARD manifest and its dependencies.
- Rerun the same profile gate or the narrowest available feature/capability validation gate. If runtime evidence is required and unavailable, report that limitation instead of claiming a pass.
- Summarize the selected
FET_004_STANDARD version, changed files, validation evidence, and the first remaining blocker or next exact feature gate.
Feature Guidance
- Repair standard OpenUSD multibody joint, articulation, and rigid-body requirements without creating new geometry.
- Apply this feature only when the asset has multiple intended rigid bodies, joints, articulation intent, or source multibody structure.
- Skip as not applicable for single-rigid-body props when the selected profile marks FET_004 conditional.
- Runtime-variant packaging. When the asset exposes physics through runtime variant sets, the neutral base owns the runtime-agnostic multibody topology only: rigid bodies,
UsdPhysics joints, exactly one PhysicsArticulationRootAPI, and no local physics:approximation on any collider. Per-runtime collider (and, for Newton, material) annotations are layered into the runnables/physics/<stem>.usd payloads via the FET_000_PHYSX/FET_000_NEWTON/FET_000_MUJOCO skills — never authored on the base.
Report Fields
| Field |
Meaning |
feature |
Exact feature ID and version, for example FET_004_STANDARD@0.2.0. |
input |
Source asset, package root, or package definition inspected. |
output |
Staged output path, or in-place only when explicitly requested. |
requirements_repaired |
Requirement IDs repaired in this pass. |
validation |
Command or inspection used to verify this exact feature. |
status |
passed, failed, skipped, or blocked. |
next_step |
The next exact feature skill or user/runtime evidence needed. |
1---2name: simready-foundation-conform-fet-004-standard3description: "Use for repairing exact FET_004_STANDARD SimReady conformance for simulate multi-body physics conformance. Use when a profile, validation report, or user request names FET_004_STANDARD; default to version `0.2.0` unless a profile or report pins another version."4license: Apache-2.05metadata:6 source: https://skillmd.com/skills/nvidia/simready-foundation-conform-fet-004-standard7 author: "Shaad Boochoon <sboochoon@nvidia.com>"8 tags:9 - simready10 - conformance11 - standard12---1314# SimReady Conform FET_004_STANDARD1516## Purpose1718Use this exact feature skill when the selected profile, validation report, or user request names `FET_004_STANDARD`. It repairs or stages simulate multi-body physics conformance without drifting into another runtime contract.1920Default to `FET_004_STANDARD@0.2.0` when the user asks for this feature without a version. Use an older integer version only when the profile, validation report, or user explicitly pins it. If the report names a different `FET_###_RUNTIME` feature, switch to that feature's matching skill before editing.2122## Source of Truth2324Before changing an asset or package, read:2526- `nv_core/tiers/simready_foundation_tier_core/simready/foundation/tier_core/features/FET_004_STANDARD-0.1.0.json`27- `nv_core/tiers/simready_foundation_tier_core/simready/foundation/tier_core/features/FET_004_STANDARD-0.2.0.json`28- `nv_core/tiers/simready_foundation_tier_core/simready/foundation/tier_core/features/FET_004_STANDARD.md`2930Treat the selected JSON manifest as authoritative for dependencies and requirement IDs. Use the feature markdown for human-readable contract details, requirement links, samples, benchmarks, and adapters.3132## Feature Versions3334| Version | Dependencies | Requirements |35|---|---|---|36| `0.1.0` | FET_003_STANDARD@0.1.0 | `JT.001`, `JT.002`, `JT.003`, `JT.ART.002`, `JT.ART.003`, `JT.ART.004`, `RB.MB.001` |37| `0.2.0` | FET_003_STANDARD@0.2.0 | `JT.001`, `JT.002`, `JT.003`, `JT.ART.002`, `JT.ART.003`, `JT.ART.004`, `RB.MB.001` |3839## Workflow40411. Confirm the input exists and identify the exact selected feature/version from the profile TOML, validation report, or user request.422. Load the selected `FET_004_STANDARD` manifest and the feature markdown before editing.433. Load requirement docs linked from the feature markdown for every reported failing requirement.444. Create or use a staged output location unless the user explicitly asks for in-place edits.455. Repair only the requirements listed by the selected `FET_004_STANDARD` manifest and its dependencies.466. Rerun the same profile gate or the narrowest available feature/capability validation gate. If runtime evidence is required and unavailable, report that limitation instead of claiming a pass.477. Summarize the selected `FET_004_STANDARD` version, changed files, validation evidence, and the first remaining blocker or next exact feature gate.4849## Feature Guidance5051- Repair standard OpenUSD multibody joint, articulation, and rigid-body requirements without creating new geometry.52- Apply this feature only when the asset has multiple intended rigid bodies, joints, articulation intent, or source multibody structure.53- Skip as not applicable for single-rigid-body props when the selected profile marks FET_004 conditional.54- **Runtime-variant packaging.** When the asset exposes physics through runtime variant sets, the neutral base owns the runtime-agnostic multibody topology only: rigid bodies, `UsdPhysics` joints, exactly one `PhysicsArticulationRootAPI`, and **no** local `physics:approximation` on any collider. Per-runtime collider (and, for Newton, material) annotations are layered into the `runnables/physics/<stem>.usd` payloads via the `FET_000_PHYSX`/`FET_000_NEWTON`/`FET_000_MUJOCO` skills — never authored on the base.5556## Report Fields5758| Field | Meaning |59|---|---|60| `feature` | Exact feature ID and version, for example `FET_004_STANDARD@0.2.0`. |61| `input` | Source asset, package root, or package definition inspected. |62| `output` | Staged output path, or `in-place` only when explicitly requested. |63| `requirements_repaired` | Requirement IDs repaired in this pass. |64| `validation` | Command or inspection used to verify this exact feature. |65| `status` | `passed`, `failed`, `skipped`, or `blocked`. |66| `next_step` | The next exact feature skill or user/runtime evidence needed. |