Studio Switching And Scenes
This file keeps its historical filename for existing doc links. The current
This file keeps its historical filename for existing doc links. The current product model has three visible layers: Universe resources, Runtime or Studio switching, and Scenes inside the active resource.
Universe Resources
| Resource | Route | Meaning |
|---|---|---|
| Universe | /@user | Owner home that lists profile, Runtimes, Studios, apps, Spaces, and future activity. |
| Runtime | /@user/runtime/:runtimeSlug | Repo-like runtime object, such as /@esmadrider/runtime/os. |
| Studio | /@user/studios/:studioSlug | Owner-scoped Studio resource. |
| Profile settings | /@user/settings/profile | User profile settings. |
Switching
Studio switching is the global resource/session layer. It moves the user between open, recent, or pinned Runtime and Studio resources:
- OS Runtime /
os - Atlas Studio / Knowledge Map
- Grid Studio / Operations Board
- Ops Studio / Growth Operations
Studio switching is not called a virtual desktop and is not called a Scene.
Ctrl/Cmd + Shift + K opens the Switcher for fast switching. Prox Mission
Control also shows the same session layer in its top band.
Scene Switching
A Scene is a layout or work state inside the active Runtime or Studio. It is not a new public URL resource. Every Studio Engine can offer Scenes, but the Shell owns the shared shortcut and overview model.
| Host | Example Scene |
|---|---|
| OS Runtime | Window layout scene. |
| Atlas Studio | Collection and context scene. |
| Grid Studio | Dashboard scene. |
| Ops Studio | Metric, record, and review scene. |
Ctrl + Shift + ArrowLeft and Ctrl + Shift + ArrowRight move between Scenes
inside the active resource. A resource with one Scene may no-op.
Routes
Runtime and Studio routes are user-scoped:
/@esmadrider
/@esmadrider/runtime/os
/@esmadrider/runtime/os/data
/@esmadrider/studios/atlas
/@esmadrider/studios/grid
/@esmadrider/studios/ops
/dev
/dev/studios/site
/dev/studios/webview
/dev/studios/device
/dev/studios/cli
/dev/studios/admin
/dev/studios/block
/dev/studios/flow
/dev/studios/board
/dev/studios/ide
/dev/studios/single-app/studio remains the AI Entry route. Product Runtime and Studio resources no
longer use the old development route family. Development-only engines are
reachable through /dev in local builds and stay out of Switcher, New, and
public navigation.