Summary:

Intro blog post: https://blog.aragon.one/introducing-the-aragon-network-20b998e2caba

Whitepaper:    Aragon Whitepaper.pdf

Web2 page: https://aragon.one

What it is: A DAO hosting platform, with a nice web3 UI, a governance network, an app store, and some other utilities to build DAOs with.  That is, you sign up on aragon.one to build and configure your own DAO.

Coinfund Q&A Notes 5/11/17:

See: https://www.youtube.com/watch?v=U35jr3UOBXc

The technical discussion centered around the architecture of a single Aragon organization, primarily using this slide, which shows you how each organization (DAO) is constructed:

The diagram shows four "levels".  Your DAO is on the left - level zero.  It is about ten lines of code that passes all transactions to the kernel via delegatecall.  You can change the kernel address.

Kernel (level 1) has three entry points, depending on the type of transaction you make.  It was made clear that Eth is insufficient for most organizations as a medium of exchange and store of value, and for governance and many other functions, so wrapping eth in ERC20 and Minime, and other measures is often necessary.  ERC20 in particular was called out as too simple for governance, as to prevent double voting you (I am reading into it) need to track balances and expenditures and serialize each token in some way.  It wasn't super clear what all of the kernels functions are.  It was also mentioned that MKR, OASIS, et al wrap ether so that it's more easily transferrable and operable (not sure why, but one can guess).

The Organs (level 2) are swappable libraries that can be installed or uninstalled from your DAO.  

Quick note on a later discussion of how that is done: You deploy your DAO once, and set bylaws and other governance rules.  Some quorum or debate period might be required for changes, or you could say that no changes can ever be made.  The rules get followed and the DAO gets it's modules swapped out as needed, requested, and authorized by the bylaws and other rules.  I think.

Apps can also be added to your DAO and used - they can be installed from an app store.  That's level 3 which we'll cover later.

The Dispatcher at level 2 brokers calls to apps and checks authorization to make them, otherwise it rolls back calls.

The Meta Organ at level 2 changes values for other organs, or for lower levels of the DAO, including the kernel address.  Again, this is something that voting and bylaws restrict.  I suppose the Meta organ is used every time an organ is swapped out as well.

The Token Vault Organ at level 2  stores the DAOs assets.

The Governance Organ stores governance tokens somewhere, and tracks who the shareholders are, and what voting powers they have.

The Apps Organ at level 2 is a directory of sorts of the applications installed, and probably has some power over installing and uninstalling apps.  Not 100% on that.

Level 3 be apps.  DAO voters vote to install these, and they appear to be the part of the DAO that is expected to be swapped out and updated frequently.

They are undergoing a huge refactor right now to bring this architecture into existence.

Democracy.earth is planning to use this, as well as a linux distro, and a bunch of open source projects and some 1000 or so other organizations.  Serious momentum, here.