I thought of a use case for the Cooperativeā¦
As Aragon Organizations (AO) begin fundraising for their entities, they as a team may not want to personally work on developing Aragon apps, but they may likely require some new apps to meet their organizationās needs.
The Cooperative can be an organization that brings together these future AOs to determine what they need built. The AOās commit some amount of funds they raise toward the Cooperativeās vault to be used in relation to design / development of these applications. This will ensure more timely delivery of the apps as well - Flock teams may not be able to deviate from their roadmaps much, but other Nest teams who also have an interest/need in these applications proposed by the community may be more likely to pick up the work.
Hence one aspect of the Cooperative can be a consulting organization of sorts, but it also has a specific aim to reduce the duplicity of work across new teams that want to develop Aragon apps or need specific Aragon apps. The goal isnāt just to build apps for the purpose of building apps, but to go toward common solutions that meet the primary use cases of most organizations. The Cooperative would manage surveys to gain insights on what the community needs are, and then see which team that is part of the Cooperative is best suited to do the work.
This doesnāt mean that Flock people shouldnāt be a part of the Cooperative, as I think that is still important as well, even if the funding model for the Cooperative ends up coming from AOs. What I propose above is another activity/use case for the Cooperative in general, not the entire purpose
But if successful, this may be a ābusiness modelā that can help fund the Aragon ecosystem outside the ICO treasury as more and more organizations adopt Aragon.