Skip to content

Add Recertia logo design brief (marketing / GTM) #3

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Draft
quantrobs wants to merge 1 commit into
base: main
Choose a base branch
from
Draft

Add Recertia logo design brief (marketing / GTM) #3

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
186 changes: 186 additions & 0 deletions docs/brand/logo-brief.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,186 @@
# Recertia — Logo Design Brief

**Audience:** Brand / identity designer
**Prepared with:** Product positioning, GTM messaging, and existing console visual language
**Status:** Ready for exploration (no prior logo or brand kit exists)

---

## 1. What to design

A primary logo for **Recertia** (pronounced roughly *re-SER-sha*; aka **Re-certify**): a mark + wordmark system that works as the face of the product across docs, the operator console, GitHub, CLI splash, and future marketing surfaces.

**Primary deliverables**

| Asset | Use |
| --- | --- |
| Primary lockup (mark + wordmark) | Website, README, console header, decks |
| Mark alone (icon) | Favicon, app tile, avatar, loading state |
| Wordmark alone | Dense UI chrome, text-heavy docs |
| Mono / single-color variants | Dark UI, print, embroidery, stamps |
| Clear-space + minimum-size rules | Hand-off to engineering |

Prefer SVG + a short usage note. Raster exports only as secondary.

---

## 2. Product in one breath (GTM)

**Positioning statement**

> Recertia is a self-improving agent system for recurring technical work. It solves tasks, then **re-certifies** what worked into versioned, retrievable memory—so the next similar job is faster, cheaper, and more reliable. Improvement is measured against a control, not claimed on optimism.

**Category:** Agent runtime / compounding memory for operators (not a chatbot, not a fine-tuning platform).

**Core promise:** Competence that compounds with use—durable skills, facts, and cases under a golden gate, with an integrity ledger so nothing “quietly” changes.

**One-line for designers (feel, not copy):**
*Precision operations software that gets sharper every time it ships a win.*

---

## 3. Who this brand must speak to

| Persona | What they care about | Brand implication |
| --- | --- | --- |
| **Operator** | Run goals, trust outcomes, resume/cancel | Clear, calm, instrument-panel confidence |
| **Reviewer / librarian** | Promote only what proves lift | Certification, gates, version honesty |
| **Platform / infra builder** | Auditability, rollback, no unbounded autonomy | Technical, serious, anti-hype |
| **Research-curious buyer** | Falsifiable claims, ablation/control | Scientific rigor without academic coldness |

**Not the audience:** Consumer AI toys, “prompt magic” buyers, or generic SaaS dashboards that look interchangeable.

---

## 4. Brand personality (marketing + GTM)

| We are | We are not |
| --- | --- |
| Precise | Vague or mystical |
| Compounding / cumulative | One-shot demos |
| Honest about measurement | Hype, glow, “AGI” swagger |
| Operational (Pilot · Tower · Ops) | Playful sticker culture |
| Re-certifying / librarian-strong | Autopilot-without-oversight |

**Voice keywords for the mark:** certify · compound · cycle · ledger · gate · tower · memory that earns its keep.

**Name cue:** “Recertia” ≈ **re-certify**. The logo should make “re-” (again, renewal, revision) and “certify” (proof, stamp, seal, check) feel inevitable—without spelling them out.

---

## 5. Concept territories (pick 1–2 to explore)

Designers: explore **distinct** directions; do not mash all metaphors into one mark.

### A. Re-certify seal
A modern certification mark / stamp / wax-seal geometry that feels digital, not bureaucratic. Suggests: promoted knowledge, golden gate, version that passed the bar.
*Risk to avoid:* looking like a government badge or ISO sticker.

### B. Cyclic graph / compounding loop
A closed loop or small cyclic walk—bounded, intentional, not an infinity swirl. Suggests: graph-with-loops runtime; learning *across* runs.
*Risk to avoid:* recycling logo clichés, Möbius gimmicks, or “AI neural” node clouds.

### C. Control tower / instrument
A spare, high-trust mark echoing Pilot · Tower · Ops—alignment, beacon, or scoped radar. Suggests: operators in command, observation without chaos.
*Risk to avoid:* literal airplanes, ATC clipart, military insignia.

### D. Ledger / hash-chain hint
A subtle sequence, link, or scored notch that implies tamper-evident memory and rollback. Suggests: integrity ledger, attributable change.
*Risk to avoid:* blockchain meme aesthetics, QR-like noise.

**Recommended primary exploration:** **A (seal) + B (bounded loop)**—strongest tie to name + product mechanism. Use C/D as secondary accents if needed, not as the whole identity.

---

## 6. Visual starting point (existing product UI)

There is **no logo yet**. The operator console already sets a palette and tone the mark should coexist with:

| Role | Value | Notes |
| --- | --- | --- |
| Near-black ground | `#0f1419` / `#1a222c` | Primary UI background |
| Ink | `#e8eef4` | Primary light type |
| Muted | `#8b9aab` | Secondary text |
| Accent blue | `#3d9cf0` | Primary action / focus |
| Accent amber | `#e8a838` | Secondary highlight / “golden” cue |
| OK / danger | `#3cb371` / `#e35d6a` | Status only—not brand heroes |
| Type in product | DM Sans + IBM Plex Mono | Expressive but technical |

Atmosphere today: cool blue + warm amber radial washes on dark—precise, instrument-like, not neon.

**Logo color guidance**

- Design **monochrome-first** (works on light *and* dark).
- Optional 2-color system: ink + blue, or ink + amber for “certified / golden-gate” moments.
- Do **not** build the identity around purple gradients, glow, or cream+terracotta trends.

---

## 7. Wordmark direction

- Spell **Recertia** exactly (capital R). Do not invent a stylized misspelling.
- Prefer a custom or carefully chosen geometric sans with confident weight; avoid Inter / Roboto / Arial / system defaults as the brand face.
- Optional: slight mono flavor in a letter or underline detail to nod at CLI / ledger—keep it subtle.
- Letterspacing should feel engineered, not luxury-fashion sparse or startup-rounded bubbly.

**Tagline (optional lockup, not required in mark):**
*Self-improving agents. Proven memory.*
(or shorter: *Re-certify what worked.*)

---

## 8. Hard constraints & anti-patterns

**Do**

- Read clearly at 16×16 (favicon) and at large deck scale.
- Feel at home next to dark ops UI *and* on a light README / print sheet.
- Suggest certification, compounding, or bounded cycles without illustration overload.
- Leave clear space; keep geometry reducible to simple paths.

**Do not**

- Robot heads, brains, sparkles, constellation “AI” nodes, or chatbot bubbles.
- Purple-on-white / indigo glow SaaS tropes; cream serif + terracotta; broadsheet newspaper density.
- Unbounded infinity loops implying runaway autonomy (product explicitly budgets loops and gates promotion).
- Literal certificates with ribbons, gavels, or diploma kitsch.
- Overly playful mascots—this brand sells trust and measurement.

---

## 9. Competitive / category contrast (GTM)

Recertia should **not** look like:

- Generic agent frameworks (friendly robot + purple gradient)
- Model providers (abstract neural shimmer)
- DevTools that only signal “code” (brackets / `>_` alone)

It **should** look like something an operator would trust to promote library changes: closer to **precision instrumentation + certification** than to consumer AI marketing.

Differentiator to encode visually: *managed, versioned, re-certified memory*—not “smarter model weights.”

---

## 10. Success criteria (how we’ll judge comps)

1. **Name test:** Someone who hears “Re-certify” can believe this mark belongs to that idea.
2. **Brand test:** Remove surrounding UI chrome—the mark still feels like Recertia, not a swap-in SaaS.
3. **Ops test:** Looks credible in a dark console nav beside “Pilot · Tower · Ops.”
4. **Scale test:** Icon remains legible as favicon and GitHub avatar.
5. **Hype test:** Nothing that would embarrass a measurement-first GTM story (ablation, golden gate, ledger).

---

## 11. Handoff notes for marketing / GTM

- **Launch narrative:** compounding competence via re-certified memory; falsifiable lift.
- **Surfaces first:** GitHub README, console brand lockup, docs site / ADR headers, social avatar.
- **Phase later:** full brand guidelines (motion, illustration, photography)—out of scope for v1 logo.
- **Owner:** Product + GTM co-own final selection; engineering applies SVG to console + static assets.

---

## 12. Designer prompt (copy-paste)

> Design a logo for **Recertia** (“Re-certify”), a self-improving agent system for operators. The product solves recurring technical tasks and promotes only proven skills into versioned memory—competence compounds across runs under a golden gate and integrity ledger. Personality: precise, measured, operational—not hype AI. Explore a modern certification seal and/or a bounded cyclic graph mark, paired with a confident geometric wordmark “Recertia.” Monochrome-first; optional accents `#3d9cf0` (blue) and `#e8a838` (amber) on dark `#0f1419`. Avoid robots, brains, purple glow, infinity loops, and generic SaaS gradients. Deliver primary lockup, icon mark, wordmark, and mono variants that work at favicon size and in a dark ops console.
Loading