This atlas provides V7's cross-cutting visual models: the platform/realm trust boundary, executable action flow, durable creator/realm records, package lifecycle, capability composition, subsystem ownership, creator journey, and release evidence. Focused pages and current security/runtime/economic evidence remain authoritative.
Platform and realm trust landscape#
This picture is wider than it can be shown here. Move across it, or read it as text.
Drawn from its Mermaid source.
As text
Parts: - Creator and Mawu Studio - Package ingest validation and signing - Immutable package registry (data) - Realm fleet orchestrator - Player client - Identity gateway and admission - Moremi authoritative realm server - Ixchel WASM sandbox - Untrusted realm code - Declared capability boundary - Trusted world data social voice economy and storage APIs - Danu meshing - Nephthys durable world state (data) - Safety integrity and anti-cheat - Commerce payout and fraud controls - Governance moderation and appeals - Audit telemetry review and incident evidence (data) Connections: - Creator and Mawu Studio to Package ingest validation and signing - Package ingest validation and signing to Immutable package registry - Immutable package registry to Realm fleet orchestrator - Player client to Identity gateway and admission - Identity gateway and admission to Moremi authoritative realm server - Realm fleet orchestrator to Moremi authoritative realm server - Moremi authoritative realm server to Ixchel WASM sandbox - Ixchel WASM sandbox to Untrusted realm code - Untrusted realm code to Declared capability boundary - Declared capability boundary to Trusted world data social voice economy and storage APIs - Moremi authoritative realm server to Danu meshing - Danu meshing to Nephthys durable world state - Trusted world data social voice economy and storage APIs to Safety integrity and anti-cheat - Trusted world data social voice economy and storage APIs to Commerce payout and fraud controls - Trusted world data social voice economy and storage APIs to Governance moderation and appeals - Safety integrity and anti-cheat to Audit telemetry review and incident evidence - Commerce payout and fraud controls to Audit telemetry review and incident evidence - Governance moderation and appeals to Audit telemetry review and incident evidence
Show source
flowchart TB
Creator[Creator and Mawu Studio] --> Ingest[Package ingest validation and signing]
Ingest --> Registry[(Immutable package registry)]
Registry --> Fleet[Realm fleet orchestrator]
Player[Player client] --> Edge[Identity gateway and admission]
Edge --> Moremi[Moremi authoritative realm server]
Fleet --> Moremi
Moremi --> Ixchel[Ixchel WASM sandbox]
Ixchel --> RealmCode[Untrusted realm code]
RealmCode --> Caps[Declared capability boundary]
Caps --> Platform[Trusted world data social voice economy and storage APIs]
Moremi --> Danu[Danu meshing]
Danu --> Nephthys[(Nephthys durable world state)]
Platform --> Sekhmet[Safety integrity and anti-cheat]
Platform --> Abundantia[Commerce payout and fraud controls]
Platform --> Eunomia[Governance moderation and appeals]
Sekhmet --> Evidence[(Audit telemetry review and incident evidence)]
Abundantia --> Evidence
Eunomia --> Evidence
Untrusted code reaches the platform only through declared, enforced, metered, and observable capabilities. Signing identifies an immutable package; it does not make the code, content, rights, or behavior trusted.
Executable realm action sequence#
The realm server owns player authority, the sandbox owns execution isolation, policy owns capability admission, and platform services own durable effects. None can be replaced by a cooperative convention inside realm code.
Creator, package, realm, and governance records#
This picture is wider than it can be shown here. Move across it, or read it as text.
Drawn from its Mermaid source.
As text
Parts: - CREATOR - CREATOR_ORG - REALM - PACKAGE_RELEASE - PACKAGE - DEPENDENCY_PIN - CAPABILITY_GRANT - REVIEW_VERDICT - WORLD_SNAPSHOT - PLAYER_SESSION - PLAYER - GOVERNANCE_CASE - EVIDENCE_ITEM - RIGHTS_RECORD - PAYOUT_LEDGER - AUDIT_EVENT Connections: - CREATOR to CREATOR_ORG (one to zero or many): belongs_to - CREATOR_ORG to REALM (one to zero or many): owns - REALM to PACKAGE_RELEASE (one to zero or many): configures - PACKAGE to PACKAGE_RELEASE (one to zero or many): versions - PACKAGE_RELEASE to DEPENDENCY_PIN (one to zero or many): locks - PACKAGE_RELEASE to CAPABILITY_GRANT (one to zero or many): declares - PACKAGE_RELEASE to REVIEW_VERDICT (one to zero or many): receives - REALM to WORLD_SNAPSHOT (one to zero or many): versions - REALM to PLAYER_SESSION (one to zero or many): hosts - PLAYER to PLAYER_SESSION (one to zero or many): joins - REALM to GOVERNANCE_CASE (one to zero or many): governs - GOVERNANCE_CASE to EVIDENCE_ITEM (one to zero or many): contains - PACKAGE_RELEASE to RIGHTS_RECORD (one to zero or many): requires - CREATOR_ORG to PAYOUT_LEDGER (one to zero or many): earns - REALM to AUDIT_EVENT (one to zero or many): produces
Show source
erDiagram
CREATOR ||--o{ CREATOR_ORG : belongs_to
CREATOR_ORG ||--o{ REALM : owns
REALM ||--o{ PACKAGE_RELEASE : configures
PACKAGE ||--o{ PACKAGE_RELEASE : versions
PACKAGE_RELEASE ||--o{ DEPENDENCY_PIN : locks
PACKAGE_RELEASE ||--o{ CAPABILITY_GRANT : declares
PACKAGE_RELEASE ||--o{ REVIEW_VERDICT : receives
REALM ||--o{ WORLD_SNAPSHOT : versions
REALM ||--o{ PLAYER_SESSION : hosts
PLAYER ||--o{ PLAYER_SESSION : joins
REALM ||--o{ GOVERNANCE_CASE : governs
GOVERNANCE_CASE ||--o{ EVIDENCE_ITEM : contains
PACKAGE_RELEASE ||--o{ RIGHTS_RECORD : requires
CREATOR_ORG ||--o{ PAYOUT_LEDGER : earns
REALM ||--o{ AUDIT_EVENT : produces
Package, release, dependency, capability, review, realm, snapshot, governance, rights, and payout identities remain distinct so revocation, appeal, migration, rollback, and settlement can be reasoned about precisely.
Package and realm lifecycle#
This picture is wider than it can be shown here. Move across it, or read it as text.
Drawn from its Mermaid source.
As text
Parts: - Start (initial) - Draft - Validated - SandboxTested - Reviewed - Signed - Staged - Published - Active - Suspended - Remediating - RolledBack - Rejected - End (final) Connections: - Start to Draft - Draft to Validated: manifest schema dependencies and quotas pass - Validated to SandboxTested: production-equivalent execution passes - SandboxTested to Reviewed: safety rights integrity and quality gates pass - Reviewed to Signed: immutable package release created - Signed to Staged: eligible test realm cohort - Staged to Published: discovery and creator release policy pass - Published to Active: realm fleet runs version - Active to Suspended: abuse fraud rights integrity or incident signal - Suspended to Remediating: creator or operator correction - Remediating to Reviewed - Active to RolledBack: prior package and snapshot restored - RolledBack to Active: recovery evidence passes - Draft to Rejected: invalid prohibited or abandoned - Rejected to End
Show source
stateDiagram-v2
[*] --> Draft
Draft --> Validated: manifest schema dependencies and quotas pass
Validated --> SandboxTested: production-equivalent execution passes
SandboxTested --> Reviewed: safety rights integrity and quality gates pass
Reviewed --> Signed: immutable package release created
Signed --> Staged: eligible test realm cohort
Staged --> Published: discovery and creator release policy pass
Published --> Active: realm fleet runs version
Active --> Suspended: abuse fraud rights integrity or incident signal
Suspended --> Remediating: creator or operator correction
Remediating --> Reviewed
Active --> RolledBack: prior package and snapshot restored
RolledBack --> Active: recovery evidence passes
Draft --> Rejected: invalid prohibited or abandoned
Rejected --> [*]
Package release and world snapshot rollbacks are coordinated but different. Suspension must contain active execution and discovery without destroying the evidence needed for investigation and appeal.
Capability composition#
Review approves an immutable hash and manifest. Runtime admission still checks the current realm, actor, policy, quota, revocation, and operation version.
V7 ownership estate#
Drawn from its Mermaid source.
As text
Tree:
- Mawu creator republic
- Creation
- Realm model and Mawu Studio
- Moremi roleplay framework
- Ixchel packages dependencies and tooling
- Discovery migration and portability
- Runtime
- Moremi authority and netcode
- Danu population and server meshing
- Nephthys persistence snapshots and rollback
- Fleet hosting data and compliance
- Community and economy
- Pheme voice and Hera social
- Streaming and Ori incarnation
- Abundantia distribution payouts and fraud
- Rights matching takedown and portability
- Governance
- Sekhmet safety child protection and integrity
- Eunomia governance moderation and appeals
- Operator data protection and economics
- Observability eval gates rollout and incidentsShow source
mindmap
root((Mawu creator republic))
Creation
Realm model and Mawu Studio
Moremi roleplay framework
Ixchel packages dependencies and tooling
Discovery migration and portability
Runtime
Moremi authority and netcode
Danu population and server meshing
Nephthys persistence snapshots and rollback
Fleet hosting data and compliance
Community and economy
Pheme voice and Hera social
Streaming and Ori incarnation
Abundantia distribution payouts and fraud
Rights matching takedown and portability
Governance
Sekhmet safety child protection and integrity
Eunomia governance moderation and appeals
Operator data protection and economics
Observability eval gates rollout and incidents
The map locates canonical ownership. Creator-facing features may compose every branch, but no realm or creator owns the trusted enforcement plane.
Creator publication journey#
Drawn from its Mermaid source.
As text
Steps: - 1. Author realm package assets and dependencies (good). Build. Creator. Score 5 of 5. - 2. Declare minimal capabilities rights and budgets (good). Build. Creator. Score 5 of 5. - 3. Run sandbox determinism security and migration tests (good). Prove. Engineering, QA. Score 5 of 5. - 4. Pass safety rights economy and governance review (good). Prove. Trust, Rights. Score 5 of 5. - 5. Sign version stage realm and verify world state (good). Publish. Release, SRE. Score 4 of 5. - 6. Enter eligible discovery and payout scope (good). Publish. Product, Economy. Score 5 of 5. - 7. Observe abuse fraud cost integrity and capacity (good). Operate. Operators. Score 5 of 5. - 8. Suspend appeal migrate or roll back with evidence (good). Operate. Governance, SRE. Score 5 of 5.
Show source
journey
title From V7 realm idea to governed live service
section Build
Author realm package assets and dependencies: 5: Creator
Declare minimal capabilities rights and budgets: 5: Creator
section Prove
Run sandbox determinism security and migration tests: 5: Engineering, QA
Pass safety rights economy and governance review: 5: Trust, Rights
section Publish
Sign version stage realm and verify world state: 4: Release, SRE
Enter eligible discovery and payout scope: 5: Product, Economy
section Operate
Observe abuse fraud cost integrity and capacity: 5: Operators
Suspend appeal migrate or roll back with evidence: 5: Governance, SRE
The journey includes failure and correction paths because executable UGC cannot be safely operated as a one-time upload approval.
Evidence order#
This is an evidence sequence, not a promise that all realm capabilities launch together.
How to use this atlas#
Use the landscape and sequence for trust-boundary review, the ER/state diagrams for versioning and incidents, the class/estate views for API ownership, and the journey/timeline for publication and release. Continue to the V7 guide, feature index, and architecture index.