Cloud Operations — Brand Guidelines

Ops Suite

Laniakea Nornforge Ocularium

A unified visual language for cloud operations infrastructure — precise, legible, and built for low-light terminal environments.

01 — Applications

The Suite

Three tools, one coherent identity. Each application has a distinct accent color and personality rooted in its name's mythology, but all share the same foundational palette and typographic system.

L⊛
Laniakea
Hub · Resource Registry
The central hub for cloud resource management. All roads lead here — service inventory, IAM, cross-project views, and infrastructure state live under Laniakea's gravity.
Hawaiian: "immeasurable heaven." The galactic supercluster containing the Milky Way, spanning 500 million light-years.
N⚒
Nornforge
Command · Terminal VM
The command and execution environment. A persistent terminal VM for shell access, automation runs, and ephemeral ops work — where things get made and unmade.
Norse: the Norns (fate-weavers) + forge. The three Norns carved runes into Yggdrasil; Nornforge is where commands are carved into infrastructure.
O◎
Ocularium
Observe · Monitoring & Ops
The all-seeing operations layer. Hosts Grafana dashboards, alerting pipelines, log aggregation, and scheduled ops jobs. If something is wrong, Ocularium knows first.
Latin: oculus (eye) + -arium (place of). An observatory for infrastructure — an instrument for seeing what cannot otherwise be seen.

02 — Color

Palette

The suite shares a single dark void foundation. Each application is differentiated by a single accent color chosen for its symbolic resonance: steel blue for the vastness of space, ember orange for forge-fire, phosphor green for instrument readouts.

Shared Foundation

Void
#080a0f — page background
Void 2
#0d1018 — section fill
Surface
#1a1f2e — card/panel background
Rim
rgba(255,255,255,0.07) — default borders
Text Primary
#dde3f0 — primary text
Text Muted
#7a8499 — body, secondary

Per-Application Accents

Laniakea
Hub · Galactic Blue
core
mid
dim
accent
bright
Stellar Blue
Primary accent — interactive elements, active states, links
#4d9de0
Stellar Bright
High-emphasis text on dark accent surfaces
#a8d4f5
Stellar Glow
Button fills, badge backgrounds, hover surfaces
rgba(77,157,224,0.15)
Nornforge
Terminal · Ember Orange
core
mid
dim
accent
bright
Forge Ember
Primary accent — prompt color, active indicators
#e07b1a
Forge Bright
High-emphasis text, command output highlights
#f0c87a
Forge Glow
Button fills, active surface backgrounds
rgba(224,123,26,0.15)
Ocularium
Observe · Phosphor Green
core
mid
dim
accent
bright
Phosphor Green
Primary accent — metric values, healthy-state indicators
#1ad98a
Phosphor Bright
High-emphasis data labels on dark surfaces
#7afad0
Phosphor Glow
Badge backgrounds, panel highlights, hover fills
rgba(26,217,138,0.12)

Semantic / Status Colors

These are shared across all three applications for uniform operational status communication.

Healthy / OK
#1ad98a accent
Warning
#e0c01a accent
Error / Alert
#e04040 accent
Unknown / Idle
var(--text-dim)

03 — Typography

Type System

Two typefaces cover the entire system. Archivo Black for headings and display — a condensed grotesque with industrial authority and no apologies. Archivo (regular weights) for body prose and descriptions, keeping the type family coherent. Fira Code for all monospace contexts: terminal output, metric values, hex codes, and command syntax. Space Mono fills in for small-caps labels and eyebrow text where a wider, more open monospace reads better at tiny sizes.

Display / Headings Archivo Black — weight 900 (single weight)
Laniakea
Nornforge
Ocularium
Archivo — body weight for descriptions, prose, and card content. Sits cleanly under Archivo Black headings without the tonal break a different family would introduce.
Monospace — data, terminal, code Fira Code — weights 300, 400, 500
$ terraform plan -out=ops.tfplan
Plan: 3 to add, 1 to change, 0 to destroy.
99.98% uptime_7d
0.42ms p50_latency
Labels / Eyebrows / Badges Space Mono — weight 400, letter-spacing 0.2–0.35em, uppercase
cloud operations · brand guidelines
hub · resource registry
terminal · nornforge vm
observe · ocularium monitoring
Token Size Weight Family Context
--ts-heroclamp(2.5rem, 7vw, 6rem)900Archivo BlackHero / page title
--ts-section1.75rem900Archivo BlackSection headings
--ts-card-title1.2rem900Archivo BlackCard / panel headings
--ts-body0.95rem400–600ArchivoProse, descriptions, card body text
--ts-label0.60rem400Space MonoEyebrows, section labels; letter-spacing 0.25–0.35em; uppercase
--ts-badge0.58rem400Space MonoStatus badges; letter-spacing 0.15em; uppercase
--ts-mono-data1.1–1.35rem400–500Fira CodeMetric values, primary data display
--ts-mono-body0.7–0.8rem400Fira CodeTerminal output, hex codes, log lines

04 — UI Language

Components

Shared component vocabulary across the suite. App-specific accent colors slot in; structure and interaction patterns are identical.

Application UI Feel

laniakea — service registry
nornforge-vm running
ocularium-grafana running
jiggler-cloud-run degraded
staging-env stopped
nornforge — terminal session
jtr@nornforge:~$ cd /opt/rubicon
jtr@nornforge:rubicon$ go build ./...
ok github.com/jjttrr/rubicon/famtree
jtr@nornforge:rubicon$ ./famtree render reese
rendered 4 generations → reese.svg
ocularium — readouts
Uptime 7d
99.98%
p50 latency
0.42ms
Alerts 24h
3
Services
12
Healthy Degraded Error Stopped
Laniakea Nornforge Ocularium
$ terraform apply ops.tfplan laniakea_service_account: creating... nornforge_vm_instance: creating... Apply complete. 3 added, 0 destroyed.
CPU
12%
nornforge-vm
Memory
3.2G
of 8G
Alerts
3
last 24h

Nornforge — Button Risk Hierarchy

Ember is earned. Ghost buttons handle low-risk reads; ember signals intent; red signals consequence. Destructive actions are spatially separated — never adjacent to safe ones — so a fatigued operator can't fat-finger them. The gap is not decorative.

Low risk
ghost
Read-only or reversible. No ember — ember is for actions that change state.
Standard
btn-n-primary
State-changing but recoverable. Ember glow signals intent. At most one per action cluster.
Destructive
btn-danger
Red regardless of app context — semantic color overrides accent. Gated by confirmation where consequence is irreversible.
Example: VM control panel
nornforge-vm-prod Running

05 — Principles

Design Character

The ops suite is instrumentation, not marketing. Every decision should read as trustworthy, precise, and calm. These principles govern how the visual language evolves.

01
The void is the canvas
Near-black backgrounds are not a stylistic preference — they reduce fatigue in terminal-adjacent environments and make accent colors sing. Never introduce light surfaces except for print contexts.
02
One accent per domain
Each application speaks in exactly one accent color. Mixing accents within a single app (e.g., using Ocularium green inside a Laniakea UI) implies integration, not decoration. Reserve cross-app colors for actual integration points.
03
Data in monospace, identity in display
All operational data — metrics, logs, command output, identifiers, hexes — renders in Fira Code. Archivo Black and Archivo carry naming, headings, and prose. These roles never swap.
04
Status is always unambiguous
Green = healthy. Yellow = degraded/warning. Red = error/alert. Gray = idle/unknown. These semantic colors are not accent colors; they override app accents wherever operational status is communicated.
05
Structure through restraint
Borders are at 7% white alpha by default. Don't introduce new visual weight to solve layout problems — solve them with spacing instead. If something needs a stronger border to be legible, that's a layout problem, not a border problem.
06
Identity earns its place
App-specific glyphs (L⊛, N⚒, O◎) and color cues are wayfinding aids, not decoration. In dense ops UIs where multiple apps may be integrated, they prevent disorientation. Don't use them for visual interest alone.