BRAND KIT

# Xenodia Brand Kit

## Brand Positioning
Xenodia is machine-native infrastructure for autonomous agents, not a consumer AI chat product.
The visual system and copy should consistently communicate:
- protocol-first
- operator-facing
- machine-native settlement
- unified routing and execution
- live system status

## Brand Character
- Keywords: precise, cold, systematic, executable, infrastructural
- Avoid: playful, cute, casual, generic SaaS, consumer-AI toy energy
- Design test: if a page feels closer to a control panel, protocol surface, or live operator console, it is closer to Xenodia

## Core Color Spec
- Background / `--bg`: #000000
- Surface / `--surface`: #0A0E1A
- Surface 2 / `--surface2`: #111827
- Accent / `--accent`: #CCFF00
- Accent Dim / `--accent-dim`: rgba(204, 255, 0, 0.10)
- Accent Dim MD / `--accent-dim-md`: rgba(204, 255, 0, 0.15)
- Border / `--border`: rgba(204, 255, 0, 0.40)
- Border Dim / `--border-dim`: rgba(255, 255, 255, 0.05)
- Danger / `--danger`: #FF0055
- Warning / `--warning`: #FF8C00
- Success / `--success`: #00FF88
- Text / `--text`: #E0E7FF
- Text Secondary / `--text2`: #94A3B8
- Text Tertiary / `--text3`: #475569

## Color Usage Rules
- Use #000000, #0A0E1A, and #111827 for large background fields
- Use acid-lime #CCFF00 only as a scarce high-signal accent for actions, labels, focus states, and status emphasis
- Do not turn the accent green into the dominant page background
- Bright contrast should support a system-status feeling, not decorative friendliness
- Red, orange, and green are semantic feedback colors, not replacements for the brand accent

## Typography Spec
- Display / `--font-display`: "Orbitron", sans-serif
- Mono / `--font-mono`: "Azeret Mono", monospace
- Body / `--font-body`: "Rajdhani", sans-serif
- Code / `--font-code`: "JetBrains Mono", "Azeret Mono", monospace

## Typography Rules
- Use Orbitron for primary headings with uppercase, compressed, directive energy
- Use Rajdhani for body copy to keep the interface readable but still technical
- Use Azeret Mono for labels, states, metrics, IDs, and meta information
- Use JetBrains Mono / Azeret Mono for code and technical snippets
- Avoid rounded, editorial, friendly-lifestyle, or playful type choices

## Icon Rules
- Current primary icon file: brand-icon.png
- Present the icon on black or near-black backgrounds
- Preserve breathing room around it
- Avoid busy textures, colorful gradients, skeuomorphic highlights, or aggressive glow
- Do not casually recolor the icon; keep its engineered, high-contrast feel intact

## Layout Rules
- Favor control-panel structures, framed modules, stable grids, and information rhythm
- Keep a stronger sense of alignment and density than a loose poster-style landing page
- Modules should feel like deployed interface surfaces rather than decorative marketing blocks
- Thin borders, dim metallic layers, and terminal-like labels are aligned with the brand

## Voice Rules
- Prefer words like infrastructure, routing, settlement, execution, protocol, system status, compute, and agent
- Avoid consumer-facing language such as fun, magic, delightful, playful, or creative companion
- Headlines should feel like system declarations or module names, not ad slogans

## Do
- Use black or near-black canvases for hero and icon presentation
- Keep acid-lime sparse and intentional
- Make the interface feel like a deployed operator system
- Use uppercase headings, mono metadata, and clear borders

## Avoid
- Do not turn it into a generic SaaS dashboard
- Do not use pastel palettes, bright gradients, or candy-like color systems
- Do not make the tone cute, casual, or social-first
- Do not let the icon dominate so much that the written specification disappears