I checked out cadwolf and as an engineer myself I find it very interesting. I am curious to understand a few points: - Why do you center everything around documents? Is it more because people are used to it, or do you believe that they are best fit for design-tasks? - I saw that to update multiple documents after a requirement changes, you need to open them one by one, in the order of their dependencies. Have you tested that this is still a viable approach, once you have thousands of dependencies and multiple users in a complex design?

I really like the equations and how you only allow to make formally correct equations (including units). Anxious to see how this develops.

(full disclosure: I am co-founder of a Software which tries to achieve the same aims using different concepts: www.valispace.com)

What I call "Document" are not files in the sense of a word file. They look like text files because that is what I thought engineers would be comfortable dealing with. However, they function as programs. Documents can be used as programs within other documents as well. Documents fill both the need to solve the calculations and to document them in one place. It eliminates the need to update documentation, have multiple platforms, etc.

There are places for users to upload and store data as well - datasets.

As of now, the code solves equations in javascript within the browser. This is why documents have to be opened when a requirement changes - because I have no server side of the code to solve them without the browser. It isn't a long term solution, merely a step in the building on the platform. My next step is to add a server side code that is capable of solver more complex and larger equations on the server. When that is done, changes to requirements will update documents without the need to open them manually. I plan on using python and there are several large libraries available.

This will allow me to link documents to CAD. When the math changes, the CAD will change as well. Once that is done, I will add a finite element meshing and solution system to create an engineering platform that essentially does everything.

I like your site. It's nice to see other people addressing these problems. I am also an aerospace guy. I worked on the shuttle for a while and then designed some components for the Orion. Shoot me an email if you want to talk more.