Parametric history layer for direct-edit CAD files

The moment this problem becomes real is when an engineer closes a SpaceClaim or Dimension session, reopens the file the next morning, and realizes they can't trace back which fillet, extrusion, or boolean operation caused a downstream mesh error — or worse, has to delete an entire geometry and start over because there's no surgical undo available. The gap persists because direct-edit modelers are architecturally designed to avoid constraint graphs — that's intentional, it's what makes them fast and flexible for geometry repair and simulation prep. But that same architectural choice means there's no natural place to attach a parametric history without rebuilding core parts of the kernel, so the vendors don't do it.

What users actually need isn't a full parametric CAD system — they need a change log they can act on: a timestamped, human-readable record of every geometric operation performed in a session, with enough metadata to replay, branch, or selectively revert those operations. Today, engineers working in direct-edit tools either keep handwritten notes, rely on manual file versioning (save_v1, save_v2, save_final_FINAL), or simply redo work from scratch. That last option is not hypothetical — users explicitly say 'we have to delete total geometry' as a real workflow outcome.

This is a business and not a feature because the vendors have a structural disincentive to fix it: adding a history tree to a direct-edit modeler either breaks the speed advantage that differentiates it, or requires deep kernel changes the engineering team is unlikely to prioritize for a segment that's not their primary buyer. Meanwhile the engineers using these tools inside simulation workflows hit this problem on every project, not occasionally. Rebuilding geometry after a mistake in a simulation prep session can cost 4-8 hours of an engineer's time — that math makes even an expensive standalone add-on look cheap.

What to build

Build a session-recording layer that runs alongside SpaceClaim (and similar direct-edit tools) via API or file-watcher, captures each geometric operation as a named, parameterized step in a local history log, and lets engineers replay or branch that history in a lightweight desktop UI — without modifying the CAD kernel.

Where to start

Start exclusively with SpaceClaim users doing Ansys simulation prep, where the history gap is most complained about, the file formats are known, and the Ansys ecosystem has existing API surface to hook into — this gives you a defensible beachhead before expanding to other direct-edit tools.

The hard part

The hardest early problem is capturing geometric operations at sufficient fidelity across tools that expose little or no scripting API — you may have to rely on file diffing between autosave snapshots, which gives you state changes but not intent, making the history log less actionable than users expect.

How it makes money

Annual per-seat license, priced per engineer, with a 30-day trial that requires no IT approval to run — targets individual engineers who expense tools without procurement involvement.