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.
LayerStructure tierPage framing around reusable tasks.
GroupWorkspaceShares the same audit lens and pairing rules as its group.
Enginesclassic / modern / rusticExpect parity in spacing, priority, and section rhythm.
Audit trayUse this page to judge whether the structure creates hierarchy before the surrounding surface starts doing the heavy lifting.
Review 01control clusteringShould be obvious on the first scan without relying on surface chrome for rescue.
Review 02speed to first actionShould stay clear once actions, counts, and support context compete for attention.
Review 03state visibilityShould keep dense content readable instead of turning the screen into a flat stack.
Common pairings
tableskanban boardsgallery views
Usually lands in
ListSurfaceReportSurface
Live preview
Compare rhythm, action placement, and supporting context across engines while the active tenant remains real.
classicmodernrustic
Compare enginesLook for spacing, action placement, and section rhythm before brand flavor.
Ignore wrappersJudge the structure itself, not route-level surface chrome or page copy.
Escalate laterMove higher only when the route contract or workflow packaging is the missing piece.
Engine comparisonExport Button render checkEach engine gets the same structure with the same tenant. Focus on spacing, hierarchy, and action cadence rather than wrapper chrome.
Rottay3 live engines
Review checklist
These are the checks that should feel obvious on the first pass, before you audit the surrounding surface or route-level content.
Check 01control clusteringShould be obvious on the first scan without relying on surface chrome for rescue.
Check 02speed to first actionShould stay clear once actions, counts, and support context compete for attention.
Check 03state visibilityShould keep dense content readable instead of turning the screen into a flat stack.
Layer fitStructures arrange page framing around reusable tasks. They should create order without taking over the whole surface contract.
Primitives
Import and usage
The structure should stay easy to consume from the published package: one import, one usage shape, and no page-local wrapper assumptions.
Consumer contract
Import onceConsumers should get the structure from the published package without extra page-local wrappers.