---
# System prepended metadata

title: Constitution + Baal Entanglements
tags: [DAOhaus, Meeting Notes]

---

---
###### tags: `DAOhaus` `Meeting Notes`
---
# Constitution + Baal Entanglements
We have identified a few key elements that seem to have an unspoken relation.
### Baal development relates strongly to the articulation of a DH constitution.
1. In Jord's draft, a distinction is made between mutable and immutable principles.
2. DH seems dedicated to coding in a sensibility into the product that facillitates the community-first ethos, to provide composable communities.
3. Baal builds upon the minimally viable DAO to allow for this composability, determined by the community that summons. What are the immutable aspects of the Baal code?

### The tools we use to compose/archive the doc are integral to the content
1. Web2 tools are broken, but now is not the time to reinvent the wheel. ie: So much information gets lost in Google Docs, Discord channels/threads, Github repos, not to mention their centralized control.
2. The writing of a constitution by a decentralized, dispersed, asychronous community is a complex dynamic that is not captured with these commenting/response features. Essential information is lost, diminishing the democratic potency.
3. As in art manifestos, the text should reflect the style of the writers in both form and structure. DH is an ideology and a product. The constitution should reflect the building and the thinking. There's a fundamental relation between the aesthetics and the architecture (especially important since DH is inspired by Bauhaus).
4. We have identified a pain point that we could build towards! How do we compose a composable, living document using the Web3-DAO tools and knowledge at our disposal? How do we dogfood our own ideology and tools to write a constitution that reflects the mutable/immutable parts, that represents the product and community that is *always changing*?
5. We don't want to get sidetracked in trying to invent a new hammer, but can this problem be anticipated in the writing of the document itself? To declare that we are laying a provisional foundation that is open-source and forkable to represent the DAOhaus community to come?
6. This seems like a much more interesting problem for technical and non-technical War Camp contributors to be focusing on. Perhaps a worthy project for EthDenver that brings together the whole work stream?

### The relationship between DH and UH
1. Spencer's article on the CCO is illuminating in it's depiction of a funding model that drives the community and vice versa. The ethics are in the mechanics of the CCO, the HAUS token, the summoning of UH. The code is law, but the law is community-first.
2. Uberhaus is poorly understood by the greater DAO community, but is an essential component of the DAOhaus mythos. As per BillW's recent comment, perhaps DH needs a manifesto (that changes every year?) and UH is more deserving of a formal constitution *written by the federate DAO ecosystem.*
3. Any definition of one should entail the other. What is the method? Answer: the same experimentation, anti-degen ethos, and radical decentralization that goes into the product.

### Core needs of the document
1. Reconcile the community-first ethos in a novel fashion (not regurgitating the MC values, per say).
2. A document architecture that represents the architecture of the product/platform.

### Baal and Constitution reflect each other
1. Current need to communicate the changes and significance of Baal to a technical and non-technical audience, especially those that doesn't necessary have experience with Moloch v1 and v2.
2. *DAOs as smart contracts* is a concept that requires explanation alongside the socio-cultural aspects. The social story runs parallel to the technical understanding. The code composes the community. Baal is an ideological vision instantiated in code.
3. A dev walkthrough of the Baal smart contracts explained to Rangers that don't know how to code solidity is a good way to understand the *why and the how it actually works,* which may inform the *why and how of writing the constitution of the product.*