3 ms·
This is a vibeslop project with a vibeslop write-up. Trees? Trees aren't expressive enough to capture all dependency structures. You either need directed acycl
by tovej 8mo ago
This is a vibeslop project with a vibeslop write-up.
Trees? Trees aren't expressive enough to capture all dependency structures. You either need directed acyclical graphs or general directed graphs (for iterative problems).
Based on the terminology you use, it seems you've conflated the graphs used in task scheduling with trees used in OS process management. The only reason process trees are trees are for OS-specific reasons (need for a single initializing root process, need to propagate process properties safely) . But here you're just solving a generic problem, trees are the wrong data structure.
- You have no metrics for what this can do
- No reason given for why you use trees (the text just jumps from graph to trees at one point)
- None of the concepts are explained, but it's clearly just the UNIX process model applied to task management (and you call this 60 year old idea "genuinely new"!)
- kimjune01 8mo agono solution is final, but if you have a better working solution, please share!
- tovej 8mo agoDAG-scheduling is a solved issue. If you really need to impement an autonomous LLM agent workflow engine, use a DAG. Just have the LLM declare the edges. My suggestion is to not do any of that but use a traditional workflow engine / project management tools if you need to boost productivity in processes /projects. You're code quality will improve and your programming skills won't deteriorate. At no cost in productivity.