SimReady Conform FET001STANDARD Minimal

Purpose

Use this workflow skill after FET_000_STANDARD passes and the next profile validation gate is FET_001_STANDARD. It brings an existing USD asset toward the Minimal/Standard feature contract while preserving visual scale, hierarchy intent, and source traceability.

This is an authoring and repair skill, not the final validator. Work on a staged copy under the requested output directory, rerun the same validation gate after each repair stage, and stop at the first remaining failing FET_001_STANDARD validation gate.

Prerequisites

Read the source-of-truth files named below before editing. Work on staged outputs where the skill requires them, and keep validation evidence with the result.

Source of Truth

Before changing an asset, load the exact FET_001_STANDARD manifest selected by the profile:

• nv_core/tiers/simready_foundation_tier_core/simready/foundation/tier_core/features/FET_001_STANDARD-0.1.0.json
• nv_core/tiers/simready_foundation_tier_core/simready/foundation/tier_core/features/FET_001_STANDARD-1.0.0.json
• nv_core/tiers/simready_foundation_tier_core/simready/foundation/tier_core/features/FET_001_STANDARD-1.0.1.json
• nv_core/tiers/simready_foundation_tier_core/simready/foundation/tier_core/features/FET_001_STANDARD.md

Profiles may select FET_001_STANDARD@0.1.0, FET_001_STANDARD@1.0.0, or FET_001_STANDARD@1.0.1. Treat the JSON manifest requirement list as authoritative for the selected profile/version.

For per-requirement repair details, read references/fet001-requirements.md when a FET_001_STANDARD validation report or inspection identifies matching failures.

Inputs

Collect these before editing:

Input	Requirement
usd_asset	Required .usd, .usda, .usdc, or unpacked USD-family asset to repair.
output_root	Required or inferred folder for staged assets and reports.
simready_profile	Profile being validated, such as Prop-Robotics-Neutral.
profile_version	Profile version, if supplied by the user or validation command.
fet001_version	Optional explicit FET_001_STANDARD version. Default to latest checked-in version 1.0.1 when neither the user nor the selected profile/report specifies a version.
validation_report	Preferred JSON or markdown report from the failing profile/feature validation gate.
source_asset	Original CAD, DCC, URDF, MJCF, or conversion input path, used for provenance.
physical_size_policy	Whether to preserve physical size. Default to preserve size.

Instructions

Use this checklist when changing the repository:

1. Confirm the input asset exists and that FET_000_STANDARD is already passing on the same staged asset. If Core still fails, hand back to simready-foundation-conform-fet-000-standard first.
2. Select the FET_001_STANDARD version:
   • Use the version explicitly requested by the user when present.
   • Otherwise use the exact FET_001_STANDARD version selected by the profile or validation report.
   • Otherwise default to latest checked-in version 1.0.1.
3. Load the selected manifest and references/fet001-requirements.md. Only repair requirements present in that selected manifest.
4. Parse the validation report and filter to FET_001_STANDARD failures. Do not repair later profile features in this skill.
5. Create a staged output folder under output_root; do not mutate the source unless the user explicitly asks for in-place repair.
6. Run or inspect minimum USD metadata: stage openability, default prim, root prims, upAxis, metersPerUnit, composed bounds, mesh/geometry counts, authored references, and used layers.
7. Apply deterministic fixes in this order, skipping requirement IDs that are not in the selected manifest:
   • Atomic asset/file fixes for AA.001 and AA.002.
   • Hierarchy fixes for HI.001, HI.003, and HI.004.
   • Unit and orientation fixes for UN.001, UN.002, UN.006, and UN.007.
   • Minimal visual geometry fixes for VG.001 or VG.MESH.001.
   • Mesh quality fixes for VG.002, VG.008, VG.014, VG.027, VG.028, and VG.029.
   • Origin placement fixes for VG.025 only when the asset placement convention is clear.
8. Rerun the same profile validation gate, or the narrowest available FET_001_STANDARD validation gate for the selected version.
9. Summarize the stage as passed, failed, skipped, or blocked. Stop when the selected FET_001_STANDARD version passes or the next FET_001_STANDARD failure requires upstream conversion, source geometry, or user intent.

Version Selection

Default to FET_001_STANDARD@1.0.1 for open-ended conformance requests such as "repair FET_001_STANDARD" or "make this Minimal compliant." Use @1 or @2 only when the user, profile, validation report, or migration task explicitly selects that older contract.

Selected Version	Manifest	Conformance Target
0.1.0	FET_001_STANDARD-0.1.0.json	Original Minimal visual-presence contract: atomic asset, declared units/up axis, meter scale, imageable geometry, and default prim.
1.0.0	FET_001_STANDARD-1.0.0.json	Mesh-quality Minimal contract: version 0.1.0 retained requirements plus Z-up, mesh representation, extents, topology, winding, normals, single root, xformable root, and origin placement.
1.0.1	FET_001_STANDARD-1.0.1.json	Latest Minimal Standard contract: version 1.0.0 plus VG.008 cached extent conformance.

If an older report uses legacy feature versions, map them before loading the manifest:

Legacy Version	Current Version
0.1.0	1
1.0.0	2
1.0.1	3

Unit Repair Policy

Treat UN.007 with extra care. Setting metersPerUnit = 1.0 without adjusting authored coordinates can change the apparent physical size of an asset.

Default policy:

• Preserve physical size.
• Record the original metersPerUnit, composed bounds, default prim, and root transforms before editing.
• If the asset uses millimeters, such as metersPerUnit = 0.001, normalize to meter units by scaling authored linear data by 0.001 or by applying an equivalent root-scale normalization in the same staged USD file.
• Recompute authored extents after any geometry-space rescale.
• Validate that the composed bounds in meters are unchanged within a small tolerance.

Prefer these approaches in order:

Strategy	Use When	Notes
Re-export from converter with meter units	Conversion options are available and reliable.	Best long-term fix because geometry, metadata, and derived data are generated consistently.
Rescale staged USD data	All relevant layers are local and editable.	Multiply points, translate ops, extents, and other linear authored values by old_meters_per_unit / 1.0, then set stage metersPerUnit = 1.0.
Apply root-scale normalization in the same staged USD	The asset root has no existing authored xform ops and the selected FET_001_STANDARD version does not reject a root scale.	Set stage metersPerUnit = 1.0 and add a root scale op equal to old_meters_per_unit / 1.0. This strategy is useful for millimeter- or centimeter-authored converter output when a root scale is acceptable.
Create a meter-unit wrapper	The package/validator contract allows a local USD payload reference without violating Core or atomic-asset rules.	Verify FET_000_STANDARD and AA.001 immediately. Current validators may reject extra USD files under simready_usd (NP.005) or ../payloads/... references as outside the asset root (AA.001).
Metadata-only change	The coordinates are already in meters, or the user accepts a physical size change.	Report this explicitly because it can make the asset too large or too small.

For any asset with metersPerUnit = 0.001, a size-preserving single-file repair can set metersPerUnit = 1.0 and author root op xformOp:scale:meter_normalization = (0.001, 0.001, 0.001), assuming the root transform is otherwise safe to modify.

Examples

Example request:

Repair FET_001_STANDARD minimal stage failures on a staged USD asset.

Expected result summary:

staged_asset: repaired copy or output directory
validation: selected feature/profile gate and report path
remaining_failures: next failing requirement IDs, if any

Repair Policy

Make automatic repairs only when the result is mechanical and locally verifiable:

• Set missing upAxis to Z when the asset is already visually Z-up or when the selected profile requires Z-up.
• Set defaultPrim to the single root prim when there is exactly one valid root.
• Wrap multiple roots under a new Xform only when all asset content can be moved or referenced without breaking paths.
• Convert search paths to anchored relative paths only after the dependency is inside the staged asset root.
• Author extents using USD-computed bounds for local editable meshes.
• Normalize or generate mesh normals only when the intended smoothing can be inferred or the converter already produced enough topology to compute them deterministically.
• If adding a root-scale normalization, check for existing root xform ops first. If the root already has meaningful transform ops, preserve order and semantics or use data-space rescaling instead.

Block and report instead of guessing when:

• The feature failure comes from missing or non-mesh geometry that requires upstream conversion.
• Unsupported file types require lossy texture/audio/geometry conversion.
• Winding, normal direction, or origin placement cannot be inferred from local geometry.
• Rescaling would require editing external layers that are not staged with the asset.
• A unit wrapper or payload layout causes FET_000_STANDARD or AA.001 to regress.

Validation Handoff

Preserve reports under the staged output directory. If the Physical AI Skill Hub validation commands are available, use:

uv run --python 3.12 validate-usd-minimum <staged-usd> \
  --report <output-root>/minimum-usd-after-fet001.json

uv run --python 3.12 validate-simready-profile <staged-usd> \
  --profile <profile> \
  --profile-version <version> \
  --foundation-root <simready-foundation-root> \
  --foundation-spec-root <simready-foundation-root>/nv_core/sr_specs/docs \
  --report <output-root>/simready-profile-after-fet001.json

Count this skill as successful when FET_001_STANDARD passes, even if the full profile still fails on later features such as rigid bodies, multibody physics, or grasp vectors. Report those remaining failures as handoff work for their own skills.

Limitations

• Do not silently mutate the source asset; work on the requested staged output.
• Do not hide later profile failures after the selected feature gate passes or fails.
• Do not invent geometry, metadata, or runtime behavior that conflicts with the asset intent.

Troubleshooting

• Error: validation tooling is unavailable. Solution: run the narrowest available USD or static check and report the gap.
• Error: a repair would change asset intent. Solution: stop and ask for direction or stage the smallest reversible edit.
• Error: later profile gates still fail. Solution: report the next failing feature and hand off to the matching conformance skill.

Resources

• assets/openai.yaml preserves optional UI metadata for clients that read skill display hints. It is not required for the workflow.
• references/ contains detailed requirement notes; load only the files needed for the active validation failure.

Summary Format

Report:

Field	Meaning
input_usd_path	Original USD path.
output_usd_path	Latest staged/repaired USD path.
profile and profile_version	Validation target.
fet001_version	Selected FET_001_STANDARD manifest version; default is 1.0.1 unless explicitly overridden.
requirements_repaired	Requirement IDs changed by this skill.
requirements_blocked	Requirement IDs that need user intent or upstream conversion.
scale_preserved	Whether composed physical bounds were preserved after unit repair.
validation_report	Path to the rerun validation report.
next_step	Usually the next failing profile feature.

Keep the user-facing summary short: what was fixed, whether the asset scale was preserved, what FET_001_STANDARD result validation reported, and the first remaining validation gate.