First pass at a great workflow RFC to rule them all.

I don't get how the multiple application repo structure solves for large organizational behavior. The independent software project approach works for large organizations, because it's something they can grok based on exiting software development practices. The Foo team is responsible for how Foo works, even though I depend on Foo. If I have 100 applications in my infrastructure that have interdependencies, how can one person/team truly support them all? If all I care about is that Foo works and I get updates, then doesn't that force the "independent software project" model for cookbooks? Or is this about describing the scope of cookbooks and not trying to eat the entire world with one large cookbook?