Efficiency requires major Refactor

So, I have made `Robot` exclusive to each web service account like Apple, Google, Jira, etc. Until now all I needed was like single resource to be fetched and I figured if I would need more than one resource I would seperate it into other `Robot` and it is working for now **but...** it is becoming extremely excruciating to add more `Robots`.\n\nSo current data pipeline is *Web Service to RobotStation(JSON) to Logic to Model*. Rinse and repeat works but I have to code adaptors for related Robots and it just looks messy, I am not happy with it.\n\nSolution one, merge `Execution` and `Processing` stations so that `Robots` are practically flexible to code, but that will hugely affect reusablity and I am looking at other refactor very near future. So, **nope**.\nSolution two, add `Pipeline` to `Robot`. This is very convincing as I would just need to make new `Execution/Processing` station for new implementation. Another advantage is to possibly add `Junction` later to take care of conditional aversions. Problem with this solution is that it would require migration and come to think of it, at this point I guess updating code is equally scary 😅\n\n**Conclusion**, taking up on Solution two after I am done with this `Product Robot` thing unless I find better solution. \n\n### Stay t👀ned!