# GMR Trust

### Role outlines

#### Marketing Lead *(signer — Marketing wallet)*

Own go-to-market for products such as Battle Leet and ecosystem awareness. Build the BL marketing plan: shipping a lean **GDD**, pushing a **Steam Coming Soon** (if possible), social campaigns, streamer outreach & exclusives, festival submissions, competitor & KPI research, KOL/collab pipeline, paid ads with A/B tests and budget caps. Partners closely with **Comms** and **Community** to execute programs; proposes Marketing spends (later) within policy.

#### Comms Lead

Own cross-channel communications: set and run the update cadence (align with CEO, Tech Lead and Marketing Lead), write posts/announcements, prep podcast/AMA notes, craft media assets (clips, visuals), and co-manage official email inboxes with Marketing. Translates product/ops into clear, timely comms; works tightly with **Marketing** on campaigns and with **Community** on events.

#### Ops Lead *(signer — Development wallet)*

Own the operating rhythm: agendas, decision & risk logs, access lists, technical incident triage, and readiness planning. Coordinates with Marketing/Comms to keep milestones realistic; proposes small Ops spends later (infra, tools) within policy. Works closely with CEO and Tech Lead.

#### Community Success Lead

Support and coordinate the mod team, keep discussions healthy, and co-run community events with Comms/Marketing. Shares anonymised moderation highlights and practical improvements; can **recommend** mod additions/removals. Offers collaborative support for mods and Trust other members.

#### Treasury Reporter

Publish the weekly ledger. Reconcile inflows/outflows for both Marketing and Development wallets, explain variances, and ensure sensitive data is handled responsibly (redact personal/supplier details where needed). Independent of signers to keep reporting clean.

### Members

**Members appointed from the project founders:**

* **CEO** 
* **Tech Lead**

**Members appointed from the community:**

* **Marketing Lead** (marketing wallet signer)
* **Communications Lead**
* **Ops Lead** (development wallet signer)
* **Community Lead**
* **Treasury Reporter**

### Signer matrix

* **Marketing wallet (2-of-3):** CEO • Tech Lead • **Marketing Lead** *(Tech Lead remains neutral co-signs with the mod by default unless harmful)*
* **Development wallet (2-of-3):** CEO • Tech Lead • **Ops Lead** *(Tech Lead remains neutral co-signs with the mod by default unless harmful)*

### Appointments

* Marketing Lead (signer): Fithos
* Communications Lead: Frank
* Community Lead: Ultimo
* Ops Lead (signer): The Best Mark
* Treasury Reporter: Open to community applications, more details soon

{% hint style="success" %}
One person = one role; no shared roles. Official emails will be set up for Comms, Marketing and Ops leads.
{% endhint %}


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://whitepaper.gmr.center/gmr-center/gmr-trust.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.