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 · Page Structure · 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
25 structures6 groups
Structures
The page-scaffolding layer for headers, command rails, record framing, dashboard context, and feedback shells.
IdentityControlContextFeedback
How to read this layer
Page chrome before surfaces
Reach for structures once the underlying pattern is chosen and the remaining problem is page-level hierarchy, separators, command placement, or supporting context.
Patterns
Reusable task behavior
Structures
Page framing around the task
Surfaces
Full route contract
Groups
6
Headers, workspaces, records, dashboards, and feedback shells.
Surface recipes
36
Structures should stay reusable across surface-level route contracts.
Workspace tools
11
The densest group proves how much command scaffolding the system can support.
Primary scope
Page chrome
This layer is about framing, section rhythm, and supporting context around tasks.
Read The Layer Fast
These cues should help teams decide quickly whether the problem belongs in structures or should stay lower in the stack.
Premium docs guidance tray
Use when
The task widget already exists, but the screen around it still needs hierarchy, command placement, or breathing room.
Expect
Headers, toolbars, section framing, guidance trays, rails, and loading shells that make dense pages readable.
Escalate after
Patterns prove the reusable task first. Structures then frame that task before surfaces take over full-route contracts.
Browse Groups
Start with the screen responsibility, then drill into the structure export.