Build on the runtime
Start with source.
Keep world authority.
MutSea's native runtime and world adapters are open source. Hosted platform APIs and a public SDK service are still in development.
Run your own development world
Use the repository quick start and retained .NET 8 build. Fresh deployments default to PostgreSQL. Provision a separate database/role and private configuration before starting a simulator. Never point a test instance at a live world's database.
The Docker path builds the inherited runtime, then the World adapter against the same assemblies. Back up native data and journals together, stop normally, and retain a tested rollback. Keep database, console, planner and citizen interfaces private.
Use the existing world boundary
Inspect structured entities. Propose a bounded WorldAction or WorldSpec. Let native policy and permissions validate it. Preview, obtain human approval, commit and record the result. Use guarded Undo when supported. An LLM response is never a database-write permission.
- World adapters, deterministic placement and private transport
- PostgreSQL configuration and persistence
- Reusable world templates and rollback
- Actual native demo and acceptance limits
One native account, web and world
Limited preview registration queues a pinned starter-avatar choice. The native runtime provisions identity, appearance, inventory and home before activating an ordinary user. The web process cannot assign roles or write world objects and inventory. Existing users sign in with the same First Last name and world password.
The portal provides profile information, native home/last location, password changes and saved recovery codes. Email reset, public administration APIs, managed hosting and a general platform SDK are not available. Operators retain the inherited private console and versioned provisioning runbooks.
Platform direction
Community primitives, reusable experience packages, editor-neutral WorldSync, live Studio authoring and third-party SDKs build on this foundation. They are roadmap capabilities, not public endpoints offered today.
Preserve BSD/upstream source notices and separately audit imported content licenses. Share redacted reproduction steps, not private INI, account, database or capability files.