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 · Tenant Showcase · 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
Evnto
Operations
Operations
Active profilePlatform Flagship
Runtime postureRottay / modern
Event-product flows showing how the system flexes for experience-heavy UIs.
Runtime controls
TenantRottay
Back to Evnto
Operations
3 scenario rows
Tier mix 1P / 0S / 14Pr
Scenario summary
Operations in Evnto balances premium presentation with live-event clarity.
Operations pages take Evnto from beautiful planning tool to reliable live-event system. They prioritize clarity, checklistability, and team coordination. These scenarios stay Evnto-specific in workflow and copy, but the live visuals should still come from the active docs runtime instead of a local preset.
Scenario rows3Named modules that anchor this category's product story.
Unique parts10Distinct structures, patterns, and primitives in this category.
Dominant archetypeOperational indexThe prevailing interaction shape across these modules.
Operators
Ops leads
Producers
Vendor coordinators
The category has to stay legible for these roles even when a different tenant runtime shifts density or contrast.
Tempo and pressure
Time-sensitive execution
Use the scenario rows below to verify that hierarchy and control placement still hold up at this pace.
Design principles
3 guardrails
Principle 01Surface blockers early.
Principle 02Keep task ownership explicit.
Principle 03Use timeline context to reduce stress during showtime.
Scenario rows
Scenario modules
Each row below captures a product-grade module, the component spread behind it, and what to scrutinize when the runtime changes.
Read orderStart with the title and archetype, then inspect composition balance and the part sample.
Proof checkConfirm the lane still reads like one product module after the runtime changes tone, density, and contrast.
01
Scenario module
Ops Checklist
Day-of operations checklist with assignment, status tracking, and dependencies.
Composition balancePrimitive-heavy assemblyA quick read on which layer is carrying most of the scenario weight.
Tier mix0P / 0S / 5Pr
Inspect forCheck whether scanning rhythm, action placement, and row density still feel safe and fast.
02
Scenario module
Vendor Coordination
Vendor roster with contracts, delivery schedules, and communication log.
Composition balancePrimitive-heavy assemblyA quick read on which layer is carrying most of the scenario weight.
Tier mix1P / 0S / 4Pr
Inspect forCheck whether scanning rhythm, action placement, and row density still feel safe and fast.
03
Scenario module
Run of Show
Minute-by-minute event timeline with cue sheets and crew assignments.
Composition balancePrimitive-heavy assemblyA quick read on which layer is carrying most of the scenario weight.
Tier mix0P / 0S / 5Pr
Inspect forCheck whether sequence, progress cues, and handoff points remain easy to follow.
Use this page as a reference sheet: the scenario modules stay constant, while contrast, shell tone, and component personality respond to the active docs runtime.
Runtime
Platform
Rottay
Rottay / ModernPlatform Flagship
Primary
#0A0A0ASecondary #6B6B6B
Radius
14pxxl 18px
Density
normalBorder-light cards
Accent
Badge
Motion
Compact runtime evidence across 3+ token signals.
roundedtop bar · solid dividers
springHover lift 2px
Keep stableOperations still needs to feel native for Ops leads, Producers, and 1 more even while the provider changes the surrounding chrome.
Stress pointTime-sensitive execution means hierarchy, action placement, and contrast cannot become ambiguous under a different runtime.
Read as one laneOperational index should feel like one coherent chapter here rather than a stack of isolated component demos.