Brand system
Editorial technical, built for trust-heavy software.
This system is designed for enterprise buyers, public sector teams, and technical operators who need calm structure, reliable signals, and modern product clarity.
Base
Stone neutrals
Action
Slate indigo
Signal
Coral accent
Personality
Editorial restraint
Use headlines and spacing to create authority, not hype or ornament.
Operational trust
Panels, borders, and hierarchy should feel controlled enough for procurement and review.
Modern product clarity
Interfaces stay contemporary through precision and simplicity, not trend-driven effects.
Technical confidence
The system should feel native to software teams without becoming cold or dense.
Avoid
Generic AI gradients and speculative futurism
Eyebrow-like decorative curves or ornamental swooshes
Added tracking that makes labels feel forced
Over-luxury styling that weakens product seriousness
Color system
Stone canvas
Main background
Mineral surface
Cards and raised panels
Graphite ink
Primary reading color
Slate indigo
Actions and active emphasis
Coral accent
Signals, highlights, warm emphasis (#E56343)
Structural border
Quiet layout definition
Typography
Display
Instrument Serif
Interface
DM Sans for navigation, product language, forms, and dense reading.
Section heading
Serif appears for hierarchy, not for every heading.
Controls
Surfaces
Default panel
Quiet structure first
Use soft borders, warm backgrounds, and readable spacing before adding any signal color.
Accent state
Accent only where intention matters
Primary and accent should guide action, status, and attention, not fill empty space.
Alerts
Info
System status and neutral guidance should stay readable and low drama.
Success
Use semantic color sparingly and keep the copy calm.
Warning
Flag review needs without turning the interface alarmist.
Navigation sample
MinervaProduct block
Operational summary
Private document workflows with traceable outputs.
Sources
24
Traceability
100%
Latency
<2s
Review state
Empty state
No knowledge base connected yet.
Keep the message direct. Explain the missing state, what the next action is, and why the workflow remains controlled.