01 / 42
Hydra
Visual Brand Deck
Sage v2  ·  Autonomous Code Governance  ·  May 2026
Contents

What is in this deck.

03Brand at a Glance
04Logo System
09Color
14Typography
18Grid and Layout
21Illustration
23Iconography
25Motion
27Data Visualization
29UI Components
33Voice on Visuals
35Applied Examples
41Quick Reference

This deck is for designers, agencies, and freelancers applying the Hydra brand across digital surfaces. Every rule has a spec. Every principle has a finished example.

02   Brand at a Glance

Hydra in 5 seconds.

Hydra
Primary
UI
Accent
Display
The fix,
not the flag.
Typeface
Inter  ·  400 / 700 / 800 / 900
Mono
bundle/error-handling.md
Brand character
The Scholar Who Ships.

Speaks in citations. Ships the fix. Quantifies everything. Never uses adjectives where a number fits.

Category
Autonomous Code Governance
Surface priority
Web  ·  Email  ·  Social  ·  GitHub  ·  Product UI
03   Logo System

Primary logo.

On dark
Hydra
Hydra
Display gradient + glow. Background #0A0A0A min.
On light
Hydra
Hydra
UI gradient, no glow. White or #F5F5F3 background.
03   Logo System

Sizes and clear space.

96px
Hero / OG image
48px
Favicons / social
32px
Nav / email header
20px
Inline / badge
16px
Minimum size
<16px
Never
Clear space

Equal to the width of one vertical stroke on all four sides. At 32px mark, clear space = 5px minimum.

Screen minimum

16px. Below this the crossbar disappears. Use text-only "Hydra" wordmark instead.

Print minimum

6mm. At 300 DPI this is 71px. Use the SVG source, never upscale a PNG.

03   Logo System

Approved color variations.

Display gradient

Dark bg only. With glow.

UI gradient

Light bg. Email, GitHub.

Mono white

Single color dark. Embossing, watermarks.

Mono black

Legal docs, fax, 1-color print.

Rule: Display gradient is for dark surfaces only. UI gradient for light. Mono white or mono black when color is not available. Never mix these modes on a single surface.

03   Logo System

Misuse. Never do these.

Wrong color

Never use custom fills or off-brand colors.

Distorted

Never stretch or squash. Constrain proportions.

Rotated

Always upright. No tilts, no angles.

Low contrast

Never place on similar-value background.

Drop shadow

Glow only. Hard shadows never.

Outlined

Never outline or stroke the mark.

Busy background

Solid or near-solid backgrounds only.

Display gradient on light

Low contrast. Use UI gradient instead.

03   Logo System

File inventory.

File name
Format
Use
Notes
hydra-mark-display.svg
SVG
Web / dark bg
Display gradient stops embedded
hydra-mark-ui.svg
SVG
Web / light bg
UI gradient stops embedded
hydra-mark-mono-white.svg
SVG
1-color dark
fill="#ffffff"
hydra-mark-mono-black.svg
SVG
1-color light
fill="#0A0A0A"
hydra-lockup-dark.svg
SVG
Mark + wordmark
Horizontal lockup, dark
hydra-lockup-light.svg
SVG
Mark + wordmark
Horizontal lockup, light

Naming convention: hydra_[asset-type]_[variant]_[size].[ext]   Access: Figma brand file (request via #brand in Slack). PNG exports at 1x and 2x live in /assets/logos/ in the main repo.

03   Logo System

Alternative mark — Hi monogram.

On dark
48px
32px
20px
Construction — 4 rectangles
H — left leg  12×64
H — crossbar  48×9 @ y24
Right bar — lower  12×31 @ y33
Right bar — top  12×14 @ y0
On light
UI gradient (#047857 → #0E7490).
No glow on light backgrounds.

H right bar runs full height, split by an 18px gap at y12. Top square and lower column share the same x-axis — one break, two reads: H crossbar and i tittle simultaneously.

04   Color

Palette overview.

Primary palette
Sage
#34D399
RGB 52 211 153
Sage Mid
#10B981
RGB 16 185 129
Teal
#22D3EE
RGB 34 211 238
Forest
#059669
RGB 5 150 105
Forest Deep
#047857
RGB 4 120 87
Neutrals
#080C09
Base
#0F1712
Surface 1
#162019
Surface 2
#2A5038
Border active
#E5E5E5
Light border
#F0F0F0
Light divider
#F5F5F3
Light bg
Alert colors
Success
#10B981
Warning
#D97706
Error
#EF4444
Info
#3B82F6
04   Color

Two gradient modes.

Display mode  —  Dark surfaces only
#34D399 0%
#10B981 55%
#22D3EE 100%
linear-gradient(130deg, #34D399 0%, #10B981 55%, #22D3EE 100%)
Use on
  • Wordmark on dark
  • Hero display headlines
  • OG images on #0A0A0A
  • Never on white or light backgrounds
UI mode  —  All surfaces
#059669 0%
#047857 55%
#0E7490 100%
linear-gradient(130deg, #059669 0%, #047857 55%, #0E7490 100%)
Use on
  • Mark on light backgrounds
  • Buttons and CTAs
  • Citation borders in email and GitHub
  • Badges and status indicators
04   Color

Proportion and pairings.

Color proportion (dark UI)
65% Base
20% Surface
10% UI green
5% Display
Color proportion (light surface)
70% White
15% Tint
15% Forest
Approved pairings
Aa
White on #0A0A0A
Ratio 19.1:1   AAA
Aa
#059669 on #F0FDF4
Ratio 4.5:1   AA
Aa
Display grad on #080C09
Ratio 10.8:1   AAA
Aa
#047857 on white
Ratio 5.9:1   AA
Aa
Dim text on #080C09
Ratio 5.0:1   AA (body only)
04   Color

Color do and do not.

Do

Display gradient on dark base.

High contrast. Gradient reads clearly. Glow adds depth.

Do not

Display gradient on light.

Low contrast. #34D399 on white = 2.1:1. Fails WCAG AA.

Do
Convention bundle
bundle/error-handling.md

UI green for citations on light: #059669 border, #F0FDF4 fill.

Do not
Convention bundle
bundle/error-handling.md

Display green on light: #34D399 = 2.1:1 on white. Fails WCAG.

04   Color

Accessibility contrast ratios.

Foreground
Background
Ratio
AA
AAA
#FFFFFF
#080C09
19.1:1
PASS
PASS
#34D399
#080C09
10.8:1
PASS
PASS
#059669
#FFFFFF
4.5:1
PASS
FAIL
#34D399
#FFFFFF
2.1:1
FAIL
FAIL
#047857
#FFFFFF
5.9:1
PASS
FAIL

Target: WCAG AA for all text. #34D399 is decorative only on dark. Never use it as text color on light backgrounds.

05   Typography

Inter. One typeface. Full system.

Weights in use
Hydra 400 · Regular Body, captions
Hydra 600 · Semibold Labels, UI elements
Hydra 700 · Bold Headings, CTAs
Hydra 800 · ExtraBold Section titles
Hydra 900 · Black Display, wordmark only
Mono — citations and code output
Discovery output
Convention: async-error-handling
Source: bundle/error-handling.md
Occurrences: 142 across 38 files
Confidence: high
Google Fonts import
@import url('fonts.googleapis.com/css2?family=Inter:wght@400;600;700;800;900&display=swap');

Italic weights are never used. Avoid faux bold. Mono fallback: 'SF Mono', 'Fira Code', monospace. Never subset without confirming all required glyphs.

05   Typography

Type scale.

Display Hero
Find. Fix.
64px900−6%
H1 — Section
The loop closes.
48px800−5%
H2 — Slide
Three-step audit.
32px700−4%
H3 — Card title
Deterministic Scanner
20px700−3%
Body Large
Hydra finds bugs across your entire codebase.
18px4000%
Body
No human in the critical path. Every change is reviewable.
15px4000%
Label / Eyebrow
Autonomous Code Governance
11px700+14%
Caption
Target: WCAG AA for all text. Never use as primary copy.
9px5000%
05   Typography

Type in context.

Navigation bar
Hydra
Overview
Findings
Kaizen
Settings
Active: 9px / 600 / #fff
Inactive: 9px / 400 / dim2
Web hero block
Autonomous Code Governance
Every other tool leaves a comment.
Hydra leaves it done. No human in the critical path.
Connect a repo
Eyebrow: 11px/700/+14%/green
Hero: 64px/900/−6%
CTA: 13px/700
Finding card
Critical · SEC-47
SQL injection in auth handler
Unparameterized query in auth/login.ts:241
Confidence: high Fix ready ✓
Card title: 11px/700/−2%
Body: 8px/400
Label: 7px/700/+12%
Terminal / citation
$ hydra fix --issue SEC-47
Reading conventions... done
Writing tests... 6 written
Executing fix... auth/login.ts
Tests passing... 6/6
PR opened... #892
Ticket closed... SEC-47 ✓
SF Mono / Fira Code
Green: #34D399 · Teal: #22D3EE
Passive: dim2
05   Typography

Type do / don't.

✓ Do — Tight display type
7 loops.
$2.75.

Extreme tight tracking at display scale. Weight 900. Numbers lead. Short, declarative.

64px · 900 · tracking −6%
✓ Do — Three-tier hierarchy
Autonomous Code Governance
The loop closes.

Green eyebrow → white heading → dim body. Three distinct levels. Never collapse into two.

Eyebrow: #34D399 / Label · Head: white/800 · Body: dim2/400
✓ Do — Mono for citations
Convention: async-error-handling
Source: error-handling.md
142 occurrences

Citations always in mono. Green = convention name. Teal = file path. White = count.

✗ Don't — Light weight display
Hydra

Never weight 400 or below at display scale. Never zero tracking above 24px. Looks unfinished.

✗ Don't — All-caps body
HYDRA FINDS BUGS

All-caps is for 11px eyebrow labels only. Never on body copy, never on headings, never above +14em tracking.

✗ Don't — Adjective-led copy
"Revolutionary seamless AI"

Hydra vocabulary is numbers and mechanisms, not adjectives. Never: revolutionary, seamless, robust, cutting-edge. Never italic.

06   Grid & Layout

12-column grid.

Desktop — 1440px reference
Columns
12
Gutter
24px
Margin
80px
Max width
1280px
Mobile — 375px
Columns
4
Margin
16px
Column span patterns
Hero — full width (12 col)
Two column — 6 + 6
Content + aside — 8 + 4
Three-card grid — 4 + 4 + 4
Product UI — sidebar 2 + content 10
Border radius system
4px
Chips
8px
Buttons
12px
Cards
16px
Panels
pill
Nav/tags
06   Grid & Layout

4px spacing system.

Scale — all values are multiples of 4
4pxspace-1
Icon gap, micro spacing
8pxspace-2
Label + value, badge pad
12pxspace-3
List item gap
16pxspace-4
Card padding, section gap sm
24pxspace-6
Card gap, gutter default
32pxspace-8
Section internal padding
48pxspace-12
Section gap, large card pad
64pxspace-16
Page section separator
96pxspace-24
Hero section padding
128pxspace-32
Page top/bottom margin
Off-grid rules

Off-grid values (6px, 10px, 14px) are permitted only for optical corrections. Never for structural spacing.

Document off-grid values in code comments when used. Never undocumented.

Line heights follow a 4px grid. 16px text → 24px line height. 13px text → 20px. Always divisible by 4.

Spacing in practice — card anatomy
Critical · SEC-47
SQL injection in auth handler
auth/login.ts:241
Fix now
Dismiss
← 16px pad
← 6px gap
← 4px gap
← 12px gap
06   Grid & Layout

Layout patterns in context.

Marketing hero
Hydra
Connect a repo
Autonomous Code Governance
Every other tool
leaves a comment.
Hydra leaves it done.
Connect a repo
16m
Discovery
$2.75
Kaizen
0
Eng hours
12-col centered · max 800px text
Product dashboard
Overview 2h ago
Open issues
47
Fixed
23
SQL injection · auth/login.ts
Fix
Dead code · utils/format.ts
Queue
Sidebar: 200px fixed · Content: flex
Documentation page
Layer 1 — Find
Discovery + Audit
Hydra reads the entire codebase before it touches anything. Discovery runs once per repo in ~16 minutes.
$ hydra discover
142 conventions found
On this page
Discovery
Three-step audit
~16 min · once per repo
8-col content + 4-col aside
Email — single column
Hydra
Subject: 7 loops. $2.75. No engineer hours.
The debt backlog is shrinking and no one is doing it manually.
We ran Kaizen on our own codebase. 7 autonomous loops. $2.75 total. Zero engineer hours.
7 loops · $2.75 · 0 hours
Connect a repo →
600px single-col · 40px pad · dark
07   Illustration

Technical diagram style.

Construction rules
2px strokeAll outlines and edges. Never 1px (thin at high DPI). Never 3px+.
4px cornersNodes and containers. Matches UI border-radius system.
OrthogonalConnectors are horizontal/vertical only. No diagonals. 90° bends with 4px radius.
#34D399 activePrimary flows, key nodes, success states. Dark backgrounds only.
#22D3EE secondaryData paths, references, teal layer. Creates visual hierarchy.
dim3 passiveInactive nodes, background structure, reference paths.

Every node represents a real system component. Every connector is a real data flow. No abstract decorative shapes. If a node cannot be labeled with its actual function, remove it.

Node anatomy — element types
Discovery
~16 min
Process node — rounded rect, 2px #34D399 border
Tests pass?
Gate / decision — amber border, conditional label
.hydra/
Data store — mono text, teal 2px border
Linear / Jira
External system — dashed dim border
Ticket closed ✓
Terminal — pill shape, filled #34D399
Connector — 2px stroke, filled triangle arrowhead
07   Illustration

Find · Fix · Improve · Govern — finished diagram.

Find
Discovery
~16 min per repo
Deterministic scan
Grep + rules engine
6 parallel agents
40 dimensions
Opus meta-review
Open prompt pass
Fix
Ticket created
Linear · Jira on roadmap
Baseline tests first
Before any change executes
Convention-matched fix
Codebase's own patterns
PR opened · ticket closed
On merge. No human touched it.
Improve
Kaizen loops
Budget or focus area
Git worktrees
No conflict with active work
Continuous
Between sprints, not event-driven
7 loops · $2.75
Zero engineer hours
Govern
PR review
Living comment · check gate
Self-improvement loop
Patterns from failure modes
78 scanner patterns
20 meet global threshold
No authoring required
Builds itself from audits
08   Iconography

Icon grid and construction.

Construction specs
24 × 24pxDefault grid. All icons drawn to this canvas. Export at 1× and 2× for retina.
2px strokeAll strokes are 2px. No filled icons except status dots and logo mark.
2px cornersstroke-linecap: round. stroke-linejoin: round. No sharp joins.
2px insetAll strokes stay 2px from canvas edge. Live area: 20×20px within 24×24px.
currentColorAlways use currentColor for stroke. Never hardcode color values inside SVG files.
16 / 20 / 24pxThree sizes. 16px in dense UI, 20px default, 24px for feature icons.

Source: Heroicons v2 Outline as base. Custom icons follow the same grid and stroke spec. Never mix icon families. Never resize by adding stroke-width — only scale the SVG element.

Grid anatomy
16px
20px default
24px feature
08   Iconography

Icon library.

Actions
search
add
expand
edit
delete
download
refresh
Status
check
error
warning
info
pending
Product — Hydra-specific
govern
pr-review
finding
kaizen
codebase
code
package
09   Motion

Motion principles.

Four timing tiers
Instant 0ms

No animation. Data display, number updates, status toggles. Motion here reads as lag, not polish.

transition: none
Quick 100ms · ease-out

Micro-interactions. Button press, hover state, checkbox, tooltip appear. Feels responsive, not slow.

transition: all 100ms cubic-bezier(0,0,0.2,1)
Standard 250ms · ease

Panel open/close, modal, slide transition, menu expand. Default for most UI motion.

transition: opacity 250ms ease, transform 250ms ease
Slow 400ms · ease-in-out

Full-page transitions, onboarding steps, major state changes. Use sparingly.

transition: all 400ms cubic-bezier(0.4,0,0.2,1)
Motion rules

Elements enter fast, exit slow. Ease-out on enter (responsive feel). Ease-in on exit (deliberate feel).

Opacity transitions always accompany transform transitions. Never transform without opacity change.

Never animate layout properties (width, height, top, left). Use transform and opacity only for performance.

Respect prefers-reduced-motion. All animations must be disabled when the system flag is set.

Slide deck — this deck
.slide {
  transition: opacity 250ms ease;
}
.slide.on {
  opacity: 1;
}
09   Motion

Easing curves and tokens.

Four curves — visualized
ease-out cubic-bezier(0, 0, 0.2, 1)

Fast start, gradual deceleration. Use for enter animations. Elements arrive immediately.

ease-in cubic-bezier(0.4, 0, 1, 1)

Slow start, fast exit. Use for exit animations. Elements leave with intention.

ease-in-out cubic-bezier(0.4, 0, 0.2, 1)

Symmetric acceleration. Major state transitions, page changes. Deliberate and weighted.

Token table
--dur-0 0ms Instant — data, status
--dur-quick 100ms Hover, press, tooltip
--dur-std 250ms Panel, modal, slide
--dur-slow 400ms Page transition, onboarding
--ease-out 0,0,0.2,1 Enter animations
--ease-in 0.4,0,1,1 Exit animations
--ease-inout 0.4,0,0.2,1 Major transitions
Reduced motion
@media (prefers-reduced-motion: reduce) {
  *, *::before, *::after {
    animation-duration: 0.01ms !important;
    transition-duration: 0.01ms !important;
  }
}
10   Data Visualization

Chart system.

Color sequence — use in order
Primary — #34D399
1st series, key metric, success state
1st
Accent — #22D3EE
2nd series, comparison metric
2nd
Neutral — rgba(255,255,255,0.35)
3rd series, background comparison
3rd
Critical — #EF4444
Error states, threshold breach, critical
Alert
Warning — #D97706
Warnings, medium severity findings
Alert
Typography in charts
Axis labels9px / 500 / dim1 — never bold
Data labels10px / 600 / #fff — only on key points
Legend10px / 500 / dim2 — right or bottom
Gridlines1px / rgba(255,255,255,0.06) — horizontal only
Chart rules
Lead with the number, not the chart

Show the key metric as a large number above or beside the chart. The chart is evidence, not the headline.

No decorative charts

Every chart answers a specific question. If you cannot state the question in one sentence, remove the chart.

Three colors maximum

Use the color sequence in order. Never introduce a 4th data color. Use opacity variations within one color before adding a new hue.

Cite the source and timeframe

Every chart gets a caption: what it shows, the period, and the data source. No unlabeled data.

Start y-axis at zero

Never truncate the y-axis to exaggerate trends. Hydra's brand is credibility — misleading charts destroy it.

10   Data Visualization

Chart examples.

Bar chart — issues by severity
47
Open issues · audited 2h ago
3
12
32
Critical Medium Low
Last 30 days · Hydra audit data
Line chart — debt velocity
↓ 34%
Debt velocity · 8-week trend
Week 1 Week 8
New issues per sprint · 8 weeks post-install
Metric cards — stat display
Kaizen total cost
$2.75
7 loops · 0 engineer hours
Discovery duration
16 min
Runs once per repo
Scanner patterns generated
78
/ 20 global
From Hydra's own codebase
11   UI Components

Buttons and forms.

Button variants
Connect a repo
Primary
bg #059669 · text #fff · 700
View findings
Secondary
bg transparent · border 1px dim · text #fff
Dismiss
Ghost
no border · no bg · text dim2
Delete repo
Destructive
bg red/10 · border red/20 · text #EF4444
Run audit
Disabled
bg dim/5 · text dim1 · cursor: not-allowed

All buttons: height 40px default (32px compact, 48px large). Padding 16px horizontal. Border-radius 8px. Font 13px/700. Min-width 80px. Never all-caps button labels.

Form inputs — states
Default
github.com/acme/api
Focus
github.com/acme/api
Error
not-a-valid-url
Must be a valid GitHub repository URL
Disabled
github.com/acme/api
Input specs
Height40px default · 32px compact
Padding12px horizontal · 10px vertical
Font13px / 400 · Inter
Focus ringbox-shadow 0 0 0 3px #059669/15
Label11px / 600 / dim2 · above input · 6px gap
11   UI Components

Cards.

Finding card
Critical
SEC-47
SQL injection in auth handler
Unparameterized query allows attacker to bypass authentication. Found in auth/login.ts:241
Convention: async-error-handling · confidence: high
Fix now
Defer
Border: severity color at 22% opacity
Badge: severity color / 700 / +10%
ID: mono / dim1
Buttons: primary + ghost pair
Audit result card
Audit complete
Passed
Issues found
47
Auto-fixed
23
Duration
16m
Cost
$0.42
Conventions discovered
142 conventions · 38 files · high confidence
Metric grid: 2-col · #080C09 inset bg
Citation block: green border 15%
Status dot: 6px filled circle
PR review card
Hydra audit passed
✓ No blockers
0 blockers  ·  2 suggestions
Cites: bundle/error-handling.md
rules/auth-patterns.md
Suggestion: Consider typed catch block in api/fetch.ts:84 — matches async-error-handling convention
Suggestion: Dead import in utils/format.ts:3 — not referenced
Updated 30s ago · 3-step audit applied
Green border: audit passed
Mono block: citation output
Suggestion dot: amber
11   UI Components

Status and feedback.

Status badges
Fixed
bg green/10 · border green/25 · text green
Critical
bg red/10 · border red/25 · text red
Warning
bg amber/10 · border amber/25 · text amber
Running
bg teal/10 · border teal/25 · text teal
Pending
bg white/5 · border white/10 · text dim2
Inline alert
Fix merged successfully
PR #892 merged · SEC-47 closed · 6/6 tests passing
Fix failed — tests did not pass
4/6 tests failing · no changes pushed · review required
Toast notifications
Ticket closed. No human touched it.
SEC-47 · PR #892 merged · 2s ago
×
Review required before fix ships
QA-12 · baseline tests: 4/6 passing
×
Toast specs
PositionBottom-right · 24px from edges
Width360px fixed
Duration5s auto-dismiss · success only
StackMax 3 visible · LIFO order
11   UI Components

Navigation and shell.

Product shell — sidebar nav
Hydra
Overview
Findings 3
Kaizen
Governance
Settings
Overview
acme/api
Open
47
Fixed
23
SQL injection · auth/login.ts
Fix
Sidebar: 200px fixed · #080C09 bg
Active nav: green tint bg + white text
Badge: severity-colored pill
Shell specs
Sidebar width200px · collapses to 56px icon-only on mobile
Sidebar bg#080C09 · 1px right border var(--border)
Nav item h32px · 8px vertical pad · 8px horizontal
Active statebg rgba(52,211,153,0.08) · text #fff / 600
Top bar h56px · border-bottom var(--border)
Content pad24px all sides · 32px on wide screens
Breadcrumbs
Overview / Findings / SEC-47
Separator: / · color dim1 · Active page: white/600 · Parent pages: dim2/400
Tab bar
All
Critical
Medium
Low
Active: #080C09 bg · white/600 · Inactive: no bg · dim2/400
12   Voice on Visuals

Sage primary. Hero secondary.

Sage primary — trust through specificity
Show the work. Cite the sources.
Use the discovery output format: "Discovered from bundle/error-handling.md. 142 occurrences." A citation is not decoration — it is the claim.
Numbers over adjectives. Always.
"7 loops · $2.75 · 0 engineer hours" beats "dramatically reduced technical debt." Quantify everything. If you cannot attach a number, question whether the claim belongs.
Dry precision. Report results. Do not narrate.
Write as if you are an operations team reporting at 4pm on a Friday. Confident. Specific. No theatrical framing. "The ticket is closed" — not "the fix delivered transformational impact."
Specificity is the impulse trigger.
The install command and the discovery output go above the fold. The reader installs because they saw exactly what it found — not because they believed a promise.
Three questions before publishing any copy
Would a senior engineer say this in Slack at 4pm?
Is there a number, a mechanism, or a specific moment — or is it just a claim?
Does it show what Hydra does, or describe what Hydra is?
Hero secondary — urgency and action
Momentum language. Ship the fix.
"The loop closes." "The codebase gets cleaner." "The PR is open. The ticket is closed. Nobody touched it." Verbs that move. State that has changed.
The aha moment is the victory.
"You ran one command. The ticket closed itself." The terminal output is the hero frame. Show it. Lead with it. The engineer reads it and installs.
Hero is not the primary voice. Sage earns trust first.
Use Hero for CTAs, victory moments, and conversion points. Sage carries all educational and explanatory content. Never lead with urgency before the mechanism is understood.
On-visual type hierarchy
Eyebrow
Category label only — "Autonomous Code Governance"
Headline
One declarative statement. Short. No period needed.
Body
Mechanism or spec. Never restates the headline.
CTA
Action verb + object. "Connect a repo" — never "Get started"
12   Voice on Visuals

Say this. Not that.

Approved — use these
"Every other tool leaves a comment. Hydra leaves it done."
Strongest competitive contrast. Primary hero option. Approved.
"No human in the critical path."
Category frame. Always use "critical path" not "loop." Humans retain review rights.
"The loop closes."
The signature momentum phrase. Use for fix completion, milestone, and section headers.
"Autonomous code governance."
The category name. Never "AI code review." Never "code quality tool."
"Find. Fix. Improve. Govern."
The four-layer architecture. Always in this order. Use as section headers and diagram labels.
"Safe by design: baseline tests before, post-fix audit after."
Required whenever discussing autonomous execution. Never omit the safety message.
Kill list — never use
Revolutionary
Unsubstantiated
Seamless
Meaningless
Robust
Meaningless
Leverage
Filler verb
Supercharge
Filler verb
Empower
Filler verb
Signal not noise
Competitor phrase
Deploy with confidence
Competitor phrase
Fully automated
Humans retain review rights
No human in the loop
Use "critical path" instead
AI slop / vibe coding
Don't enter that frame
Eliminates engineers
Eliminates execution loop only
13   Applied Examples

Website hero.

Hydra
Docs Pricing GitHub
Connect a repo
Autonomous Code Governance
Every other tool
leaves a comment.
Hydra leaves it done.
Hydra finds the issue, writes the tests, executes the fix using your codebase's own conventions, and closes the ticket. No engineer in the critical path.
Connect a repo
Read the docs
16 min
Discovery · once per repo
$2.75
Kaizen · 7 loops · 0 eng hours
0
Human reviews to merge a fix
13   Applied Examples

Email — awareness.

From: Hydra <hello@hydra.dev>
To: eng@acme.com
7 autonomous improvement loops. $2.75. No engineer hours.
Hydra
The debt backlog is shrinking and no one is doing it manually.
We ran Kaizen on our own codebase. 7 autonomous improvement loops over the weekend. Zero engineer hours allocated. Here's what it cost.
Kaizen run · acme/api · weekend
Loops completed: 7
Total cost: $2.75
Engineer hours: 0
PRs opened: 7
Connect a repo →
Hydra · Autonomous Code Governance
Unsubscribe · Manage preferences
Subject line rules
✓ Lead with the specific number
✓ No more than 9 words
✓ Present tense, active voice
✗ No "introducing" or "announcing"
✗ No question marks
Format specs
Width600px max · dark bg #0D0D0D
Padding28px horizontal
LogoTop left · display gradient
Headline18px / 900 / −4%
CTACentered · #059669 bg · 700

Every email has exactly one CTA. The stat block is the evidence. The headline is the claim. The CTA captures the install. Never more than 3 paragraphs of body copy.

13   Applied Examples

Social card — LinkedIn + X.

Open Graph image — 1200 × 630px
Autonomous Code Governance
7 loops.
$2.75.
0 engineer hours.
We ran Kaizen on our own codebase over the weekend. Here's the output.
Hydra
hydra.dev
LinkedIn post format
Hydra
Autonomous Code Governance · 2h
We ran 7 improvement loops on our own codebase over the weekend. $2.75 total. No one worked on it.

Here's what Hydra found.
Autonomous Code Governance
7 loops. $2.75.
hydra.dev
Social copy rules
Lead with the result — not the product
OG image carries the headline — post copy teases
Number in the first line always
OG image: 1200×630 · display gradient · number-forward
Never name competitors in external posts
13   Applied Examples

GitHub PR review comment.

Open
Fix: typed catch blocks in async handlers #892
hydra-bot bot just now
Hydra audit passed
0 blockers · 2 suggestions
Convention-matched: async-error-handling
Source: bundle/error-handling.md · 142 occurrences
Baseline tests: 6/6 passing
Suggestion api/fetch.ts:84

Consider typed catch block — matches async-error-handling convention. Not blocking.

hydra/audit Passing · merge when ready
PR comment anatomy
Audit status block — green on pass, red on block
Convention citation in mono — source + count
Baseline test count always shown
Suggestions in amber — never block merge
GitHub check: hydra/audit — green or red
Copy rules for PR comments
Results before recommendations
Cite the convention source, not just the rule
Suggestions are never blocking — label clearly
Never say "critical" for non-blocker findings

The comment updates live as code changes. It is not static. The GitHub check system surfaces green/red in the PR merge UI independently of the comment body.

13   Applied Examples

In-app dashboard — findings view.

Hydra
Overview
Findings3
Kaizen
Governance
acme/api · main
Findings
Last audit: 2 hours ago
Run audit
All 47
Critical 3
Medium 12
Low 32
SQL injection in auth handler SEC-47
auth/login.ts:241 · Convention: async-error-handling · confidence: high
Fix now
View
Dead code in format utilities QA-12
utils/format.ts:3–18 · 142 references to exported types, none used
Queue fix
View
Missing typed catch in api handler Fixed ✓
api/users.ts:89 · PR #891 merged
13   Applied Examples

README badge and GitHub Marketplace.

README.md badge placement
Governed by Hydra
0 blockers
2 open issues
acme-api
The primary API service for Acme. Governed by Hydra — autonomous code governance.
## Getting started
$ npm install
$ npm run dev
## Code governance
This repo is governed by Hydra. Issues are found, fixed, and closed automatically. All fixes are convention-matched, baseline tested, and reviewable before merge.
Badge copy
[![Governed by Hydra](badge-url)](
  https://hydra.dev/repos/acme/api)
GitHub Marketplace listing
Hydra — Autonomous Code Governance
Code review · Security · Testing · Utilities
Install for free
About
Hydra reads your entire codebase, finds bugs and security issues, and closes them autonomously — from issue to merged PR. No human in the critical path. Discovery in 16 minutes. Kaizen improvement loops: $2.75.
Features
Autonomous fix execution — baseline tests, post-fix audit, PR opened, ticket closed
Three-step audit: scanner + 6 agents / 40 dimensions + Opus meta-review
Kaizen: continuous improvement loops — runs between sprints, no sprint time needed
CLAUDE.md injection — every teammate's AI session gets architecture context automatically
Quick Reference

Everything on one slide.

Color
#34D399
Display gradient · dark only
#059669
UI gradient · all surfaces
#22D3EE
Teal accent · mono, cites
#080C09
Background base
#EF4444
Critical / error
#D97706
Warning / medium
Typography
Display
64px · 900 · −6%
H1
48px · 800 · −5%
H2
32px · 700 · −4%
Body Large
18px · 400 · 0%
Body
15px · 400 · 0%
Eyebrow / Label
11px · 700 · +14%
Spacing
Base unit4px
Card gap24px
Section48–64px
Page margin80px
Max width1280px
Motion
Quick100ms ease-out
Standard250ms ease
Slow400ms ease-in-out
Logo clearspace
Hydra
Min clearspace = 0.5× wordmark height on all sides
Approved phrases
"No human in the critical path."
"The loop closes."
"Autonomous code governance."
"Find. Fix. Improve. Govern."
"Revolutionary / seamless / robust"