This is interesting, thanks @skilesare. Does this differ a lot to an SNS registering a generic nervous system function that executes the manage_neuron function? This already allows an SNS to manage the permissions that different principals have on a specific neuron (and therefore the actions that they can perform). @rem.codes has done some great work making this a smooth process with Toolkit. I’d be interested to learn more about your research into DAOs. I think the IC needs this sort of stuff.
That’s a nice way of putting it. Indeed, the committee need to be impartial and simply respect the results of an NNS election 
I’d like to see this too. Ideally the founding committee’s role will be temporary (we’ll see what the NNS wants), and I agree that openness and transparency is top priority. I think all that’s needed for this to be fully on-chain is a proposal type that can execute manage_neuron on a neuron that’s owned by the governance canister (D-QUORUM). This is already possible for SNSs (generic functions can execute manage_neuron on the governance canister for other SNSs, and DFINITY has proposed introducing a native nervous system function that should soon allow an SNS proposal to execute manage_neuron on its own governance canister).
This is very well put! Thanks @krzysztofzelazko