This repo contains the architectural design of FWE (Flow Works Engine) — the initial docs covering how the program may be built and how it's intended to work.
The main repo is below, but please do take some time reading this and all the docs in the docs folder above:
https://github.com/FWE-R3nSoftOrg/Flow-Works-Engine-FWE
Note: Yes there is now a Repo for the skeleton that Honestly that was made with Claude, I initially plan it to actually make the code(with claude of course) at least rough one and let the community polished it, but well, as I realized, I needed actual people to help this happened. It's just WAYYYY to big for me, But I am gonna do my absolute best to still contribute on it, I want to use it, who wouldn't want free software? and for this caliber? yeah well, I lack skill so hope you understand. -LazyR3nR3n
A few things to note: there is a business model included. Yes. But that's only because if FWE ever gets adopted, having that design in mind early makes things easier, besides because of how large this is, and specially the material data constraints that if you read the whole docs, you will understand WHY, ITS GONNA BE BIG, that again just gaps to fill. Ultimately, You guys are the developers you can suggest what's direction it will go, I started this whole thing for Basically just wanting some software I couldn't afford so, I did say fuck it and just make it, there is Opensource tools out there who can make it happen as it's backbone and it compounded to THIS SOO WELP, Here we are am I right? but AGAIN, need help either way can't do this alone, I'm the visionary, and I'm learning to build it — but I can't do this alone..
I'm a 20 year old with no CS degree, starting BS Entrepreneurship because that's the only accessible option I have given my personal reasons. I've been tinkering about FWE for a while — with Claude. YES, WITH CLAUDE, on a free tier account.
I don't have a vocabulary for coding, well maybe a bit, but mostly just basic stuff, but when it comes to the open source projects that form FWE's backbone, I needed help figuring it out, so I did Use AI specifically Claude, the MCD or Main Context Document are the ones I and will probably gonna use in the future for prompting, but since there will be an actual contributors, I probably just gonna use it for Debugging or bug hunting.
There is also a developing constraints that I, don't have a good machine, just a old laptop that runs windows 10, and I am scared it might suddenly failed on me mid development, literally yesterday before I decided to leave it to the actual developers hand, my laptop keyboard just spammed T for some reason and I need to physically pry-up, the T key on my laptop to stop it. it's fine for now since it stopped because I blew hard(and it stop for some reason now), but who knows what could happen mid development? plus it's literal second hand Fujitsu Lifebook A series, with just an i5 7th generation I think Idk, either way it's old and the screen is literally pink and I have to use our family TV (that I don't have access always Cause I am not the only one who use the TV) to not make my eyes hurts with pink hue with green lines covering the whole thing except a strip at the top that have only 5 percent full color, even less probably.
This project started from me just wanting an accessible CAD and simulation tool — in one program — with a physics-driven data approach to produce somewhat realistic results. In theory at least, yes in theory, it is possible. I do believe it can still happen. And if a specific approach doesn't work — please suggest it.
#Support
If you want to support the vision, the donations are much appreciated: