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 · Pattern Library · Rottay / modernShared route metadata for the active runtime, kept inline so the shell reads like a thin header band.
Communication patterns should show information freshness, authorship, and actionability in the same frame.
How to read this pageUse the showroom switchers in the sidebar to change engine and tenant. The comparison grid below keeps the active tenant and swaps engines so we can inspect the pattern instead of page-local editorial chrome.
Live preview
Compare the same pattern across engines
Sidebar tenant drives thisAssistant
This comparison is the documentation surface. If the pattern only reads well inside local chrome, we should fix the pattern or its preview runtime before teams style around it.
Preview heuristics
3 items
Compare density, action placement, and state readability before aesthetic flavor.
Judge the pattern itself, not any showroom-local framing around it.
If the pattern only works with extra chrome, the pattern or preview runtime still needs work.
Structure pairing
3 items
Consumption
Import and usage
Treat the pattern as a reusable task contract. Keep route-specific business rules outside and use these snippets as the fast-reading baseline.
Consumption contract
Usage notes
3 items
Import from the published package rather than building route-local wrappers first.
Pass data, config, and callbacks while keeping product semantics in the consuming app.
Escalate to a surface only once the whole screen contract is stable, not just the task module.
Surface fit
3 items
ChatSurface
API surface
Props
6 rows
Assistant propsProp contracts stay readable across dark-first and light-first tenants.
6 props1 required5 optional
Fast readStart with required props, then scan defaults before dropping to per-row details.
Contract postureThis reference stays intentionally concise so the primitive contract remains scannable.
TierPatternReusable workflow or composition contract.
GroupCommunicationStart with message hierarchy.
Best paired withDetailHeaderUsually lands inside ChatSurface.
DetailHeader
WorkbenchHeader
PageShell
Engine comparisonEngine comparisonThe active tenant stays real while the same component is rendered by every engine. The wrapper stays intentionally quiet so engine differences come from the DS itself.
Rottay3 live enginesSame tenant, isolated engine
ClassicAnt Design
Live provider
What to evaluate
3 items
message hierarchy
presence cues
response affordances
Structure pairing
3 items
DetailHeader
WorkbenchHeader
PageShell
Surface fit
3 items
ChatSurface
ActivitySurface
NotificationSurface
ActivitySurface
NotificationSurface
ImportPublished package entrypoint, ready to copy.
tsx
1 line
Consumption
Runtime-aware snippet
import { Assistant } from '@rottay/design-system';
UsagePaste-ready example that shows the base contract first.