duplicate code paths hero_flows and hero_proc #54

New issue

Open

opened 2026-04-28 02:02:07 +00:00 by despiegk · 0 comments

despiegk commented

2026-04-28 02:02:07 +00:00

Owner

there is now hero_flows and hero_proc

its not ideal because DAG was imlemented in hero_proc to be used everywhere

also I don't think its not good to use OSIS for this feature, because this needs to run before OSIS is even there
and OSIS is probably not going to be fast enough

DAG needs to be part of a core service with NO dependencies

there are very cool features in hero_flows, we should then maybe merge them back to hero_proc

note

we need to make distinction between stories (which is high level and can have multiple parts) and something an agent executes on

![image](/attachments/1081dc11-084d-4619-abf9-149b3d020109) there is now hero_flows and hero_proc its not ideal because DAG was imlemented in hero_proc to be used everywhere also I don't think its not good to use OSIS for this feature, because this needs to run before OSIS is even there and OSIS is probably not going to be fast enough DAG needs to be part of a core service with NO dependencies there are very cool features in hero_flows, we should then maybe merge them back to hero_proc ## note - we need to make distinction between stories (which is high level and can have multiple parts) and something an agent executes on

image.png

141 KiB