---
# System prepended metadata

title: 'WarGames: SSOT, Canon, Rules, Roles'
tags: [WarGames]

---

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

# WarGames: SSOT, Canon, Rules, Roles

### SSOT
We need to create a single source of truth to increase coherence and collaboration across the project. This IA will be broken down into the following deliverables.
- [ ] Create **SSOT for all content**, including:
    - [x] [**Master Index**](https://hackmd.io/@daohaus/HkwX30cLc) divided into:
        - [x] **Internal**: technical WC-facing **testing and research rubric**.
            - Overview of the problem space
            - Hypothesis for testing
            - Methodology for testing
            - Anticipated solutions/outcomes
            - Quantitative data: numbers, analytics, empirical measurement
            - Qualitative data: user feedback, entrance/exit surveys, interviews, testimonials, chat logs from coms channels
            - **Deliverable**: UX research report to justify improvements to the UH onboarding flow, proposal flow, added security, etc.
        - [x] **External**: lorecrafted player-facing **playbook**. Provides all the information the players need to particpate in the game.
            - Introduction/overview of WarGames in general
            - Intro/overview of this particular game, set and setting
            - General rules (rules about the rules: encourages to break the game)
            - Specific rules for each act/phase of the game (objectives for each phase to serve as boundaries to enforce)
            - Supplemental lore (for LARPing, but not necessary for testing mechanics). This content can be WC generated (as prompts and invitations to iterate), but should mostly be generated by the players themselves (ie: crowdsourced)
                - Character/world backstories
                - Political/philosophical contexts
                - Make it short and sweet
            - **Deliverable**: Lorecrafted and visually stylized player "grimoire" that explains all the aspects of the game.
        - [ ] **Design**: all visual assets and art collected into a **Figma project space**, including:
            - World maps, game maps, theaters of engagement
            - DAO skins, Character PFPs, artifact NFTs
            - General WGs POAPs for participation, for passing various acts/levels, for successfully breaking the game
            - Discord and Discourse visual elements: banners, backgrounds, color themes
            - **Deliverable**: Figma board that serves as a visual design system and asset archive for each game to create aesthetic consistency
- [ ] Cross-correlate with the **DH/UH Handbook updates**
    - Serves as the canonical truth for the UH procedures, policies, and architecture. *This is the ultimate deliverable that these WarGames are seeking to improve.* It is written in straightforward (non-lorecrafted) language.
    - Includes:
        - Clear instructions on how to summon the DAO, setup the minion, and configure technical parameters in prep for joining UH.
        - Clear instructions for proposing changes to the policies via UH soft/hard governance.
        - Clear visualization of the UH two body system.
        - Q&A/FAQ that continues to grow with experience
        - Index/Glossary that continues to grow with experience.
    - **Deliverable**: awesome DAO handbook(s) with clear, up-to-date policy that encourages participation in UH!

![](https://i.imgur.com/0YLzGwS.jpg)


### Lorecrafting Questions

- How might the WG experiment contribute to our own DH lore?
- How might we invite and encourage players to submit their own lore to the game?
- How do we ensure that the lore remains tethered to the testing agenda?
- How will the game lore be ratified into canon? How will changes to this canon be made? Does every game reset it's lore or does it transfer and continue from game to game?
- How might we adapt the [Canonical Lore DAO](https://hackmd.io/@TravisWyche/CanonDAOtemplate) to our WarGames to track these changes and consider lore incentive mechanisms? How might we dogfood this idea to create a **DAO template/pattern** that other groups in the ecosystem can fork and iterate?

### Game Rules (to be integrated into the playerbook)
#### Rules About the Rules (WG Rules)
- [First draft is outlined here](https://hackmd.io/@daohaus/WarGames-Briefs-Uberhaus)
- Should encourage and support players to exercise total freedom, especially potentially malicious, coercisive, or collusive behaviors. *We want the players to try to break the game!*
- Each act/level/phase is defined by its own local set of rules. 
    - New scenarios will be defined by their rules.
    - Players that divert from these rules are considered "out of bounds" with disciplinary action, such as: GM will pause their social account, admin will jail their wallet address.

<details>
  <summary> Q: How will a new player join the existing game? </summary>
A: New players can join at any time. Refer to onboarding flow for the minimum requirements, including: treasury amount, proposal intensity settings, activity/participation requirements, etc.
</details>

<details>
  <summary> Q: How will players join each each others DAOs? Is this allowed? </summary>
A: Anything goes! Players will decide this policy themselves through their own soft governance, forum, Snapshot, and on-chain ratification. This will include the social and technical requirements. Data from these actions will be applied towards justifying our IRL UH policies.
</details>

<details>
  <summary> Q: Are players allowed to RQ their DAOs to combine forces (tokens) with other player DAOs? </summary>
  
A: This can happen IRL, so yeah! Players can choose to make restrictions on this in-game if they desire. This will include the social and technical requirements. Data from these actions will be applied towards justifying our IRL UH policies.
</details>

<details>
  <summary> Q: Can anyone play WarGames? Are there restrictions? </summary>
A: WG is open to anyone and everyone! The only restrictions are following the correct onboarding flow, which has baked-in social consensus and curation mechanisms to attempt to weed out bad actors. This is an attack vector and a necessary theater of engagement for testing! If a bad actor gets through the social vetting, this will be an important learning experience in itself.
</details>

### Key Roles
#### Operator (UberPaladin?) - TBD
- [Refer to Bau's outline here.](https://github.com/HausDAO/daohaus-rangers/issues/57)
- TL;DR: players determine how this role is chosen and the limits of their responsibilities.
- How does WC feel about positioning this role for security?

#### Ghost (or God-King Admin if we choose) - Dekan
- One individual is required to spinup the starting infrastructure. In the case it is Dekan.
- Should be a technically omnipotent non-player of the testing team that avoids interfering with the gameplay itself.
- Attends to DAO and token settings.
- Is this role necessary? Can it be avoided? RQ after initial deployment?

#### Bot Master - Jeremy
- Installs and programs bots for player onboarding/coms on social channels. Currently occupied by Jeremy.
- Bots are an important attack vector of the simulation, so we might reconsider the neutrality of this role. She who controls the bots controls the universe.
- Might the Bot Master be player elected like the Operator?
- Does UH have it's own Discord? Will this be conducted on the DH server?

#### Game Master (akin to an UberPaladin? Community Engineer?) - UI369
- Delivers the lore to the players as an omniscient narrator, protagonist or antagonist character, or voluntarily by a player.
- The lore, responsibilities, and character elements can continue to shift as long as the primary testing objectives are preserved.

#### Rogue Flavortext Archer - BorrowLucid
- There's lots of flavor text to write all over the place. This creates a necessary cultural adhesive for immersion for the games.

#### Scum Master - TW
- Tracks the testing progress of the project.
- QA to ensure lore is aligned with the testing parameters.
- Tracks tasks and adds issues to the kanban board.
- Updates the SSOT across the game to facilitate knowledge sharing across teams and players.

