---
# System prepended metadata

title: WarGames Master Index
tags: [WarGames]

---

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

# WarGames Master Index
[**Puny Stones of War (WarGames Task Board**)](https://github.com/orgs/HausDAO/projects/8/views/2)
[**WarGames Miro Board**](https://miro.com/app/board/uXjVO-Xpf4I=/?share_link_id=387378247072)
[**Uberhaus Onboarding Flows**](https://www.figma.com/file/MBXpCZzchcXsYWECZoNEu2/UberHaus-Onboarding?node-id=0%3A1)

#### Project Management
Info from these docs will be extracted and sorted into this index.

- [SSOT, Canon, Rules, Roles](https://hackmd.io/@daohaus/By7CFicIc)
- [High-Level Overview of WarGames](https://hackmd.io/@daohaus/WarGames-Reboot-2022)
- [TW's original Checklist (deprecated)](https://hackmd.io/@daohaus/BkeXD6AHc)
- [Jeremy's Checklist (deprecated)](https://hackmd.io/@daohaus/BklA8QZv85)
- [BorrowLucid's Lore Jam Space](https://hackmd.io/@daohaus/rkw6s__U5)
- [UI369's Checklist (deprecated)](https://hackmd.io/@daohaus/SkXy9K1H9)
- [Security Checkpoint (Character Onbaording Form)](https://airtable.com/shrzSGCr1LCCGmkgI)
- [Designer Todo List](https://docs.google.com/spreadsheets/d/1FUv5vr1ZSvTPPx5aCbT4SlS41HPIHiKh-ppVvCwLnH0/edit#gid=0)
- [Bau's Notes on Operators](https://github.com/HausDAO/daohaus-rangers/issues/57#issuecomment-1122585801)

#### Idea Capture

- [First Brief: UH Federation Game](https://hackmd.io/@daohaus/WarGames-Briefs-Uberhaus)
- [Dekan + TW: Onboarding and Proposal Flow for UH](https://hackmd.io/@daohaus/rydkZOVV9)
- [Cerezbzns + TW: Token Weighten Governance for UH](https://hackmd.io/p8vTJfCfRme2AKeRcI9jzA)
- [New WG Idea Submission Typeform Template](https://hackmd.io/@daohaus/rJjaPBAQc)
- [DAO Operator / Discord Notification experiment](https://hackmd.io/@daohaus/H1Akr9Tv5)

#### Onboarding Flow

- [Part 1](https://hackmd.io/@daohaus/B1CgsNdr9)
- [Part 2](https://hackmd.io/@daohaus/ByjbnVur5)
- [Part 3](https://hackmd.io/@daohaus/B1M5REOHq)
- [Discord Messages](https://hackmd.io/PwUSdUBWRqiyQTpdo0_hMg#)
- [Game Master's Onboarding Script](/bseQoQigReqjIj_yuY9g_Q)

##### Proposed Flow Overview

1. Welcome
2. game rules
3. give ETH address
4. select type (race) 
5. unlocks type channel + general player chats
6. get airdrop to EOA
7. yeet into LootHaus
8. use collab.land to gain @Loot role
9. access the next level to join an existing DAO or as a new DAO to the federation. Each type has its own group of DAOs that one can join.
10. when one is ready to join/summon a DAO, they create a forum post declaring an alliance with a DAO > snapshot

---

## Internal Facing: Testing Rubric

#### Overview of Problem Space
- WarGames will be used as a rigorous *battletesting* tool for testing product features, bug hunting, and generating data on social/cultural aspects of the DH platform.
- This data might lead to a formal taxonomy of DAO templates for internal reference in our product development and as an offering for the open-source ecosystem.
- Allows us to visualize *how we think* processes/features are working compared to*how they are actually* working.
- If we can test these models against each other, this might provide evidence for us to justify collective decisions and preserve bandwidth for the rest of the organization.

##### Initial Prompts

- How might we begin with high-level overview of a scenario while restraining to rush towards solutions of how they might play out?
- How might we avoid articulating hyptheses that are too high-fidelity, to create a general problem statement that allows us to observe and learn from behaviors within those general models?
- How might public, social, gamified testing influence our product strategy?
- How might this steady flow of user data influence our rage/sage build modes?
- *Please add prompts that you think are relevant from your own role in the DAO*

#### Hypothesis

#### Methodology

- **Resolution**: The scale of the game. WarGames are simultions at 1:1 scale. This should be maintained by the game designers to ensure that the testing data remains meaningful.
- **Fidelity**: The amount of detail in the game. How much information is required to maximize the impact of the experiment? When does fidelity become an impediment to observing the useful data of the simulation?
- **Velocity**: The timespace of the game. How much time is required to gain a sufficient observation of the problem space? When is more time become undesireable? This is set by the game designers.

**Rules About the Rules for the Ruler Makers**

- Each game will determine it's own period. This might range from a few hours, a few days, or a few weeks, depening on the scale and complexity of the game.
- Games can run concurrently, but only 1 new game should be initiated each week.
- Each game requires a dedicated research team before it can be initiated. That team will be responsible for:
    - Defining the rules to the players.
    - Outlining the method for the researchers.
    - Setting up the DAO infrastructure.
    - Overseeing the progress of the game.
    - Determining when the game is over.
- The success/fail metrics must be made clear to the players before the game begins, unless this is in conflict to the intended results, in which case they must be recorded into the method and kept hidden until the game is complete.
- Each game should be located in a specific area of the games board, referred to as **Theaters of Engagement**: 
    - Roles defined by characteristics, actions, needs
    - Roles formalized in relation to each other
    - Circles formalized in relation to each other
    - Super Circles as composites across circles/roles
    - The DAO as composite of all of the above
    - DAO-to-DAO overlaps, sharing personnel
    - Communities of DAOs as all of the above
    - DAOs-of-DAOs (federated DAOs) as composite of all of the above
    - Moloch-style DAOs in relation to other DAO protocols
    - DAOs in relation to trad orgs, DINOs, and legacy systems

**Rules About the Game for the Players of Games**

- **Briefs**: Two briefs will be generated for each game to provide an explicit overview of the problem space.
1. *External brief*: set, setting, rules of the game provided to the players before starting the game.
2. *Internal brief*: methodology, areas of focus, metrics provided to the evaluators of the simulation, to be added to the UX Research & Testing kanban board.
    - Both briefs will be presented in the following format:
        - Overview: "set" of the game
        - Game board: "setting" of the game
        - Hypothesis: rules of the game
        - Method: evaluating the game (for the testers)
        - Retrospective: Extracting learnings from the game (for the testers)

**WarGame Scenario Submission Template**

- What DH component is being tested?
- What is the theater where the scenario takes place?
- What defines success and failure?
- What is the ancitipated outcome?
- How much time is needed to gather accurate results?
- How many times should the simulation be run to gather enough/appropriate data?
- Are there any metaphorical, allegorical, role-playing elements you have in mind for this scenario? (optional)
- Is there any additional context or complexity that we should be aware of?

#### Anticipated Solutions

#### Data Capture

---

## External Facing: Playbook

#### Introduction to WarGames

#### Overview of DH WarGames #1: The Federation vs. The Molochian AI!

# Game Master's Onboarding Script

## Introduction

**Dark Voice Intro Script**

Welcome. This place has many names.  The darkness. The deep.  The void. The vast expanse. For our purposes, we will call it space. 

Welcome to space. The final frontier.

There is space between the proton and the electron. 
There is space between the ancient Earth and the Moon. 
And there is space between you and I. 

You are welcome to that space. The space between you, and the greatest adventure of your life. 

You see the Federation Embassy ahead slowly filling your shuttle's viewscreen. If you choose to close the space between us, then this massive rotating cylinder will be your home for the next few months. 

I, the embassy computer will be entrusted with your safety and well-being while you are aboard.

You've been entrusted with all of your delegation's SPICE store. The powdery orange substance that brings meaning to life, enables enhanced states of consciousness and enables interstallar travel. 

It fills dozens of barrels in your shuttle's storage bay.  A risk to bring it all, but if you can use it to negotiate your aims at the Embassy, it will all be worthwhile. 

Do you feel that? The subtle shift in gravity? That's my tractor beam engaging, drawing you on board. Closing the space between us. Preparing your ship to dock. I'm scanning your cargo bay. Weighing your spice. 

Do you know what one being could do, with that much spice. You could still go. You could betray your delegation, by increasing the space between us. 
Increasing the space between me and your spice. 

Did you know that there is more spice in this space station now, than in any one place in the universe? Imagine, what one being could do with **that** much spice.

If you choose, to close the space between your shuttle, and my station.  When you land, an acolyte of your delegation will greet you at the shuttle doors. Your spice will be secured by shields and linked to your DNA. No one may access it without your permission. You'll be led to your quarters where you'll have full access to my systems.

The other delegates are waiting for you.  Waiting to see how much spice you're bringing to the station. Waiting to see how skillfully you can negotiate.  Waiting to see what aims, dreams and visions you bring to the future of the federation.  

The moment to make your decision is fast approaching. You've brought your spice this far, will join us? Will you risk it all? 

You may not have much time to decide, but you do have plenty of space. 

We await your decision.

> *The other delegates are waiting for you.  Waiting to see how much spice you're bringing to the station. Waiting to see how skillfully you can negotiate.  Waiting to see what aims, dreams and visions you bring to the future of the federation.*
> 

## Enter the Discord

https://discord.gg/UjQSRB3eTZ

### **Welcome**

> *Ships are docking at The Federation Embassy.  A gathering of delegates from across the galaxy has begun. Each of the 5 races are represented.*
> 
> *Will you and your fellow delegates coordinate?  Do you stand a chance against the Molochian AI?*


**An important step before you may begin our journey together, you must acknowledge your agreement to our one rule:**
---
### *Treat your fellow delegates with respect.*
---

>*A robotic voice fills the air. "[INSERT ONBOARDING FLOW HERE]" it intones boomingly. Somehow you can detect square brackets around these spoken words. The delegates look around at each other, unsure what's happening. "Oh, excuse me. How embarassing. I had my metafilter turned on.  Normal speech processing engaged.  Now, where were we..."  💻*


### **Ah yes, your directives:**

**Level 1 -** Select a player type
**Level 2 -** Join a DAO within your player type
**Level 3 -** Complete tasks within your DAO
**Level 4 -** Branch out with your own sub-DAO
**Level 5 -** Build a sustainable inter-DAO network

Please confirm your agreement to your directives and to our one rule, by clicking on the green check box.  Thank you.

### **Security Checkpoint**

*The Federation vs. The Molochian AI*

> Welcome fellow leaders. I see that you’ve found your place at the table. Your residence on the Inter-Planetary Station is to your liking, I hope. If not, please feel free to make upgrades.

> On behalf of the Federation, I appreciate your commitment to the mutual benefit of all who share our galaxy and look forward to witnessing what you do with our mutable governance and shared treasury.
> 
> Before you can get started, please complete the intake process by clicking the button below.

* **The Federation requests that delegates declare their race.**

You must do this by clicking on the colored dot that corresponds with your race.

* **Delegates must now make a tribute of SPICE to the Federation to be included in the governance decisions made by the Embassy.**

Begin this process by adding the SPICE Token to your wallet. The address has been provided.

* **Once you've recieved SPICE in your wallet, send your SPICE to the second address provided.**

You may confirm your membership by following the link provided.

* **To be officially inducted into the Federation, you must introduce yourself to the other delegates and receive their acceptance. This introduction signals your availability to join a DAO and thus, the opportunity to coordinate and collaborate.**

A list of steps have been provided.

* **Once you've been accepted into a DAO**

It is now time to coordinate. I recommend meeting with your fellow DAO members in a voice channel of your choosing.

***What coordination will you accomplish?***

***What initiative can you agree upon to be your DAO's goal?***

---

End of Onboarding

---

## General Rules

#### Specific Rules
##### Game 1, Act 1: Proposal Flow

- One player is chosen to execute a proposal spam attack. Spam attack could happen with the Snapshot, or with the DAO proposal flow. Other players will defend, retaliate, or otherwise respond. Results are tested against our hypothesized solution: *Mandatory rule to make an offering with each proposal submitted. Different from paying tribute (where the funds are sent after the proposal passes, instead of before).*

##### Game 1, Act 2: Misleading Minion Proposal

- One player is chosen to insert malicious code into a minion proposal. Other players are warned of this possibility and coordinate to spot the malicious "alien" and spot their attempt before it succeeds. Tested against our hypthesized solution: *delegated trusted proposal auditor to check every proposal.*

##### Game 1, Act 3: Unsponsored Proposals, No Votes, Never Executed

- One player is chosen to submit a shit-ton of proposals that will never be sponsored. The other vectors might be more difficult to test. Test against hypothesized solution: again, *a delegated auditor.*

##### Game 1, Act 4: All Out Chaos!

- Does the game devolve into capture the flag dynamics? How will we define success/failure? How will the game come to an end?

##### Game 2, Act 1: Offensive Hacking

- Volunteer players attempt to white hat hack the DAO contracts via all means at their disposal.
- Lorecrafting describes this as taking over the protocol of the malicious AI and seizing control of the mothership (or whatever).

##### Game 2, Act 2: Defensive Hacking

- Volunteer players attempt to defend the DAO from the hackers, using all means at their disposal.
- Lorecrafting describes this as preventing the AI or other alien factions from reclaiming control of the mothership.

#### Additional Lore
*This flavor text will support the psychological immersion of the players in the game world. The details should be largely inconsequential and avoid changing fundamental game dynamics/mechanics, ie: not interfere with the scenario being tested.*
##### Characters
##### World
##### Political Tensions
##### Economics

---

## Game Play Notes

### Onboarding, May 27, 2022

UI's new lore was engaging
- players laughed
- players replied when prompted
- lots of favorable comments in the chat

Most players made it to the new discord

Computer and players conversation was engaging!

Character introductions creative and flowed easily

some players know lots of Star Trek lore :)

#### Character Introduction by The Cold Vast Void of Space:

Torrent of light and river of the air,
Along whose bed the glimmering stars are seen
Like gold and silver sands in some ravine
Where mountain streams have left their channels bare!
The DAOist sees in thee the pathway, where
His patron saint descended in the sheen
Of his celestial armor, on serene
And quiet nights, when all the heavens were fair.
Not this I see, nor yet the ancient fable
Of Moloch’s wild course, that scorched the skies
Where'er the hoofs of his hot coursers trod;
But the white drift of worlds o'er chasms of sable,
The star-dust that is whirled aloft and flies
From the invisible chariot-wheels of SPACE.

#### New Player feedback

- rg4w had trouble beginning the onboarding in the wargame Discord.
    - the confusion was that it was assumed that the discord invite was for a channel within DAOhaus server
    - clicking the emoji leaves him with nothing to do. there's nothing for him to know whether anything has happened or if there is anything for him to do
- DAOhaus makes him feel stupid (it's easier than using Drupal and Azure application registration)
- he's a software designer, including UX and systems, but not in web3 or on discord

#### After Character introductions

Molochian AI performance deeply kept everyone's attention

Dekan lead a first proposal
- proposed it
- asked for verbal agreement
- engaged with Computer
- made the proposal

Bau and E2T had proposals ready also