Prepare and inspect geometry

Start from an owned, verified geometry artifact. Record its units, checksum and lineage. Uploaded CAD, implicit-design exports and mesh previews are different resources; use the actual geometry output as the meshing input.

Use inspect_mesh_geometry for bounds and, when supported, component evidence. Use check_geometry for the available closure, size and solid checks. A bounds-only result does not establish watertightness or valid structured component IDs.

Check before planning

Confirm scale against a known physical dimension, orientation against the operating flow direction, and the smallest gap or feature the analysis must resolve. Remove unintended duplicate bodies and distinguish physical regions from display helpers. Keep intentional openings and named boundary patches identified.

For STL, units may be absent. Use declared provenance or a known dimension to resolve scale. If multiple unit interpretations remain plausible, ask for one real dimension; do not select the one that happens to make a meshing request pass.

For STEP assemblies, inspect solid names and which solids are actual fluid and material volumes. CHT workflows requiring explicit fluid bodies cannot infer coolant merely from a cavity in a solid.

Geometry preparation can return a durable operation_id. Poll that operation and reuse its completed result. Inspection is not permission to start a mesh or silently repair a geometry feature that matters to the design.

See uploads and inspection, units and implicit exports.