> For the complete documentation index, see [llms.txt](https://whitepaper.muish.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://whitepaper.muish.com/contact-and-community-engagement.md).

# Contact and Community Engagement

### **Contact & Community Access**

You don’t need permission to enter Muish—but if you have questions, we answer them.

***

#### **NFT & Token Inquiries**

For direct questions about $MUISH, NFTs, or project involvement:\
**Email:** <team@muish.com>\
We don’t outsource support. You’ll hear back from someone building it.

***

#### **Digital Channels**

The website holds the spine:\
**muish.com** — Live updates, docs, media kits, and dev logs.\
Additional platforms will be announced through the site and verified socials. No surprise launches. No stealth drops.

***

#### **Community Protocol**

This isn’t a hype machine. It’s a player-owned simulation. Our community strategy is simple:

* **Talk like humans.**
* **Ship real updates.**
* **Reward participation that changes something.**

Bounties, AMAs, faction channels, lore drops, bug hunts—it all happens in public.

***

#### **Transparency Commitments**

* Major updates are logged, not teased.
* All token sales and NFT events are announced ahead of time.
* Dev updates are time-stamped and archived.
* No fine print. If it matters, it’s on-chain or on-record.

***

#### **Feedback Loops**

We don’t farm engagement. We process signal.

Early feedback shapes mechanics. Player behavior reshapes systems. The roadmap is a starting point—not a rulebook.