SimReady Conform FET_100_ISAAC
Purpose
Use this exact feature skill when the selected profile, validation report, or user request names FET_100_ISAAC. It repairs or stages Isaac composition conformance without drifting into another runtime contract.
Default to FET_100_ISAAC@0.4.0 when the user asks for this feature without a version. Use an older 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_100_ISAAC-0.1.0.json
nv_core/tiers/simready_foundation_tier_core/simready/foundation/tier_core/features/FET_100_ISAAC-0.2.0.json
nv_core/tiers/simready_foundation_tier_core/simready/foundation/tier_core/features/FET_100_ISAAC-0.3.0.json
nv_core/tiers/simready_foundation_tier_core/simready/foundation/tier_core/features/FET_100_ISAAC-0.4.0.json
nv_core/tiers/simready_foundation_tier_core/simready/foundation/tier_core/features/FET_100_ISAAC.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 0.4.0 keeps the 0.3.0 contract (FET_003_PHYSX@0.4.0, ISA.001).
It changes only the composition pipeline: prefer producing Isaac composition with
the standalone simready.asset_transformer package
(nv_core/cip_specs/isaac_asset_transformer) using the
simready_physx_to_isaac_prop transform, then validate against the selected
manifest. Older versions remain supported for assets pinned to them.
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_100_ISAAC 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_100_ISAAC 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_100_ISAAC 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_100_ISAAC 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_100_ISAAC@0.4.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-100-isaac3description: "Use for repairing exact FET_100_ISAAC SimReady conformance for Isaac composition conformance. Use when a profile, validation report, or user request names FET_100_ISAAC; default to version `0.4.0` unless a profile or report pins another version."4license: Apache-2.05metadata:6 source: https://skillmd.com/skills/nvidia/simready-foundation-conform-fet-100-isaac7 author: "Shaad Boochoon <sboochoon@nvidia.com>"8 tags:9 - simready10 - conformance11 - isaac12---1314# SimReady Conform FET_100_ISAAC1516## Purpose1718Use this exact feature skill when the selected profile, validation report, or user request names `FET_100_ISAAC`. It repairs or stages Isaac composition conformance without drifting into another runtime contract.1920Default to `FET_100_ISAAC@0.4.0` when the user asks for this feature without a version. Use an older 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_100_ISAAC-0.1.0.json`27- `nv_core/tiers/simready_foundation_tier_core/simready/foundation/tier_core/features/FET_100_ISAAC-0.2.0.json`28- `nv_core/tiers/simready_foundation_tier_core/simready/foundation/tier_core/features/FET_100_ISAAC-0.3.0.json`29- `nv_core/tiers/simready_foundation_tier_core/simready/foundation/tier_core/features/FET_100_ISAAC-0.4.0.json`30- `nv_core/tiers/simready_foundation_tier_core/simready/foundation/tier_core/features/FET_100_ISAAC.md`3132Treat 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.3334## Feature Versions3536| Version | Dependencies | Requirements |37|---|---|---|38| `0.1.0` | FET_003_PHYSX@0.1.0 | `ISA.001` |39| `0.2.0` | FET_003_PHYSX@0.3.0 | `ISA.001` |40| `0.3.0` | FET_003_PHYSX@0.4.0 | `ISA.001` |41| `0.4.0` | FET_003_PHYSX@0.4.0 | `ISA.001` |4243Version `0.4.0` keeps the `0.3.0` contract (`FET_003_PHYSX@0.4.0`, `ISA.001`).44It changes only the composition pipeline: prefer producing Isaac composition with45the standalone `simready.asset_transformer` package46(`nv_core/cip_specs/isaac_asset_transformer`) using the47`simready_physx_to_isaac_prop` transform, then validate against the selected48manifest. Older versions remain supported for assets pinned to them.4950## Workflow51521. Confirm the input exists and identify the exact selected feature/version from the profile TOML, validation report, or user request.532. Load the selected `FET_100_ISAAC` manifest and the feature markdown before editing.543. Load requirement docs linked from the feature markdown for every reported failing requirement.554. Create or use a staged output location unless the user explicitly asks for in-place edits.565. Repair only the requirements listed by the selected `FET_100_ISAAC` manifest and its dependencies.576. 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.587. Summarize the selected `FET_100_ISAAC` version, changed files, validation evidence, and the first remaining blocker or next exact feature gate.5960## Feature Guidance6162- Repair only the requirements listed by the selected `FET_100_ISAAC` manifest and its dependencies.63- Do not add schemas, metadata, or runtime behavior for a sibling runtime feature.64- Report missing runtime/tooling evidence as a validation limitation instead of claiming a pass.6566## Report Fields6768| Field | Meaning |69|---|---|70| `feature` | Exact feature ID and version, for example `FET_100_ISAAC@0.4.0`. |71| `input` | Source asset, package root, or package definition inspected. |72| `output` | Staged output path, or `in-place` only when explicitly requested. |73| `requirements_repaired` | Requirement IDs repaired in this pass. |74| `validation` | Command or inspection used to verify this exact feature. |75| `status` | `passed`, `failed`, `skipped`, or `blocked`. |76| `next_step` | The next exact feature skill or user/runtime evidence needed. |