People will be able to create entities on the blockchain (groups, users, companies), these are really simple objects and only have a publickey and a name basically. They allow someone to own an alias which represents something in the real world, like my identity on here. By the way this is exactly the way the evolution documents describe the process of implementing these systems, these are the "network primitives". Next, using these identities you'll be able to create a proposal or contract, which is then controllable in the future. You can add things to it, like reports.
Reports have a date and a url. It's just a really simple abstraction of exactly what we're going to need over the next 5-10 years and nothing more. They'll live elsewhere, perhaps all over the internet.
Groups of people working together are managed with decentralized autonomous organizations. We could have DAOs for DashCORE, DashResearch (vending machines, etc?), DashFoundationLLC, etc. So when the foundation wants to get funding for something, we can group all of the requests together and see how much funding they've gotten total and other metrics. Graphing these metrics out over long periods of time is going to allow people to study our currency and figure out how it's growing, what is working and what is not.
Here's a comment from my code of the layout of the network:
/*
CATEGORY MAPPING
* means the category has an associated class
DASH NETWORK (ROOT)
-> NETWORK VARIABLE
-> switch, setting
-> CATEGORIES
-> LEVEL
-> I, II, III, IV, V, VI, VII, VIII, IX, X, XI
-> VALUEOVERRIDE
-> NETWORK, OWNER
-> ACTOR
-> GROUP*
-> CORE, NONCORE
-> USER*
-> CORE, NONCORE
-> COMPANY* / ORGANIZATION
-> DAO
-> COMMITTEE
-> BUSINESS, RESEARCH, DEVELOPMENT, AMBASSADOR
-> FORPROFIT
-> LLC, INC
-> NOTFORPROFIT
-> 501c3, 501c6
-> PROJECT*
-> TYPES
-> SOFTWARE
-> CORE, NONCORE
-> HARDWARE
-> PR
-> PROJECT REPORT*
-> UPDATE
-> PROJECT MILESTONE*
-> START, ONGOING, COMPLETE, FAILURE
-> PROPOSAL*
-> FUNDING, GOVERNANCE, AMEND, GENERIC
-> CONTRACT*
-> TYPE
-> INTERNAL, EXTERNAL
-> STATUS
-> OK
-> GROUPS
-> GROUP1
-> USER1 (only users are allowed here in this scope)
-> USER2
-> GROUP2 (EVO)
-> VALUEOVERRIDE (STORE=DASHDRIVE)
-> USER1
-> COMPANIES
-> COMPANY1
-> DAO1
*/
The category mapping and its associated classes look pretty neat.
Something tells me Dash Github Visualization 2016 will be interesting.
* due to Dash forking from Bitcoin you will see not only development on Dash but also on Bitcoin