Logo exploration / v01-v06

Holmes

Local-first, evidence-backed memory for coding agents. These directions avoid generic brain/cloud memory branding and focus on proof, source routing, and agent handoff.

Target buyer: Head of Platform or DevEx at a 50-500 developer, security-aware org already using Codex plus Claude.

Audience: Staff engineers, AI Platform, DevEx, security-conscious CTOs, and platform teams evaluating local Tier 0 discovery.

Brand Job

Signal developer infrastructure with evidence and inspectability. Holmes should feel like a local tool an engineering team trusts before procurement, not a broad consumer memory app.

Competitive Read

Mem0, Zep, Supermemory, Hindsight, Letta, Basic Memory, and LangMem cluster around memory APIs, temporal graphs, stateful agents, profiles, Markdown files, and self-improving agents. Holmes needs a sharper proof-and-routing identity.

Visual Guardrails

Use restrained geometry, source marks, database forms, code brackets, and review states. Avoid brain icons, cloud loops, detective costumes, friendly mascots, and abstract node meshes that blur into every other AI memory product.

v01 / Proof Orbit

Holmes

Best for making memory feel governed: a central memory block, source states, and accepted/rejected evidence. Strongest tie to review, audit, and conflict handling.

evidencereviewoperator trust

v02 / Source Lens

Holmes

Most immediately readable: local database plus inspection lens and verified source. It is less novel, but it communicates what the product does fastest.

local DBinspectablefirst-read clarity

v03 / Casefile Terminal

Holmes

A memorable bridge between evidence packet and CLI. It leans closer to the Holmes name without using detective cliches, and could work well for audit/report surfaces.

artifact packetCLIaudit-ready

v04 / Routing Switch

Holmes

Closest to the GTM thesis: decide what belongs in static files versus reviewed Holmes context. It is explanatory and strong for sales collateral, though busier as a tiny favicon.

static-file honestyroutingproof packet

v05 / Agent Handoff

Holmes

Good for Codex plus Claude continuity: two coding-agent surfaces pass reviewed context through a proof path. Needs simplification if selected.

Codex + Claudehandoffcontinuity

v06 / Bracket Memory

Holmes

Most brandable as a developer icon: bracket shell plus memory bars and a small review dot. It is abstract enough to own, while still pointing at code context.

developer-nativeapp iconmemory space

Holmes

ProfilesMemory SpacesProcedures

Local Tier 0 Discovery

Source candidates42

Static-file exports9

Reviewed memories18

Holmes

AuditRecallHandoff

Knowledge-Loss Audit

Repeated contextHigh

Evidence coverageReady

Buyer packetDraft

Recommended Iteration Path

Start from v06 for the core identity, then borrow the verified-source accent from v02 and the audit/report metaphor from v03. v04 is valuable as campaign iconography even if it is too explanatory for the master mark.

1. v06 Bracket Memory

Best primary logo candidate. Strong app-icon silhouette, developer-native, and visually less crowded than the routing concepts.

2. v02 Source Lens

Best literal product explanation. Refine into a smaller secondary mark or onboarding illustration.

3. v03 Casefile Terminal

Best memorable brand story. Strong for proof packets, audits, and conference-style collateral.

Research Inputs

Project positioning: README, docs/guardrails.md, CONTEXT.md, docs/product-model.md, docs/tiers.md, docs/marketing/perfect-customer-profile.md, docs/marketing/customer-development.md, docs/marketing/holmes-differentiation-2026-06.md, docs/marketing/competitor-summary.md, docs/competition/competitive-feature-matrix-2026-06.md.

External competitor references: Mem0, OpenMemory MCP, Letta Code, Zep Graphiti, Supermemory, Hindsight, Basic Memory, LangMem.

Generated with the built-in image generation path. Source images were copied from the Codex generated image store into this versioned exploration directory.