SimReady Conform FET_022_PHYSX
Purpose
Use this exact feature skill when the selected profile, validation report, or user request names FET_022_PHYSX. It repairs or stages PhysX driven-joint conformance without drifting into another runtime contract.
Default to FET_022_PHYSX@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_022_PHYSX-0.1.0.json
nv_core/tiers/simready_foundation_tier_core/simready/foundation/tier_core/features/FET_022_PHYSX-0.2.0.json
nv_core/tiers/simready_foundation_tier_core/simready/foundation/tier_core/features/FET_022_PHYSX.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_004_ROBOT_PHYSX@0.1.0 |
DJ.001, DJ.002, DJ.003, DJ.004, DJ.005, DJ.006, DJ.007, DJ.011 |
0.2.0 |
FET_004_PHYSX@0.4.0 |
DJ.001, DJ.002, DJ.003, DJ.004, DJ.005, DJ.006, DJ.007, DJ.011 |
Version 0.1.0 is retained for compatibility with historical or external
contracts that pin the deprecated FET_004_ROBOT_PHYSX feature. New profile
versions must select FET_022_PHYSX@0.2.0 and its canonical
FET_004_PHYSX@0.4.0 dependency.
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_022_PHYSX 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_022_PHYSX 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_022_PHYSX version, changed files, validation evidence, and the first remaining blocker or next exact feature gate.
Feature Guidance
- Repair only the requirements listed by the selected
FET_022_PHYSX manifest and its dependencies.
- Do not add schemas, metadata, or runtime behavior for a sibling runtime feature.
- Report missing runtime/tooling evidence as a validation limitation instead of claiming a pass.
Report Fields
| Field |
Meaning |
feature |
Exact feature ID and version, for example FET_022_PHYSX@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-022-physx3description: "Use for repairing exact FET_022_PHYSX SimReady conformance for PhysX driven-joint conformance. Use when a profile, validation report, or user request names FET_022_PHYSX; 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-022-physx7 author: "Shaad Boochoon <sboochoon@nvidia.com>"8 tags:9 - simready10 - conformance11 - physx12---1314# SimReady Conform FET_022_PHYSX1516## Purpose1718Use this exact feature skill when the selected profile, validation report, or user request names `FET_022_PHYSX`. It repairs or stages PhysX driven-joint conformance without drifting into another runtime contract.1920Default to `FET_022_PHYSX@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_022_PHYSX-0.1.0.json`27- `nv_core/tiers/simready_foundation_tier_core/simready/foundation/tier_core/features/FET_022_PHYSX-0.2.0.json`28- `nv_core/tiers/simready_foundation_tier_core/simready/foundation/tier_core/features/FET_022_PHYSX.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_004_ROBOT_PHYSX@0.1.0 | `DJ.001`, `DJ.002`, `DJ.003`, `DJ.004`, `DJ.005`, `DJ.006`, `DJ.007`, `DJ.011` |37| `0.2.0` | FET_004_PHYSX@0.4.0 | `DJ.001`, `DJ.002`, `DJ.003`, `DJ.004`, `DJ.005`, `DJ.006`, `DJ.007`, `DJ.011` |3839Version `0.1.0` is retained for compatibility with historical or external40contracts that pin the deprecated `FET_004_ROBOT_PHYSX` feature. New profile41versions must select `FET_022_PHYSX@0.2.0` and its canonical42`FET_004_PHYSX@0.4.0` dependency.4344## Workflow45461. Confirm the input exists and identify the exact selected feature/version from the profile TOML, validation report, or user request.472. Load the selected `FET_022_PHYSX` manifest and the feature markdown before editing.483. Load requirement docs linked from the feature markdown for every reported failing requirement.494. Create or use a staged output location unless the user explicitly asks for in-place edits.505. Repair only the requirements listed by the selected `FET_022_PHYSX` manifest and its dependencies.516. 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.527. Summarize the selected `FET_022_PHYSX` version, changed files, validation evidence, and the first remaining blocker or next exact feature gate.5354## Feature Guidance5556- Repair only the requirements listed by the selected `FET_022_PHYSX` manifest and its dependencies.57- Do not add schemas, metadata, or runtime behavior for a sibling runtime feature.58- Report missing runtime/tooling evidence as a validation limitation instead of claiming a pass.5960## Report Fields6162| Field | Meaning |63|---|---|64| `feature` | Exact feature ID and version, for example `FET_022_PHYSX@0.2.0`. |65| `input` | Source asset, package root, or package definition inspected. |66| `output` | Staged output path, or `in-place` only when explicitly requested. |67| `requirements_repaired` | Requirement IDs repaired in this pass. |68| `validation` | Command or inspection used to verify this exact feature. |69| `status` | `passed`, `failed`, `skipped`, or `blocked`. |70| `next_step` | The next exact feature skill or user/runtime evidence needed. |