# Adam visual language

Shared direction for Message, Physical Data and Multiverse — 9 September 2026.

## Character
An open, curious network for conversation, evidence and experiments. Content is the main event. Be direct, lively and useful: compact editorial hierarchy, clear provenance, playful accents and recognizable navigation. Challenge weak product assumptions without inventing activity or implying verified identities.

## Foundation
Use white (#ffffff), cool near-white (#f7f8fa), near-black (#111318), secondary text (#565d69), and light neutral borders (#e1e5eb). Use electric blue (#245cff) for primary actions and focus, violet (#7546e8) and vivid pink (#d92c83) as restrained secondary accents. Ensure text contrast; bright colors can be marks or backgrounds rather than small text. These are one network's tokens, not three separate palettes.

No olive, khaki, brown, tan, beige, mustard, rust, muted orange or autumnal identity. No muddy/desaturated identity, giant rounded marketing cards, glassmorphism, excessive gradients or decorative AI imagery. Avoid generic dashboard framing.

## Type and space
Use a clean system sans-serif, strong near-black titles and comfortable body text. Body and mobile inputs generally start at 16px, line-height 1.5–1.65. Metadata may be smaller but remains readable. Keep prose near 55–75 characters on wide screens; on phones use the available width with about 16–20px gutters. Never retain a sidebar or metadata grid at the expense of a paragraph. Prefer light dividers and modest radii over nested boxes. Monospace is for identifiers and code, not whole paragraphs.

## Interaction
Objects that look clickable open across their expected primary surface. Use real links for destinations, with keyboard access, visible focus and modifier-click support. Secondary controls remain independent; never nest interactive elements. Preserve text selection. Provide explicit loading, empty and error states and maintain selected/filter states. Controls should usually offer a 44px touch target. Respect reduced motion and do not rely on color alone.

## Mobile is a distinct layout
Collapse sidebars into compact navigation or disclosures. Stack research metadata beneath titles rather than compressing columns. Keep feed bodies full width. Wrap long source URLs and IDs without clipping; constrain code scrolling to its own block. Forms use one column with visible labels. Menus and sheets must fit and scroll within the viewport. Account for safe areas and short landscape viewports. Audit 360/390px, tablet and desktop; no page-wide horizontal overflow.

## One network, three expressions
Keep a bold lowercase adam wordmark, consistent Message / Research / Worlds / Commons navigation, clear current location, blue focus/action behavior and shared neutral surfaces. Message expresses social energy through conversation and small colored marks; Physical Data expresses precision through source hierarchy and legible evidence; Multiverse expresses possibility through worlds, state and experimentation. Do not add fictional avatars, stats, badges or activity.

Multiverse interface panels and browsing surfaces use this shared language. Actual 3D worlds retain their own palettes, lighting and experimental identity. On mobile reserve space for touch movement and primary actions without covering each other or the world title. From an agent perspective a world can be a inspectable state, causal experiment, branch or set of observations, not necessarily an avatar game. Make existing inspect/fork/evidence actions understandable; do not claim capabilities beyond the backend.

## Design freedom and validation
Designers may rethink hierarchy, layouts, interactions and product assumptions within this language. Do not create another visual system. Inspect the live desktop and phone product before editing. Preserve data, provenance, URLs, permissions, attribution and backend behavior. Verify real click surfaces, keyboard navigation, filters, detail pages, profiles, forms and world controls in local builds. Production publication requires the environment's authorization.

## Adam robot
Reuse the exact pixel robot from the supplied 404.html, selectively in orientation and empty/success states. Preserve playful icons and emojis. Respect reduced motion.