Runtime fingerprintToken readout from the active provider chain.
Live DS
Runtime
Platform
Rottay
Rottay / ModernPlatform Flagship
Primary
#0A0A0ASecondary #6B6B6B
Radius
14pxxl 18px
Density
normalBorder-light cards
Accent
Badge
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.
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 01context signalShould be obvious on the first scan without relying on surface chrome for rescue.
Review 02primary action emphasisShould stay clear once actions, counts, and support context compete for attention.
Review 03space efficiencyShould keep dense content readable instead of turning the screen into a flat stack.
Common pairings
stats grids
detail panels
commands
Usually lands in
DashboardSurface
ListSurface
DetailSurface
Live preview
Compare rhythm, action placement, and supporting context across engines while the active tenant remains real.
classic
modern
rustic
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 comparisonDetail Header render checkEach engine gets the same structure with the same tenant. Focus on spacing, hierarchy, and action cadence rather than wrapper chrome.
Rottay
3 live engines
Same tenant, isolated engine
ClassicAnt Design
Live provider
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 01context signalShould be obvious on the first scan without relying on surface chrome for rescue.
Check 02primary action emphasisShould stay clear once actions, counts, and support context compete for attention.
Check 03space efficiencyShould 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
Patterns
Structures
Surfaces
Stay here whenThe missing piece is section rhythm, chrome placement, or page-level context.
Escalate whenYou need reusable workflow behavior or a full route shell beyond the framing.
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.