Litmus Brand Pack v1
Brand identity · proposed direction

Two AIs.
One verdict
you can trust.

A complete brand system for an automated assurance platform — where OpenAI and Claude cross-check each other across contracts, databases, payment flows and cloud cost, so you ship with confidence.

Litmus
The test before the test.
Smart contracts Database testing Payment flows Cost optimization Security review
01

The name

You're outgrowing "SC Pre-Audit." Here's a name built for everything you're becoming.

Recommended
Litmus

Why it works. A litmus test is the quick, trusted check that tells you go or no-go before you commit — exactly what this product does. It's short, memorable, easy to say, and not tied to smart contracts, so it stretches cleanly across databases, payment flows and cost.

It also pairs perfectly with your traffic-light verdict system — a litmus strip changes colour to give a clear reading, just like Ready / Caution / Stop. (Run a quick trademark + domain check — e.g. litmus.dev / getlitmus.com / litmusaudit.com.)

Shortlist — alternatives explored
Crux
The crucial point — and Latin for "cross." Shorter, more ownable, more abstract.
Find the crux before you ship
Preflight
The pre-launch checklist metaphor. Broad across the stack, friendly, instantly understood.
Your pre-launch checklist
Auspex
The Roman official who inspected the signs before any major decision. Premium, distinctive.
Read the signs first
Crosscheck
Says the dual-AI method out loud. The most literal description of what you do.
Audited twice, trusted once
03

Color

A serious ink base, one electric brand blue, and a signal system that powers every verdict.

Brand — electric indigo
brand-700#1B33C7
brand-600#2747E6
brand-500#3B5BFF
brand-300#9DB0FF
brand-100#E7ECFF
brand-50#F2F5FF
Ink — neutrals
ink-900#0A0E16
ink-700#1C2433
ink-500#4A5468
ink-300#9AA2B2
ink-100#E7EBF1
ink-50#F4F6FA
Signal — the verdict system
pass · Ready#08C076
caution · Testnet#F5A623
critical · Not ready#F0453B
Usage balance
62% Paper / Ink
28% Brand
10% Signal

Keep surfaces calm and neutral. Brand blue carries actions and identity; signal colors are reserved for verdicts and severity — never decoration. Scarcity is what makes a red finding feel urgent.

Dark surfaces (app / terminal)

The app and report viewer run on ink-900 for a focused, developer-tool feel. Brand-300 and signal colors stay vivid against the dark base.

Pass Caution Critical
04

Typography

Confident display, neutral body, and a mono voice for everything technical.

Aa
Space Grotesk
Display & headlines · 600–700
Aa
Hanken Grotesk
Body, UI & long-form · 400–700
Aa
JetBrains Mono
Code, labels, scores, verdicts
Display
Space Grotesk 700 · 64/0.98 · -3.5%
Ship with confidence
Heading
Space Grotesk 600 · 30/1.1 · -2%
Multi-engine cross-audit
Body
Hanken Grotesk 400 · 17/1.55
Two independent AI engines review your code, then reconcile their findings. You only see issues that survive a second opinion — fewer false positives, more signal.
Mono / label
JetBrains Mono 500 · tracked +12%
SEVERITY: HIGH · CWE-841 · reentrancy_guard_missing
05

The verdict system

Your signature asset. The go / caution / stop language carries across every service you offer.

Ready
Cleared for beta / testnet. No critical or high findings unresolved.
Testnet only
Proceed with caution. Medium-risk findings to address before mainnet.
Not ready
Hold. Critical issues that must be fixed before any deployment.
81
Security score
Scoring

Transparent 0–100 score with an explainable formula. The ring fills with the verdict color so the number and the recommendation always agree at a glance.

Severity scale
Critical High Medium Low Info

Reentrancy in withdraw()

External call precedes state update, enabling a recursive drain. Apply checks-effects-interactions or a nonReentrant guard. Confirmed by both engines.

06

Core components & iconography

The building blocks — buttons, chips, and a clean 2px line-icon set.

Buttons
Icon system — 2px stroke, round joins
contracts
database
payments
cost
security
verdict
07

Voice & tone

Direct, technical, honest about limits. We're the trusted second opinion — not the hype.

Do

  • Be specific and actionable — name the function, the line, the fix.
  • Be honest about scope: "a second opinion before your formal audit," never "a replacement for one."
  • Lead with the verdict, then the evidence.
  • Speak developer-to-developer. Precise, calm, no fear-mongering.

Don't

  • Overpromise "100% secure" or "audit-grade certainty."
  • Bury the lede in marketing fluff or buzzwords.
  • Use alarmist language to manufacture urgency.
  • Hide the AI — the dual-engine method is the selling point.
precisetrustworthytechnicalplain-spokenconfidenthonest
Litmus Brand Pack v1 · proposed direction · June 2026