Mawu · Guides & deep dives

V7 Diagram Atlas

Untrusted code reaches the platform only through declared, enforced, metered, and observable capabilities.

9sections1 minread

On this page

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#

FlowchartFlowchart: 17 steps and 18 connections.Creator and Mawu StudioPackage ingest validationand signingImmutable packageregistryRealm fleet orchestratorPlayer clientIdentity gateway andadmissionMoremi authoritative realmserverIxchel WASM sandboxUntrusted realm codeDeclared capabilityboundaryTrusted world data socialvoice economy and storageAPIsDanu meshingNephthys durable worldstateSafety integrity andanti-cheatCommerce payout andfraud controlsGovernance moderationand appealsAudit telemetry review andincident evidence
Flowchart: Flowchart. Flowchart: 17 steps and 18 connections.

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#

sequenceDiagram actor Player participant Realm as Realm server participant Sandbox as Ixchel sandbox participant Policy as Capability policy participant Service as Trusted platform service participant Store as Nephthys state Player->>Realm: Authenticated gameplay intent Realm->>Sandbox: Invoke package version with bounded context Sandbox->>Policy: Request declared capability and quota alt denied throttled or suspended Policy-->>Sandbox: Named refusal and audit reason Sandbox-->>Realm: Safe deterministic failure else admitted Policy-->>Sandbox: Scoped capability token Sandbox->>Service: Versioned idempotent operation Service->>Store: Authoritative read or write Store-->>Service: Durable result or conflict Service-->>Sandbox: Typed receipt and remaining budget Sandbox-->>Realm: Deterministic realm outcome end Realm-->>Player: Authoritative visible result

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#

Entity-relationship diagramEntity-relationship diagram: 16 entities and 15 relationships.belongs_toownsconfiguresversionslocksdeclaresreceivesversionshostsjoinsgovernscontainsrequiresearnsproducesCREATORCREATOR_ORGREALMPACKAGE_RELEASEPACKAGEDEPENDENCY_PINCAPABILITY_GRANTREVIEW_VERDICTWORLD_SNAPSHOTPLAYER_SESSIONPLAYERGOVERNANCE_CASEEVIDENCE_ITEMRIGHTS_RECORDPAYOUT_LEDGERAUDIT_EVENT
Entity-relationship diagram: Entity-relationship diagram. Entity-relationship diagram: 16 entities and 15 relationships.

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#

State diagramState diagram: 14 states and 15 transitions.manifest schema dependencies and quotas passproduction-equivalent execution passessafety rights integrity and quality gates passimmutable package release createdeligible test realm cohortdiscovery and creator release policy passrealm fleet runs versionabuse fraud rights integrity or incident signalcreator or operator correctionprior package and snapshot restoredrecovery evidence passesinvalid prohibited or abandonedDraftValidatedSandboxTestedReviewedSignedStagedPublishedActiveSuspendedRemediatingRolledBackRejected
State machine: State diagram. State diagram: 14 states and 15 transitions.

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#

classDiagram class RealmInvocation { realmId packageVersion actorId tick } class CapabilityManifest { allowedApis quotas dataScopes } class SandboxLease { instanceId fuelBudget deadline } class PlatformReceipt { operationId stateVersion auditRef } class ReviewEnvelope { packageHash rightsRefs verdicts } RealmInvocation --> CapabilityManifest : constrained by CapabilityManifest --> SandboxLease : instantiates SandboxLease --> PlatformReceipt : may emit ReviewEnvelope --> CapabilityManifest : approves version

Review approves an immutable hash and manifest. Runtime admission still checks the current realm, actor, policy, quota, revocation, and operation version.

V7 ownership estate#

Mawu creator republicMind map: 21 ideas.Mawu creator republicCreationRealm model and MawuStudioMoremi roleplay frameworkIxchel packagesdependencies and toolingDiscovery migration andportabilityRuntimeMoremi authority andnetcodeDanu population and servermeshingNephthys persistencesnapshots and rollbackFleet hosting data andcomplianceCommunity and economyPheme voice and HerasocialStreaming and OriincarnationAbundantia distributionpayouts and fraudRights matching takedownand portabilityGovernanceSekhmet safety childprotection and integrityEunomia governancemoderation and appealsOperator data protectionand economicsObservability eval gatesrollout and incidents
Mind map: Mawu creator republic. Mind map: 21 ideas.

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 incidents
Show 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#

From V7 realm idea to governed live serviceUser journey: 8 stages.1Author realm package assets and dependenciesBuild. Creator. Score 5 of 5.2Declare minimal capabilities rights and budgetsBuild. Creator. Score 5 of 5.3Run sandbox determinism security and migration testsProve. Engineering, QA. Score 5 of 5.4Pass safety rights economy and governance reviewProve. Trust, Rights. Score 5 of 5.5Sign version stage realm and verify world statePublish. Release, SRE. Score 4 of 5.6Enter eligible discovery and payout scopePublish. Product, Economy. Score 5 of 5.7Observe abuse fraud cost integrity and capacityOperate. Operators. Score 5 of 5.8Suspend appeal migrate or roll back with evidenceOperate. Governance, SRE. Score 5 of 5.
User journey: From V7 realm idea to governed live service. User journey: 8 stages.

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#

timeline title V7 release evidence Contract : Realm package capability dependency and data invariants : Creator rights economy governance and appeal policy Runtime : Sandbox enforcement authority meshing persistence and services : Voice social discovery payouts and operator controls Verification : Adversarial security migration rollback and load tests : Safety rights fraud accessibility and regional evidence Candidate : Signed package staged realm snapshots and incident rehearsal : Fleet observability discovery and payout reconciliation Supported : Named versions capabilities realms regions and cohorts : Current revocation incident appeal and recovery evidence

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.