Runtime fingerprintToken readout from the active provider chain.
Live DS
Runtime
PlatformRottay
Rottay / ModernPlatform Flagship
Primary
#FFFFFFSecondary #A0A0A5
Radius
Compact runtime evidence across 3+ token signals.
Published DS package ยท Tenant Showcase ยท Rottay / modernShared route metadata for the active runtime, kept inline so the shell reads like a thin header band.
Palette
#FFFFFFRottay
Chrome
Modernrenderer posture
Radius
14pxsurface shape
Density
normalPlatform Flagship
Back to Platform
Navigation3 scenario rowsTier mix 0P / 0S / 15Pr
Scenario summary
Navigation in Platform is about controlled clarity, not ornamental UI.
Platform navigation is a productivity feature. It needs to help operators jump between deep modules without losing orientation. The workflow stays Platform-specific, but the live rendering should still come from the active docs runtime rather than a local preset.
Scenario rows3Named modules that anchor this category's product story.
Unique parts13Distinct structures, patterns, and primitives in this category.
Dominant archetypeTask moduleThe prevailing interaction shape across these modules.
Scenario rows
Scenario modules
Each row below captures a product-grade module, the component spread behind it, and what to scrutinize when the runtime changes.
Read orderStart with the title and archetype, then inspect composition balance and the part sample.
Proof checkConfirm the lane still reads like one product module after the runtime changes tone, density, and contrast.
01
Scenario module
Admin Sidebar
Collapsible sidebar with nested menu groups, icons, and active indicators.
Composition balancePrimitive-heavy assemblyA quick read on which layer is carrying most of the scenario weight.
Tier mix0P / 0S / 5Pr
Inspect forCheck whether the module still feels product-grade rather than like an isolated component demo.
Supporting partsRepresentative pieces behind this scenario lane.
Menu
Collapse
Badge
Avatar
+1 more
02
Scenario module
Command Palette
Keyboard-triggered command search with categorized results and shortcuts.
Composition balancePrimitive-heavy assemblyA quick read on which layer is carrying most of the scenario weight.
Tier mix0P / 0S / 5Pr
Inspect forCheck whether scanning rhythm, action placement, and row density still feel safe and fast.
Supporting partsRepresentative pieces behind this scenario lane.
Modal
Input
List
Kbd
+1 more
03
Scenario module
Breadcrumb System
Dynamic breadcrumbs with entity resolution and overflow dropdown.
Composition balancePrimitive-heavy assemblyA quick read on which layer is carrying most of the scenario weight.
Tier mix0P / 0S / 5Pr
Inspect forCheck whether the module still feels product-grade rather than like an isolated component demo.
Supporting partsRepresentative pieces behind this scenario lane.
Operational admin patterns for the flagship platform experience.
Runtime controls
TenantRottay
EngineModern
Operators
AdminsSupportPower users
The category has to stay legible for these roles even when a different tenant runtime shifts density or contrast.
Tempo and pressureContinuous throughout every workflowUse the scenario rows below to verify that hierarchy and control placement still hold up at this pace.
Design principles3 guardrails
Principle 01Keep hierarchy stable.
Principle 02Expose shortcuts for expert users.
Principle 03Preserve context during movement.
Active provider
Runtime audit
Rottay is rendering this appendix.
Use this page as a reference sheet: the scenario modules stay constant, while contrast, shell tone, and component personality respond to the active docs runtime.
Runtime
PlatformRottay
Rottay / ModernPlatform Flagship
Primary
#FFFFFFSecondary #A0A0A5
Radius
Compact runtime evidence across 3+ token signals.
14pxxl 18px
Density
normalBorder-light cards
Accent
Badge
roundedtop bar ยท solid dividers
Motion
springHover lift 2px
Keep stableNavigation still needs to feel native for Admins, Support, and 1 more even while the provider changes the surrounding chrome.
Stress pointContinuous throughout every workflow means hierarchy, action placement, and contrast cannot become ambiguous under a different runtime.
Read as one laneTask module should feel like one coherent chapter here rather than a stack of isolated component demos.