True, but I would argue that the purpose of a design system is to be a user manual of sorts. We want our software to appear and behave as if it was created by one team, even though in reality it was created by separate teams working independantly within a large organization. Consistency has a value, a value that is probably under appreciated.
I agree, writing good content for the system is probably just as difficult, if not more so, than figuring out how to organize it. We don’t have this part figured out yet. That might be another thing to share once we do.
Sharing and finding design work is getting to be a challenge as our team grows and other business units…
I don’t completely understand your question, but if you are referring to why we inverted the hierarchy to place Applications in the beginning, it was because we wanted to place an emphasis on how to properly use specific UI components by showing real examples rather than having people jump into assembling pieces however they want.