SimReady Conform FET_003_STANDARD
Purpose
Use this exact feature skill when the selected profile, validation report, or user request names FET_003_STANDARD. It repairs or stages rigid body physics conformance without drifting into another runtime contract.
Default to FET_003_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_003_STANDARD-0.1.0.json
nv_core/tiers/simready_foundation_tier_core/simready/foundation/tier_core/features/FET_003_STANDARD-0.2.0.json
nv_core/tiers/simready_foundation_tier_core/simready/foundation/tier_core/features/FET_003_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 |
None |
RB.COL.001, RB.COL.002, RB.COL.003, RB.COL.004, RB.001, RB.003, RB.005, RB.006, RB.007, RB.009, RB.010 |
0.2.0 |
None |
RB.COL.001, RB.COL.002, RB.COL.003, RB.COL.004, RB.001, RB.003, RB.005, RB.007, RB.009, RB.010 |
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_003_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_003_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_003_STANDARD version, changed files, validation evidence, and the first remaining blocker or next exact feature gate.
Feature Guidance
- Repair only standard OpenUSD rigid-body, collider, mass, and physics-material requirements.
- Do not add PhysX or Newton APIs for this Standard feature.
- Hand off to FET_004_* when the asset has multiple intended rigid bodies, joints, or articulation semantics.
Report Fields
| Field |
Meaning |
feature |
Exact feature ID and version, for example FET_003_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-003-standard3description: "Use for repairing exact FET_003_STANDARD SimReady conformance for rigid body physics conformance. Use when a profile, validation report, or user request names FET_003_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-003-standard7 author: "Shaad Boochoon <sboochoon@nvidia.com>"8 tags:9 - simready10 - conformance11 - standard12---1314# SimReady Conform FET_003_STANDARD1516## Purpose1718Use this exact feature skill when the selected profile, validation report, or user request names `FET_003_STANDARD`. It repairs or stages rigid body physics conformance without drifting into another runtime contract.1920Default to `FET_003_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_003_STANDARD-0.1.0.json`27- `nv_core/tiers/simready_foundation_tier_core/simready/foundation/tier_core/features/FET_003_STANDARD-0.2.0.json`28- `nv_core/tiers/simready_foundation_tier_core/simready/foundation/tier_core/features/FET_003_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` | None | `RB.COL.001`, `RB.COL.002`, `RB.COL.003`, `RB.COL.004`, `RB.001`, `RB.003`, `RB.005`, `RB.006`, `RB.007`, `RB.009`, `RB.010` |37| `0.2.0` | None | `RB.COL.001`, `RB.COL.002`, `RB.COL.003`, `RB.COL.004`, `RB.001`, `RB.003`, `RB.005`, `RB.007`, `RB.009`, `RB.010` |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_003_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_003_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_003_STANDARD` version, changed files, validation evidence, and the first remaining blocker or next exact feature gate.4849## Feature Guidance5051- Repair only standard OpenUSD rigid-body, collider, mass, and physics-material requirements.52- Do not add PhysX or Newton APIs for this Standard feature.53- Hand off to FET_004_* when the asset has multiple intended rigid bodies, joints, or articulation semantics.5455## Report Fields5657| Field | Meaning |58|---|---|59| `feature` | Exact feature ID and version, for example `FET_003_STANDARD@0.2.0`. |60| `input` | Source asset, package root, or package definition inspected. |61| `output` | Staged output path, or `in-place` only when explicitly requested. |62| `requirements_repaired` | Requirement IDs repaired in this pass. |63| `validation` | Command or inspection used to verify this exact feature. |64| `status` | `passed`, `failed`, `skipped`, or `blocked`. |65| `next_step` | The next exact feature skill or user/runtime evidence needed. |