kevinsync
10 hours ago
Looks very intriguing!
My main question after looking it over though is: given an existing codebase, how could I go about building a decision graph to essentially get "caught up" to current (I guess based on commit history?) to then move forward actively using Deciduous from here on out?
rhgraysonii
10 hours ago
The value is in the in the moment weights and decision making so it builds it in a living fashion as it sits now.
It wouldn’t be hard to make a skill that went through and did this at a basic level if you have a good healthy and well organized git history (most people don’t)
There is already tooling to link commits to nodes and re author chains so you could tell it to explore and start making this.
I might do an experiment trying this with an existing project in the OSS ecosystem tonight, sounds fun