V7 Documentation Guide — Mawu

This guide is the curated front door to V7, Mawu: The Open World & Creator Republic—a UE5 and Rust platform for player-authored, server-authoritative realms with executable UGC. Its defining contract is not creation alone; it is creation inside a hard trust boundary that keeps realm code sandboxed, world state durable, economies defensible, voice/social systems governable, creators paid, and operators able to contain harm.

Like V6, V7 begins from an originating feature design. The derived backlog and current implementation, security, economic, operational, and release evidence govern completion truth.

Documentation map#

mindmap root((V7 documentation)) Creator experience Realm model and massive population Moremi roleplay framework Mawu Studio Ixchel executable modding Community Pheme voice and Hera social Streaming incarnation and live service Discovery migration and portability Creator republic and payouts Trust boundary WASM sandbox and capability model Server authority anti-cheat and child safety Economy firewall and anti-fraud Eunomia governance and appeals Operations Danu meshing and Nephthys persistence Fleet data residency and rollback Observability performance and eval gates Backlog dependencies and launch evidence

Start with the question#

Question	Canonical starting point	What it covers
What does V7 promise creators and players?	Feature hub, feature index, and overview/posture	Realm creation, play, executable UGC, social continuity, economy, governance, and launch.
Where is the platform/realm trust boundary?	Glossary/trust boundary and architecture thesis	Trusted platform authority, untrusted realm code/content, capability boundaries, and topology.
How does executable UGC run safely?	Ixchel feature, Ixchel architecture, and creator DX	WASM sandbox, capabilities, quotas, dependencies, review, signing, observability, and developer workflow.
How are realms authoritative and durable?	Realm/Danu feature, Moremi netcode, Danu/Nephthys, and rollback	Server authority, meshing, persistence, migration, snapshots, recovery, and rollback.
How do economy and governance resist abuse?	Economy/rights feature, Abundantia architecture, Eunomia, and Sekhmet	Payouts, fraud, rights, child safety, moderation, governance, appeals, and cross-version identity.
What is actually supported?	V7 backlog, gap analysis, product review, current code/tests/security evidence, and release review	Conservative status by creator, realm, package, economy, region, and platform.
Which dependencies compose V7?	Dependency registry	Shared engines/domains, versions, ownership, trust, and fallback expectations.
Where are the visuals?	V7 diagram atlas and the global diagram gallery	Curated realm, package, trust, economy, governance, and rollout models.

Trust and release model#

stateDiagram-v2 [*] --> Draft Draft --> Validated: manifest schema dependencies and quotas pass Validated --> Sandboxed: package executes with declared capabilities Sandboxed --> Reviewed: automated safety integrity and rights gates pass Reviewed --> Published: signed version enters eligible discovery scope Published --> Active: realm fleet runs the immutable version Active --> Suspended: safety fraud rights or integrity signal Suspended --> Remediated: corrected version and review evidence Remediated --> Published Active --> RolledBack: operator restores prior package or world snapshot RolledBack --> Active: verified recovery

Every claim names the immutable package version, realm, capability set, creator, tenant/region, fleet cohort, and evidence revision. A WASM module is not safe because it starts; a manifest is not capability enforcement; a signed package is not rights clearance; a realm snapshot is not proven restoration; and a payout record is not settlement without provider/ledger reconciliation.

Recommended reading journey#

journey title From V7 creator idea to governed realm section Create Define realm package capabilities and dependencies: 5: Creator Validate locally with production-equivalent limits: 5: Creator, Engineering section Review Run sandbox safety rights and integrity gates: 5: Trust, QA Inspect economy governance and child-safety posture: 5: Governance section Publish Sign immutable version and stage a cohort: 4: Release Verify authority persistence discovery and payout: 5: SRE, Product section Operate Observe contain appeal migrate and roll back: 5: Operators Update docs diagrams evidence and runbooks: 5: Owners

Creator product and developer experience#

Start with the feature index. Read the realm, Moremi, Ixchel, Studio, social, economy, governance, and launch pages as one creator journey. Document errors, limits, review results, versioning, dependency resolution, migration, discovery eligibility, payout status, and recovery—not only the happy authoring path.

Platform and runtime engineering#

Start with the architecture index. Trace package ingest/signing, capability enforcement, Moremi authority, Danu meshing, Nephthys persistence, Nàná data, Pheme/Hera, Abundantia, Sekhmet, Eunomia, fleet/data residency, telemetry, and tests. Realm code never bypasses platform authority through a convenient shared service.

Trust, economics, QA, and operations#

Exercise malicious imports, quota exhaustion, nondeterminism, dependency revocation, package/version conflict, state migration, abuse/report/appeal, child accounts, voice harassment, fraud/chargeback, rights match/takedown, region denial, host loss, snapshot restore, rollout, and rollback. Validate both pre-publication gates and behavior under sustained live load.

Page-set organization#

Feature index — 12 focused topics across realms, executable UGC, Studio, social/continuity, economy, governance, and launch.
Architecture index — 10 focused topics across topology, authority/meshing/persistence, sandboxing, data/voice/social, economy, safety/governance, fleet, and operations.
V7 diagram atlas — trust, execution, durable entities, package lifecycle, capability composition, ownership, and rollout.
Root gap/backlog/dependency/review/audit records plus docs/ and release/ — focused policy, migration, economic, protection, rollback, and launch evidence.

Documentation quality contract#

Every canonical page stays substantial, indexed exactly once, visually explicit, and precise about trusted/untrusted ownership, immutable versions, capabilities, authority, rights, economic settlement, and evidence. Runtime or policy changes update contracts, migrations, adversarial/security/integration tests, backlog/evidence, and runbooks. Generated Docs Center integrity, freshness, search, diagram gallery, and desktop/mobile checks pass.