---
# System prepended metadata

title: UberHaus Development Checklist
tags: [WarGames]

---

---
###### tags: `WarGames`
---

# UberHaus Development Checklist
## High-Level / Uberhaus Specific

- [ ] Outline step-by-step overview of what needs to be accomplished for UberHaus MVP
    - [ ] Onboard initial users
    - [ ] test current structure with wargames
    - [ ] create hypothesis on solutions to main problems
    - [ ] perform research to validate hypothesis
    - [ ] devise implementation strategy
    - [ ] implement & test
    - [ ] reevaluate
- [ ] Define/document the UX of the 2 body system for UH
    - [ ] Document for DH/UH docs
    - [ ] Outline for testing rubric
    - [ ] Lorecraft for playbook
- [ ] Diagram the entire UH onboarding flow
    - [ ] Insert into DH/UH docs
    - [ ] Insert into testing rubric
    - [ ] QA playbook lore to make sure it is accurate

---

## UXR&T

- [ ] Define the general high-level WarGames testing methodology, to serve as a template
- [ ] Define the test procedure for WarGames Act I (UH onboarding flow)
    - [ ] Problem Statement
    - [ ] Hypothesis
    - [ ] Methodology
    - [ ] Anticipated Results
    - [ ] Data
    - [ ] Analysis
    - [ ] Recommendations
- [ ] Define the test procedure for WarGames Act II (UH proposal flow)
    - [ ] Problem Statement
    - [ ] Hypothesis
    - [ ] Methodology
    - [ ] Anticipated Results
    - [ ] Data
    - [ ] Analysis
    - [ ] Recommendations
- [ ] Define the test procedure for WarGames Act III (HAUS token utility and governance weight)
    - [ ] Problem Statement
    - [ ] Hypothesis
    - [ ] Methodology
    - [ ] Anticipated Results
    - [ ] Data
    - [ ] Analysis
    - [ ] Recommendations

---

## WarGames General Tasks

- [ ] Instructions for both kinds of hackers (for Act II) of the game

---

## WarGames Lorecrafting Tasks

- [ ] Encoded instructions for hackers into "secret encrypted messages" (Act II)

---

Meeting Notes to integrate:

- Create a policy for players to vote on:
    - Rule, request for funds, story, etc.
- Guidelines/directions for the game master role
- Onboarding bot to automate player flows
    - Potentially a use case for RG Tavern Keeper
- Divide player quests by priority:
    1. Testing flows
    2. Game-only flows
- Lore, dice rolling, etc., is irrelevant to UH
- After the airdrop with token, the UH flow begins

Friday Script:
- Describe the onboarding flow
- Join one of the existing DAOs
- Game Master provides set/setting to present the policy/conflict to the players
    - Introduce themselves to each other
    - Introduce relations to other players
    - Introduce a reason to start collaborating, tensions within the factions, or their own factions initiative to provide back story
- After the players Yeet they go into the game Discord server


Policy: If the DAO is being attacked, can it gain emergency executive privleges in times of war without requiring Snapshot vote approval? What does it mean for the DAO to be under attack and when is it ok for the DAO to act on this?

Act II: Malicious proposals: How is the Operator chosen? Do they understand the weight of their responsibility? How do we design in shared accountability?

Policy: Does every proposal need to be audited by an operator? Operator requires some decent experience to spot the call functions and trace the lineage of the contract. Malicious code could be arbitrary markdown text.

Whoever is able to successfully pass their markdown text update.

Discord notification attack vector!

