---
# System prepended metadata

title: MetaOS Design Exploration
tags: [v3]

---

---
tags: v3
---

# MetaOS Design Exploration

Ven Divergent Path:
https://www.figma.com/file/9lCwprCNaoAmUDmiMQpFEA/DAOhaus-v3?node-id=3438%3A17631

Adrienne Divergent Path (more metanav focused): 
https://www.figma.com/file/1RCw6028L7AVb7usE0N3vs/MetaHaus?node-id=151%3A455

### Value Adds - Needs Research Validation
#### MetaOS

- Ability to connect to different DAOhaus apps easily
- Ability to connect to different Moloch DAOs
- Ability to add other types of DAOs and onchain governance tools
- Ability to bring in offchain tools
- Governing the content / security and worries on attack 

#### MetaHAUS
- Ability to connect to different DAOhaus apps easily
- Experience of not bouncing between different contexts when navigating among DAOhaus apps

### Use Cases for MetaOS
- Provide a landing page for a DAO and links to relevant content/tools for members 
- Provide a shared landing page for multiple related DAOs 
- Provide information on how multiple DAOs are interconnected
- Additional boosts can be in the market for the MetaOS functionality (ex. a calendar plugin)
- (AT) Creating a portion or entire page as member access only? 

### Problems to Think On
- How would 4 DAOs make content updates that rely on proposals? 
- What benefits does it provide over a wiki or small webpage? Does that value outway the technical complexity to develop + the infrastructure work? 
- Can this be a tool we have another team build or is it integral to the DAOhaus ecosystem? 
- Would a more advanced 'Allies' page provide enough information on interconnected DAO relationships? 

## Next Steps
- Wrap a few questions to validate value add into the current research survey/interview workstream
- Determine what additional research we want to do (via prototype or anything else)
- Continue design and user workflow explorations
- Create a hackmd version of the Warcamp metaOS to solve our own problem and what is missing  
