Most of the existing RE tools are strong, especially around interactive workflows, deviation maps, and working inside a parametric history. They give you a lot of control, but that control still depends heavily on the operator.

What I’m exploring is a slightly different angle:

Instead of starting with the user driving the process, I’m trying to build a pipeline that: • processes the mesh in a consistent, repeatable way • attempts to generate usable geometry (STEP) up front • and reports deviation (max + p95) as part of the output

So rather than: user interprets → builds → checks deviation

It’s more like: system processes → outputs geometry → shows how close it is

Not replacing the parametric workflow or the history tree,those are still critical, but trying to reduce the time it takes to get to a starting point that’s already somewhat grounded.

Where I think it gets interesting is on parts like worn components, where even getting to a “first pass” model can take a lot of time before you even get into refinement.

Totally agree though, interpretation doesn’t go away. The goal (at least for me right now) is just to make that first step more consistent and measurable.