Thanks!

I have 13 or 14 bullet points that took me about 45 minutes to draft.

Here's an excerpt (just six):

— finding non-symmetrical control points and automatically balancing them or by teaching the user how to apply constraints (thank you, a 2nd time, 24c, as I only thought of this while drafting my response to your post) tho, if mirrored, constraints-based control points reach a crazy-high amount, constraints will be a severe maintenance issue for the human;

— allowing the user to sort or to relabel and re-sort names of sub-layers;

— allow the user to select layers to actually be physically, not sleight-of-hand cosmetically grouped, moved outside of their current nested layer;

— keep realtime track of the last 2,000 actual edits, and be ready to INSTANTLY redo the work for the user after a crash;

— keep track of the recent 10,000 edits that might have contributed to file corruption;

— eradicate from or totally separate from the Undo stack ANY ACTIONS that are not geometry; really, administrative things should be in a separate undo stack so that admin-type acts that might spawn dozens of sub steps could swarm the undo stack to the point of busting it really fast, making Undo and Redo untrustworthy — I had to bail out of/quit a file because the Undo stack got goofy);

I feel compelled to share two more suggestions not in my excerpt I posted above:

— immediately recognize that high-tedium geometry creation, such as creating ship hull stiffening anolg a compound curvature along >100 meters can be done by replicating the user's steps (of the user has a plan, and can explain such as "every x meters, between these points...) to do in 3 minutes what might take (me) 3 hours;

— auto-fair, by analyzing user apparent intent, 3D/compound curvature interpolated and even control point splines so that a spline that is the top deck, various waterlines, profile, and body plan (front/bow view, as well as its rear/stern view) can be constrained so the user need not play with excessive amounts of constraints in a valiant effort to make a faired hull;

...

As for the Adam video, I don't know if that company is going along a path of trying to patent anything as if no other CAD app makers thought of what the video presents, but, it feels like

— Tim's Copilot;

— various features of FreeCAD; featues in Rhino/Grasshopper/Orca/Nemo/Swordfish; and

— other's apps which I've watched that have been or seem to be offering comparable features.

Perhaps a "moat" Adam may have is a clean sheet CAD system? Could it be one devoid of 20+ years of spaghetti minefield code that even an AI regression analysis would overheat past 10 million degrees Kelvin?