WorldOS Authoring

Build a playable WorldOS Simulation through the public WorldOS MCP. Use only MCP capabilities exposed to the authorized account. Do not use Supabase, SQL, private APIs, platform source code, or repository-specific scripts as a fallback.

Start with the live contract

1. Call get_authoring_guide before designing or editing a world.
2. Treat the live guide and current tool schemas as the transport contract. Validation errors are write blockers; warnings describe quality or compatibility concerns and may be consciously accepted when the runtime supports the world.
3. If the WorldOS MCP is unavailable or unauthorized, stop and explain how to connect or reauthorize it. Never request an access token in chat.

Read the supporting material that matches the task:

• For gameplay and content design, read references/world-design.md.
• For deciding which app owns each persistent fact, read references/state-ownership.md.
• For locale overlays and template variables, read references/i18n-and-templates.md.
• Before any write, read references/acceptance-checklist.md.

When the player controls a polity or faction and durable territorial war drives the core loop, use the worldos-war-authoring specialist workflow and its live canonical template. Do not infer that workflow merely from a war-themed setting.