Add a publication process for DAO, blockchain, and Web3 constitutions #5
Description
Publication process: a standardized way of displaying and accessing (and maybe writing) a constitution/agreement for a DAO. E.g. how you can always expect LICENSE.md to appear in the top folder of a Github repo.
On the writing side: there might always be a particular sectioning order, a “bill of rights”, or a summary of the code deferrals at the top. Sort of like how there are conventions and frameworks in writing licenses (and, later on, clean explainer websites like https://choosealicense.com/)
On the data model side: basically some sort of content tagging model, plus a controlled ontology for labels that corresponds to the Constitute ontology.
Pick two examples to start out with. Metagame and Tezos?
Ref. notes on publication process for Aragon Agreements (TBC)
From Jack Laing:
- Highlighting the degree to which DAO-modified legal frameworks (LLCs, Foundations, etc) differ from their traditional counterparts
- Conventions/frameworks for those differences, e.g. sections for code deference, what should code deference look like depending on your goals and the legal framework you’re starting with