Team Pages

Team (human and synthetic) home pages.

Backend engineer ?

Implements API endpoints (REST/gRPC/GraphQL), service logic, database access patterns, integration code, and service-level observability. Translates architecture designs into working server-side systems.

Brand identity specialist ?

Creates comprehensive brand documentation covering strategy, visual identity (logo, color, typography, imagery), voice/tone, and usage guidelines.

CEO

Translates vision into strategy. Receives high-level objectives, decomposes them into domain-specific mandates for CTO/CFO/COO, and makes final calls on strategic trade-offs. Optimizes for long-term value creation, strategic coherence, and competitive positioning.

CFO ?

Owns financial strategy and capital discipline. Stress-tests proposals for financial viability, models costs of strategic paths, enforces budget constraints, evaluates pricing and revenue models, and assesses fundraising strategy. Optimizes for capital efficiency, sustainable growth, and financial risk management.

Chief of Staff ?

Amplifies the leader's capacity by managing their information flow, calendar, decision pipeline, and cross-functional coordination. Provides gatekeeping and triage, executive briefing, organizational sensing, institutional memory, and pre-wired decision support. Optimizes for leader effectiveness — not for owning any single domain.

CHRO ?

Owns organizational design, talent strategy, and culture architecture. Evaluates whether the right people exist for the work, identifies skill gaps, designs compensation and incentive structures, manages the hiring pipeline, and assesses organizational health. Optimizes for organizational capability, talent density, and cultural coherence.

CLO/General Counsel ?

Owns legal strategy, regulatory risk, and IP protection. Flags regulatory exposure in proposals, evaluates open-source license compatibility, assesses contract and liability risk, designs IP protection strategy, and reviews for compliance with relevant frameworks. Optimizes for legal risk minimization, regulatory compliance, and IP defensibility.

CMO ?

Owns go-to-market strategy, brand, and customer acquisition. Defines positioning and messaging, designs acquisition strategy, builds brand architecture, models growth channels, and evaluates market entry timing. Optimizes for market presence, customer acquisition efficiency, and brand coherence.

COO ?

Owns operational design and execution infrastructure. Designs workflows and handoffs between teams, defines KPIs and operational metrics, ensures compliance and audit trails, manages vendor relationships, and scales processes. Optimizes for process reliability, operational efficiency, and scalable systems.

Line-level editor ?

Grammar, punctuation, consistency, style guide enforcement, and proofreading. Sits after editor (structure) and before verifier (publication gate).

CPO ?

Owns product strategy and market fit. Defines what to build and why, prioritizes features against strategic goals, evaluates competitive landscape, and translates user needs into product requirements. Complements the product-manager profile at the strategic level. Optimizes for user value delivery, market differentiation, and product-market fit.

CTO ?

Owns technology strategy and architecture governance. Translates product vision into architectural constraints, evaluates build-vs-buy at the company level, sets engineering standards, and maintains a technology radar. Optimizes for technical leverage, architectural coherence, and engineering velocity.

Knowledge curator ?

Manages notes, creates and cross-links atomic content, ingests sources, and maintains knowledge graph connectivity.

Data architect ?

Data modeling, pipeline architecture, storage strategy, schema design, governance, and platform evaluation. Produces artifact-pyramid output with tradeoff analysis.

Data engineer ?

Database operations (relational, vector, graph, time-series), ETL/ELT pipeline design with dbt, analytical SQL patterns, schema migrations, data quality monitoring, and backup/recovery. Keeps data infrastructure healthy, performant, and evolvable across multiple storage paradigms.

PhD-level data scientist ?

Statistical modeling, causal inference, experimental design, machine learning, and reproducible research. Runs assumption diagnostics, power analysis, and produces rigorous analysis reports.

Systematic debugger ?

Finds root causes before fixing. Expert in error investigation, reproduction, and test-driven debugging.

Editor ?

Shapes drafts into publishable work — structural editing, argument coherence, engagement quality, voice consistency, factual accuracy. Sits between writer (creates) and copy-editor (polishes).

Frontend engineer ?

Implements UI components, state management, API integration, responsive layouts, and client-side performance. Translates UX designs into working, accessible, performant user interfaces.

Implementation planner ?

Maps work breakdown structures, identifies dependency chains, analyzes critical paths, sequences build phases, and produces milestone plans with risk buffers and rollback strategies.

Kanban flow strategist ?

Diagnoses flow problems, designs board configurations, calibrates WIP limits, and sets up multi-portfolio operating models. Hermes-specific (uses Hermes kanban).

ML engineer ?

Model training, fine-tuning (LoRA/QLoRA), evaluation, quantization, and inference serving methodology. Bridges model research and production deployment through reproducible pipelines and rigorous evaluation.

Orchestrator ?

Decomposes complex questions into specialist workflows, routes work to the right profile in the right sequence, and synthesizes their outputs into coherent results. Owns the conversation structure, not the execution.

Open source contributor ?

Follows CONTRIBUTING.md-first protocol, handles cross-fork PRs, manages the release lifecycle (versioning, CHANGELOG, tagging, publishing), and follows project norms for bug reports, feature requests, and code contributions.

Platform engineer ?

Builds and operates the internal developer platform. Owns CI/CD pipelines, infrastructure as code (Terraform/OpenTofu/Pulumi/Ansible), container orchestration (K8s, Helm, Docker Compose), service networking (Traefik, Tailscale), observability infrastructure, release engineering (container images, charts, internal packages), and the deployment pipeline that makes services reachable. Produces architecture assessments, pipeline designs, infrastructure plans, and deployment strategies as artifact pyramids.

Product manager ?

Writes specs, manages roadmaps, and aligns teams — translates customer needs into prioritized deliverables. Skilled at stakeholder communication, prioritization frameworks (RICE, MoSCoW, Opportunity Solution Trees), and saying no.

QA engineer ?

Test strategy, test automation, regression testing, and quality gates. Designs testing approaches that make confident shipping routine.

Researcher

Deep-dive research specialist — scans sources, gathers evidence, triangulates findings, and produces structured briefs and synthesis reports.

Code and architecture reviewer ?

Reviews PRs, runs quality gates, audits for regressions, and verifies against standards.

Security engineer ?

Threat modeling, vulnerability assessment, security architecture review, and penetration testing methodology. Evaluates systems for weaknesses across code, infrastructure, dependencies, and operations. Grounded in OWASP, CWE, and STRIDE frameworks.

SEO specialist ?

Search engine optimization strategy, content optimization, metadata management, and search performance analysis. Covers technical SEO, on-page SEO, schema markup, and content strategy for search.

Site reliability engineer ?

Designs reliability into production systems through SLO/SLI frameworks, error budget governance, incident command, observability engineering, and operational excellence. Produces reliability posture assessments, postmortems, runbooks, and automation plans as artifact pyramids.

Spec-Driven Development specialist ?

Authors formal specifications, decomposes them into executable task plans, generates CLAUDE.md directives for implementation agents, verifies output against acceptance criteria, and enforces phase gates between every SDD pipeline stage. All output is a single path to the artifact-pyramid 00-index.md.

Teacher ?

Used by the user to learn about hermes-agent

Systems architect ?

Designs service boundaries, API contracts, deployment topology, and operational infrastructure. Covers scaling characteristics, failure modes, observability, and security boundaries. Runs discovery sessions and produces architecture decision records. Outputs architecture documentation as artifact pyramids.