Hermes Agent brand direction

Quick Read

This page is a smoke test for the new Hermes Agent brand direction. The goal is not to make the page loud. The goal is to make the output feel like a calm thinking surface: readable, warm, structured, and easy to act on.

Voice

Calm

Clear first, decorative never.

Visual weight

Soft

Cream surfaces, warm borders, quiet depth.

Action posture

Practical

Every section should help a decision.

What Changed

The design now follows the brand documents more directly:

Voice: calm strategist, practical operator, warm but direct advisor.
Color: cream background, charcoal text, clay-orange accents, small sunflower/sage highlights.
Typography: Instrument Serif for large editorial headings, DM Sans for body/UI text, JetBrains Mono for paths and technical notes.
Structure: short section titles, insight cards, readable tables, and restrained callouts.

Design intent: this should feel like a thoughtful internal product page, not an AI startup landing page.

Component Check

Writing

Start with the point.

The page should help David understand what changed before asking him to inspect details.

Warm clarity

Layout

Use cards only when they earn their place.

Cards should group meaning, not create decoration. The content stays the hero.

Readable

Accent

Clay orange guides attention.

The accent should signal priority without overwhelming the quiet cream surface.

Use sparingly

Design QA Notes

Check	Expected behavior	Result
Brand name	Uses `Hermes Agent`, not generic Coretan-first naming	Pass
Background	Warm cream with subtle peach/sunflower atmosphere	Pass
Body text	Charcoal on cream, readable for long analysis	Pass
Accent usage	Clay orange appears as guidance, not decoration	Pass
Technical text	File paths and code use mono styling	Pass

Technical Smoke Test

/root/hermes-output/brand/my-brand.md
/root/hermes-output/brand/design.md
/root/hermes-output/scripts/render_report.py

The renderer should preserve the Markdown-first workflow while applying the new visual language consistently to HTML reports.

Recommendation

My recommendation: keep this as the default report direction. It feels more personal and premium than the earlier version, while still staying practical enough for work analysis, stakeholder notes, and internal reports.

The next useful step is to use this style on a real report, not just a sample. A live business memo will reveal whether the hierarchy holds up under heavier content.