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
BitHire
Ai Agents
Ai Agents
Active profilePlatform Flagship
Runtime postureRottay / modern
Recruiting-focused adaptations of the shared design system.
Runtime controls
TenantRottay
Back to BitHire
AI Agents
3 scenario rows
Tier mix 0P / 0S / 15Pr
Scenario summary
AI Agents in BitHire is built for speed, visibility, and decision support.
AI agent surfaces should feel like explainable copilots, not black boxes. They accelerate sourcing and screening while preserving human judgment. These scenarios stay BitHire-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 parts9Distinct structures, patterns, and primitives in this category.
Dominant archetypeAnalytics surfaceThe prevailing interaction shape across these modules.
Operators
Recruiters
Talent intelligence
Hiring leads
The category has to stay legible for these roles even when a different tenant runtime shifts density or contrast.
Tempo and pressure
Assistive and insight-driven
Use the scenario rows below to verify that hierarchy and control placement still hold up at this pace.
Design principles
3 guardrails
Principle 01Show rationale next to recommendations.
Principle 02Balance confidence scores with human override.
Principle 03Keep AI suggestions actionable, not abstract.
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
Sourcing Agent
AI agent dashboard showing search queries, matched candidates, and confidence scores.
Composition balancePrimitive-heavy assemblyA quick read on which layer is carrying most of the scenario weight.
Tier mix0P / 0S / 5Pr
Inspect forCheck whether chart emphasis, contrast, and labels stay legible under the active provider.
02
Scenario module
Resume Screener
Automated resume analysis with skill extraction, scoring, and recommendation rationale.
Composition balancePrimitive-heavy assemblyA quick read on which layer is carrying most of the scenario weight.
Tier mix0P / 0S / 5Pr
Inspect forCheck whether the module still feels product-grade rather than like an isolated component demo.
03
Scenario module
Match Engine
Candidate-to-role matching interface with similarity scores and skill gap analysis.
Composition balancePrimitive-heavy assemblyA quick read on which layer is carrying most of the scenario weight.
Tier mix0P / 0S / 5Pr
Inspect forCheck whether chart emphasis, contrast, and labels stay legible under the active provider.
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 stableAI Agents still needs to feel native for Recruiters, Talent intelligence, and 1 more even while the provider changes the surrounding chrome.
Stress pointAssistive and insight-driven means hierarchy, action placement, and contrast cannot become ambiguous under a different runtime.
Read as one laneAnalytics surface should feel like one coherent chapter here rather than a stack of isolated component demos.