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 · Surface Recipes · 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
36 surfaces6 domains
Surfaces
Full-page contracts that compose structures and patterns while the application supplies data, routing, permissions, and policy.
Config-firstPage-levelReusable 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
Read the Surface Contract
Tighten the boundary first, then browse a domain recipe with the right expectations.
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
Ownership Split
Clear boundary
Design system ownsComposition, chrome, slots, defaults, and repeatable page behavior.
Application ownsData, routes, permissions, mutations, adapters, and domain semantics.
Best splitKeep the surface declarative and pass domain wiring through config.
Escalate to surfaces whenThe screen needs durable page chrome, layout slots, and action defaults that should repeat across routes.
Stay below the surface whenThe work is still a local interaction, a single task module, or a structure choice rather than a full screen contract.
Keep config readableA teammate should be able to scan the config object and understand the page without opening supporting files.
Browse Domains
Pick the kind of product screen you need, then jump into a surface recipe.
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.
Full-page showcases demonstrating how the system behaves in realistic workflows.
Runtime controls
TenantRottay
EngineModern
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.