The Caldura
brand, in one place

Everything you need to represent Caldura correctly — download the logos and social images, make yourself a business card, and check the colors and type. HEAT is the name of Caldura's brand system; it covers the parent company and both operating brands, Capital and AI.

I want to…

Get a logo↓ Make a business card→ Check colors & fonts↓ Browse all assets↗

HEAT v4 is Caldura's current brand system, and still being finalized. The adopted looks for Caldura, Caldura Capital, and Caldura AI are settled — but some details are still being tuned. For anything printed or high-visibility, it's worth a quick check with the brand owner before it ships.

The three brands

Caldura is one company with two operating brands. Each has its own look.

Whatever you're making belongs to one of these three. It's never a mix — a page, deck, or card is Caldura, or Capital, or AI. That choice sets the background, the accent color, and which mark you use.

Parent · the group

Caldura

Where: caldura.com — the hub
Ground: warm cream
Accent: old-gold bronze
Mark: the parent ring

Operating brand

Caldura Capital

Where: the investment arm
Ground: paper-white
Accent: deep navy
Mark: Horizon

Operating brand

Caldura AI

Where: the AI platform
Ground: warm-black
Accent: amber
Mark: Bloom (it animates)

Logos & assets

Ready-made files for each brand. Use them as-is — don't recreate them.

Each brand has a finished asset pack — the logo, the standalone mark, favicons for browser tabs, and social-preview images for link shares. The easiest way to see and grab them is the asset browser:

↗ Browse & download every assetlogos · marks · favicons · social images

Which file for what

You need…	Use
A logo for a site header, footer, or slide	Lockup — the mark + "Caldura" name, in a light or dark version to match your background
Just the icon (tight spaces, app tile)	Mark — the ring / Horizon / Bloom on its own
The browser-tab icon	Favicon set — the shared Caldura “C”
A nice preview when a link is shared	Social image (1200×630) for Slack, iMessage, LinkedIn

Always pick the version — light or dark — that suits your background, and give the logo a bit of breathing room. The files already include clear space around the mark, so you don't need to add your own. If a file looks wrong, don't fix it yourself — flag it to the brand owner so it's corrected at the source and everyone gets the fix.

Make a business card

A self-serve maker — fill in your details, download, order.

You don't design a card from scratch. The card maker is the approved Caldura design, ready to print — you just add your name and contact details:

→ Open the card makertype your details · download · order at MOO

Fill in your details — name, role, phone, email. The card updates live as you type; the Caldura name, tagline, and web address are already set.
Give it a glance — the on/off “guides” show the trim and safe lines, so you can confirm nothing important sits too close to the edge.
Download both sides — the Front and Back buttons save print-ready images at the right size and resolution.
Order at MOO — follow the ordering checklist shown on the page (Standard size, square corners, uncoated/matte paper, no extra finishes). Start with the smallest pack to check the color on real card first.

Order a small batch first. The maker exports on-screen images, and the bronze gold can shift slightly when a printer converts colors. A small first order lets you confirm it looks right on real stock before printing a full run. The print-perfect (CMYK) version is still being finalized — for a large or important run, check with the brand owner first.

Colors & type

The core palette and typefaces. Exact values are in the developer section.

Accent colors

Each brand leads with one accent color, on its own background:

Caldura bronze

#765B12

Capital navy

#1B365D

AI amber

#E8A24C

Backgrounds & ink

Warm cream

#EAE2D6

Paper-white

#F8F6F0

Warm-black

#1A1210

Muted text

#6B5D52

Type

Source Serif 4 — headlines and the Caldura name. Warm, editorial, distinctly Caldura.
Inter — body text, labels, and interface copy.
JetBrains Mono — small technical labels and code.

In the “Caldura Capital” and “Caldura AI” lockups, “Caldura” is set a touch heavier than the brand name after it, so the family name leads and the arm reads as a lighter qualifier. If you're working in code, the exact color values and font tokens are in the developer section and TOKENS.md.

Using the logo

A short list that keeps everything on-brand.

Do

Use the official files from the asset browser.
Pick the light or dark version that suits your background.
Leave clear space around the logo (it's built in — don't crowd it).
Match the brand to the context — Capital work uses the Capital mark, AI work uses AI.

Don't

Recolor, restyle, or redraw the mark — no gradients, shadows, or new colors.
Stretch or squash it — keep the proportions.
Place it on a busy background or one that clashes with its color.
Rebuild the logo by hand when an official file exists.
Mix two brands' marks or colors in one piece.

For developers

Building a website or app on the Caldura brand? Everything below is the technical contract — how to load the styles, the class names, and where the exact tokens live. The full inventory of source files is in the artifact viewer; deep references are TOKENS.md and COMPONENTS.md.

Names are stable; values may still move. HEAT v4 is a design-review baseline — token names are committed, but values can change until one Capital variant fully commits. Production today is still systems/v3.1/. Build against v4 for the adopted brands, but pin a synced snapshot rather than assuming values are frozen. HEAT is the source of truth; downstream apps consume a synced copy and never edit it in place.

Add HEAT to a site

Load foundation → components → variant, then set one wrapper class.

Get the bundle by running the sync from the HEAT repo root — it copies systems/v4/ into the sites app:

# from the heat repo root
node scripts/sync-v4-brand-viewer-to-sites.mjs
# → ../sites/public/brand-system/v4/   (public entry: /brand-system/v4/using-heat.html)

Load the CSS in dependency order — fonts, the :root foundation, the shared component layers, then your brand's tokens.css last (it shadows the resolved tokens for its wrapper scope):

<link rel="stylesheet" href="/brand-system/v4/assets/shared/fonts/brand-fonts.css">
<link rel="stylesheet" href="/brand-system/v4/code/shared/tokens-foundation.css">
<link rel="stylesheet" href="/brand-system/v4/code/shared/tokens-deck.css">
<link rel="stylesheet" href="/brand-system/v4/code/shared/deck-components.css">
<link rel="stylesheet" href="/brand-system/v4/code/shared/section-motifs.css">
<link rel="stylesheet" href="/brand-system/v4/code/shared/paper-texture.css">
<link rel="stylesheet" href="/brand-system/v4/code/shared/entrance.css">
<link rel="stylesheet" href="/brand-system/v4/code/shared/sr-only.css">
<!-- your brand's tokens LAST -->
<link rel="stylesheet" href="/brand-system/v4/code/group/variant-parent/tokens.css">

Then set the wrapper class on <body>, and optionally force light/dark on <html>:

<html data-color-scheme="dark">   <!-- or "light"; omit for the brand default -->
  <body class="caldura-group variant-parent"> … </body>
</html>

Brand	Wrapper class
Caldura (parent)	`caldura-group variant-parent`
Caldura Capital	`caldura-capital variant-blue-institutional`
Caldura AI	`caldura-ai variant-amber`

How the sites app actually consumes it. The Next.js app doesn't <link> these at runtime — it adapts the token blocks into src/app/globals.css, each with a /* Source: heat/systems/v4/… */ comment so the next sync can be reconciled. Either way, HEAT stays the source; don't silently fork the values.

Components & tokens

Apply a class, get brand-correct styling. Read color/type from tokens.

Apply a system class to the right element and its brand styling resolves automatically. The everyday ones (full list in COMPONENTS.md):

Class	What it is
`.cta-primary`	primary button — reads `--cta-bg`/`--cta-text` (you own padding/radius/size)
`.cta-secondary`	text-link secondary action, reads `--accent`
`.parent-link`	the cross-reference back to caldura.com on any brand surface
`.section-motif`	section boundary (Horizon echo for Capital, thermal bars for AI)
`.section-label`	eyebrow/section label — Capital themes it all-caps + 0.15em tracking. Use this instead of ad-hoc `uppercase tracking-widest` utilities.
`.deck-*`	deck kit — `chevron`, `deck-table`, `matrix`, `deck-kpi`, `deck-bullets`, `deck-badge`, `deck-section`

All color and type comes through tokens so mode and brand resolve correctly and contrast holds — never hardcode a brand hex. The ones you'll reach for most: --bg-base, --text-primary, --accent, and the AAA-tested --cta-bg/--cta-text pair. Full surface in TOKENS.md. Page layout, nav chrome, forms, and modals are yours — don't back-port them into the system.

Favicons & social in code

These are build-time — pin one brand statically.

Favicons and social images are emitted server-side (Next.js generateMetadata runs at SSR), while the active brand on an interactive page can be client state — a mismatch. Pin the surface's brand statically for metadata: a page's favicon and social image should reflect the one brand it actually is, not a runtime-swapped variant. Reserve runtime switching for live preview only.

The tab favicon is the shared Caldura “C”, not the brand ring. Per ADR-0007, at 16–12px the C stays a legible letterform while a ring collapses to a generic dot — so the C is the shared family favicon across all three sites. The brand ring/mark ships to logo, lockup, and social image only.

Preview variants

A dev affordance for reviewing brands live on one page.

During a review it helps to flip brands live without a rebuild. A magic-key cycler writes the active variant to localStorage, swaps the wrapper class on <html>, and a pre-paint script restores it on reload (no flash). Keep this out of production builds.

// pre-paint restore (head, before first paint)
<script>
  var v = localStorage.getItem('caldura-variant');
  if (v) document.documentElement.className = v;
</script>

// Shift+V cycles the adopted brands
const VARIANTS = [
  'caldura-group variant-parent',
  'caldura-capital variant-blue-institutional',
  'caldura-ai variant-amber',
];

HEAT · the Caldura brand system · v4. Source of truth: heat/systems/v4/. Published to the sites app at /brand-system/v4/using-heat.html. Underlying source inventory: artifact viewer. How v4 was chosen: design cycles.