Mawu · Architecture

V7 — Architecture (Page Index)

A focused page within the Mawu Architecture documentation. The full map and every sibling page live in the Architecture hub.

7sections3 minread1diagram

On this page

This directory holds the V7 (Mawu — a UE5 + Rust open-world "creator republic" of player-authored, server-authoritative realms with executable UGC) architecture reference, decomposed from the single ../V7_ARCHITECTURE.md hub into focused, in-depth, code-grounded pages. The hub remains the canonical entry point and preserves every section heading; each page below expands one part of the system with richer, code-grounded detail and an honest implemented / spec-only status. The companion feature map lives in ../V7_features.md.

Cross-reference convention. Page-to-page links are relative (./<slug>.md). Platform-foundation links point at the shared platform/ space.

Architecture landscape#

flowchart TB Studio[Mawu Studio and creator tooling] --> Ingest[Validation review signing and package registry] Ingest --> Fleet[Realm fleet and version orchestration] Player[Player clients and identity edge] --> Moremi[Moremi authoritative realm server] Fleet --> Moremi Moremi --> Ixchel[Ixchel WASM sandbox] Ixchel --> Caps[Capability enforcement and quotas] Caps --> Services[Trusted world data voice social economy and governance APIs] Moremi --> Danu[Danu server meshing] Danu --> Nephthys[(Nephthys persistence snapshots and recovery)] Services --> Sekhmet[Safety child protection integrity and anti-cheat] Services --> Abundantia[Distribution payouts and anti-fraud] Services --> Eunomia[Governance moderation appeals and Ori bridge] Nephthys --> Operations[Hosting data compliance observability performance and launch] Sekhmet --> Operations Abundantia --> Operations Eunomia --> Operations

The arrows cross explicit trust boundaries. Signing identifies a reviewed immutable package; sandboxing limits execution; capability policy authorizes individual effects; authoritative services commit state; and governance and operations retain containment, appeal, and recovery control.

Trace a change from package/hash/dependency and capability manifest through ingest/review, fleet activation, sandbox execution, Moremi authority, Danu/Nephthys state, trusted services, receipts/audit, and incident rollback. Pair it with the feature index to verify creator and player-visible behavior, not only infrastructure.

Every focused architecture page appears exactly once below. The V7 documentation guide supplies the trust/release model and role paths; the diagram atlas supplies the shared visual language. Backlog, dependencies, gap/review evidence, security and adversarial tests, signed package/runtime state, provider reconciliation, and fleet operations determine completion.

Read failures in the same ownership order. Package or dependency failures stop before activation; sandbox or capability failures terminate the offending realm execution; authority or persistence failures invoke recovery; trusted service failures withhold the requested platform effect; and governance or launch failures preserve the last safe release. That order keeps containment local while ensuring every rejected transition leaves evidence for operators, creators, and appeal reviewers.

Orientation#

Realm Backbone#

Executable UGC#

Character, Voice & Social#

Economy, Trust & Governance#

Operations#