Prox OS Internal Docs
PlatformArchitectureOverview

Platform Runtime Architecture

Prox OS is a user-scoped runtime platform. The outer platform frame owns

Prox OS is a user-scoped runtime platform. The outer platform frame owns identity, navigation, Alma, Inspector, and platform preferences. Each Runtime owns its own command chrome, Dock, visual overlays, windows, and local display behavior.

User-Scoped Routes

RouteScopeProduct meaning
/@userUniversePublic User Space for a person or organization. It lists owned Runtimes, Studios, apps, Spaces, profile metadata, and future activity signals.
/@user/runtime/:runtimeSlugRuntimeOwner-scoped Runtime root. The default seeded Runtime can be /@esmadrider/runtime/os.
/@user/runtime/:runtimeSlug/:runtimeModeRuntime modeRuntime Command Strip modes such as Data, Apps, Automations, Collect, Settings, and Publish.
/@user/studios/:studioSlugStudioOwner-scoped Studio route for Atlas, Grid, Device, Site, Board, Flow, Block, and other registered Studio Engines.
/@user/settings/profileUser settingsProfile settings for the owner. It is user scope, not Runtime scope.

Runtimes are repo-like objects in the product model: users own them, name them, rename them, publish or keep them private, and can eventually create many of them. os is only the seeded slug for the first OS Runtime, not a hard-coded platform singleton.

Scope Boundaries

ScopeOwnsDoes not own
PlatformGlobal navigation, brand, Launchpad, Universe, App Store, Community, Alma side and rail width, Inspector side rule, platform navigation position and flow, platform theme, platform safety default.Runtime Dock, Runtime Command Strip placement, Runtime screensaver, Runtime cursor, runtime-local wallpaper or density.
RuntimeRuntime Command Strip placement and flow, Runtime Dock position and size, app windows, pinned and running apps, Runtime screensaver, Runtime cursor, runtime theme override, runtime-local display effects.Platform navigation, Alma side, Inspector side rule, user profile settings, global app store entries.
StudioStudio entry route, Studio name, Studio first command tab, Studio About menu, Studio-owned interior UI.Platform settings, Runtime Dock, OS Runtime window manager state.
UniverseOwner profile, owned Runtimes, owned Studios, apps, Spaces, and future user graph.Runtime-local display settings and platform chrome settings.

Display Options is runtime-local. Platform Options is platform-level. Settings must be added to the smallest scope that can own the behavior without leaking into sibling surfaces.

Chrome Layers

Chrome layerRoute visibilityResponsibilities
Platform NavigationPlatform frame and runtime frameBrand Prox OS, Launchpad, Universe, App Store, Community, Studio Switcher, command search, user menu, Platform Options.
Runtime Command StripRuntime and Studio containers onlyCurrent Runtime or Studio tab, mode tabs, About menu, runtime-local placement, runtime-local flow.
Runtime DockOS Runtime onlyPinned apps, running apps, active app, minimized/background state, runtime-local position and size.

Platform Navigation does not read Runtime Display Options. Runtime Command Strip does not own platform destinations such as Universe or Community.

Runtime Command Strip

CapabilityBehavior
PlacementSupports top, bottom, left, and right inside the Runtime frame.
Flowstandard and reversed affect the Runtime Command Strip layout only.
First tabRepresents the active Runtime or Studio, such as OS or Atlas Studio.
About menuThe first tab has a separate chevron trigger. Clicking the tab changes/selects the mode; clicking the chevron opens the About menu.

Studio containers use the same command strip component with Studio-specific About menu labels such as About Atlas, About Grid, or About Block.

Dock Model

Dock concernRuntime behavior
Pinned appsAlways shown first in the OS Runtime Dock.
Running appsAdded after a visual divider when they are not already pinned.
Active appMarked from the focused window.
Minimized or background stateReflected when window state exists.
PositionSupports top, bottom, left, and right inside the OS Runtime.
SizeRuntime-local numeric preference controls item size and container thickness.

The Dock is not part of Platform Navigation and should not show Universe, Community, or other global platform links.

Platform Options

SettingScopeEffect
Alma positionPlatformPlaces Alma rail and panel on the left or right side of the platform runtime frame.
Inspector side rulePlatformInspector renders opposite Alma by default.
Platform navigation positionPlatformPlaces Platform Navigation at the top or bottom of the platform frame.
Platform navigation flowPlatformControls platform navigation item flow and alignment.
Platform themePlatformControls Platform Navigation, Alma, Inspector, platform pages, and the default inherited Runtime theme.
Alma rail widthPlatformControls Alma rail width.
Safety mode defaultPlatformStores the default safety posture future runtimes and apps can read.

These settings are persisted as local platform preferences today and can be backed by backend user preferences later.

Display Options

SettingScopeEffect
Runtime Command Strip positionRuntimeMoves the command strip inside the Runtime frame.
Runtime Command Strip flowRuntimeChanges command strip flow inside the Runtime frame.
Runtime Dock positionRuntimeMoves the OS Runtime Dock inside the Runtime viewport.
Runtime Dock sizeRuntimeChanges Dock item size and container thickness.
ScreensaverRuntimeCovers only the OS Runtime content layer, not Platform Navigation, Alma, Inspector, or the command strip.
CursorRuntimeApplies only inside the OS Runtime viewport.
Runtime themeRuntime visual preferenceDefaults to platform, then can independently choose system, light, or dark for runtime-facing surfaces.
Density and wallpaperRuntime visual preferenceAffects runtime-facing surfaces without changing Platform Navigation ownership.

Theme Background Principle

Root backgrounds must be defined at the root container level for both light and dark themes. Homepage and website backgrounds must not depend on an inner section being mounted. Theme variables should include a stable page background, mesh/radial layer, and surface layer for dark mode so deployment bundling or route changes cannot leave the first viewport visually blank.

Leave-Site Policy

Prox OS does not use browser-level beforeunload prompts. If a runtime needs confirmation before leaving, it must use an app-level custom confirmation dialog. Community, Universe, platform pages, and Studio routes should not install native leave-site handlers.

Naming Rules

Product areaDisplay wordingCode vocabulary
Platform brandProx OS / Prox OS when ASCII-onlyGlobalPlatformNavigation, PlatformOptions
User homeUniverseUserUniverseSurface, universeMockData
Post-login app entryLaunchpadLaunchpadSurface
Runtime objectRuntimeruntimeSlug, RuntimeDock, RuntimeCommandStrip
Runtime settingsDisplay OptionsdisplayOptions, runtimeDockPosition, runtimeCommandStripPlacement
Platform settingsPlatform OptionsplatformNavigationPosition, platformNavigationLayout, almaSettings
Platform AI railAlmaAlmaRail, AlmaPanel
Context panelInspectorInspector

On this page