worldos-authoringlisted

# 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](references/world-design.md). - For deciding which app owns each persistent fact, read [references/state-ownership.md](references/state-ownership.md). - For locale overlays and template variables, read [references/i18n-and-templates.md](references/i18n-and-templates.md). - Before any write, read [references/acceptance-checklist.md](references/acceptance-checklist.md). ## Respect write intent Read-only requests such as “review,” “audit,” “explain,” or “show me a proposal” do not authorize creation or updates. Stop after research, a candidate world payload, or validation. Call a write tool only when the user clearly asks to create,