This framework might seem nice and organized but glosses over the extreme complexity and messiness in the "recipes" layer. I work on a very large product that

This framework might seem nice and organized but glosses over the extreme complexity and messiness in the "recipes" layer. I work on a very large product that has 100+ product teams using my core team's design system. The number of "recipes" that are created is enormous. The number of duplicate recipes that are created is enormous (teams creating the same combination of components over and over and over). The number of recipes shared between product teams is enormous. It's a massive, chaotic web of componentry. There's no way to control the chaos. And you wouldn't want to - that would stifle product team independence, creativity, and speed. The only thing you can do is try to have the right system and incentives in place to nudge people in the right direction to improve the overall health of the ecosystem. Oh and you also need to figure out how to measure the health of this ecosystem... I was hoping this post would have a cute framework for that, but it doesn't.