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 ยท Surface Recipes ยท Rottay / modernShared route metadata for the active runtime, kept inline so the shell reads like a thin header band.
Palette
#0A0A0ARottay
Chrome
Modernrenderer posture
Radius
14pxsurface shape
Density
normalPlatform Flagship
Surfaces
Surfaces
Surfaces
Active profilePlatform Flagship
Runtime postureRottay / modern
Full-page showcases demonstrating how the system behaves in realistic workflows.
Runtime controls
36 surfaces
6 domains
Surfaces
Full-page contracts that compose structures and patterns while the application supplies data, routing, permissions, and policy.
Config-first
Page-level
Reusable recipes
Contract reading
The DS should own composition and defaults while the application keeps the data, routes, and policy visible through config.
Domains6
Engines3
Contract styleConfig-first
ScopeFull page
Escalation cue
Reach for a surface after primitives, patterns, and structures have already answered the smaller questions and the page still needs a consistent shell.
Read the Surface Contract
Tighten the boundary first, then browse a domain recipe with the right expectations.
Declarative first
Usage Contract
Config-first
Surfaces work best when the config reads like the screen you want to ship.
Declarative usagePaste-ready example that shows the base contract first.
tsx
13 lines
Consumption
Runtime-aware snippet
Browse Domains
Pick the kind of product screen you need, then jump into a surface recipe.
Highest DS layer
Each domain card separates the screen promise, best-fit scenarios, and starter recipes so the overview reads like a routing shelf instead of a wall of copy.