Most product-accurate: recall, trace, evidence, adoption, and test/commit proof in one system.
Closer To What Holmes Does
This pass uses Holmes' actual product model as the source: local-first coding-agent memory, prompt-context, recall traces, evidence refs, Procedures, Memory Spaces, Artifacts, Profiles, and Shared Workspace handoffs.
Lead Recommendation
Ranked by actual Holmes fit first, then memorability and logo viability.
Best product-model logo: the mark directly encodes Profiles, Memory Spaces, Artifacts, Procedures, and Shared Workspaces.
Best market-positioning mark: Holmes as the owned local layer underneath existing coding agents.
Best differentiator mark: reusable operating knowledge surfaced to agents with evidence.
Exact Logo Proposals
Left: logo crop used by the brief. Right: the full generated product board it came from.
Recall Trace
Holmes retrieves memory with provenance: why it surfaced, where it came from, and whether later work used it.
Five Product Nouns
The H is built from Holmes' canonical primitives: Profiles, Memory Spaces, Artifacts, Procedures, and Shared Workspaces.
Owned Memory Layer
Holmes sits under existing coding agents so accumulated context stays local, portable, and owned by the team.
Procedures
Holmes turns recurring engineering work into reusable runbooks, rules, migrations, and troubleshooting workflows.
Local Tier 0
Holmes works fully offline: local storage, BM25/FTS5 recall, no embedder, no model, no API key.
Shared Handoff
Holmes packages scoped context for teammates and agents with readable evidence, artifacts, procedures, and workspace boundaries.