Brand guide · v2
An identity built like the product: restrained, provable, alive.
HyperMindZ is the transaction infrastructure for agentic advertising — and the brand behaves like infrastructure. Editorial serif for beliefs, mono for facts, one saturated blue reserved for active transactions, and artwork that depicts the thesis instead of decorating it. This guide supersedes v1 (the indigo/Inter system).
01 / Logo
The mark and the wordmark.
The hexagonal knot is the mark; the wordmark sets it beside the name. Black on light, white on dark, minimum height 32px, clear space equal to the mark's height on all sides. These 4x files are the only approved sources.
02 / Color
One blue that means something.
The interface is ink on paper. Ultramarine appears only where a transaction is active or an action is primary — so when the blue shows up, it means something happened.
The ground. Cool ice-white, never warm ivory.
Near-black navy. All headings and primary text.
The brand blue — reserved for active transactions, primary actions, and one line per artwork.
Machine accents on dark surfaces only — it fails contrast on light. Never AI-purple.
Only for what is checked, verified, signed, or free — as dots and fills. Verify-colored TEXT uses the AA tints: --verify-text (#067A5A) on light, --verify-soft (#35D3A5) on dark.
The sell amber, deepened to AA for small text on light; strokes and fills stay --amber-line (#DD9526).
Dark bands carry machine truth: live data, terminals, records.
03 / Typography
Serif for beliefs. Sans for explanation. Mono for facts.
headlines · theses · figure captions — weight 400, letter-spacing −0.02em to −0.026em
paragraphs · UI · navigation
kickers (11px · 0.22em tracking · uppercase) · counts · endpoints · deal IDs · system labels
04 / Artwork
Art that depicts the thesis, never decorates it.
Two families, both vector, both figure-numbered like a systems paper. Ink flow-fields show the mechanism; colorful flat geometry shows the community. In every piece, exactly one ultramarine line completes — the transaction.
Fig. 01 — the crossing · ink flow-field · one line completes
Fig. 02 — the network · flat geometry in the art palette · one line threads all
The tile family marks the four sides of the transaction — BUY, SELL, DATA, CONNECT. Flat overlapping geometry, one color world each, never used as icons inside interface controls.
05 / Voice
How HyperMindZ speaks.
Newsreader carries every claim we stand behind — headlines, theses, the sentences competitors can't say.
Inter carries the body: how things work, in complete sentences.
JetBrains Mono carries every literal fact — counts, endpoints, floors, deal IDs. If it's checkable, it's mono.
Each section earns exactly one belief. Demonstrate, never assert — every claim gets a mechanism or artifact in the same viewport.
Present tense descriptions of how the market works — never predictions. "Buyer agents don't browse. They query."
No registry entry, demo tenant, or prospect appears as a customer. Sample agents are descriptive, on .example domains.
The transaction infrastructure for agentic advertising — the neutral network, running on the Deal Plane, connecting every AI buyer with every AI seller. Routing is the verb of the mechanism; orchestration belongs only to BuyerAgentZ.
06 / Never
The rules that keep it ours.
Questions about usage, co-marketing, or press assets: contact us →
Writing should()
The developer brand under HyperMindZ. A common word made ownable by two characters of punctuation — so the typography rules are the brand.
lowercase, with the parentheses, in JetBrains Mono: should(). The punctuation is the logo.
“Should” capitalized, bare “should” as a name, or inflected forms (“shoulding”, “shoulds”). Write “a should() judgment”.
the Judgment Record — capitalized, two words. It is the ownable phrase; prefer it in headlines and search-facing copy.
“Powered by Jev” is the endorsement lockup — swappable by design; should() stays the senior brand in the pair.
judgment ids render in mono as name:version (deal-fit:v3) wherever they appear.