@User , It was mostly so that it would be most broadly useful. I cannot guarantee how others structure your project. The roots of find-kedro comes from my experience on

0.14.x

project that had a very deeply nested set of pipelines. You can easily change up the keys in your register pipelines module. You can make up rules that make most sense for your team. The core of what

find-kedro

does to create pipelines based on name (quite similar to how pytests picks up tests) will still be there, you will just make a slight tweak to make it cleaner for your project.