Decision

Standardize product terminology from "Agent-First Workspace" to TeamHive.

Context

The product was originally referred to as "Agent-First Workspace" internally, but we're now branding it publicly as TeamHive (teamhive.ai). Need consistent terminology across codebase, docs, and conversations.

Naming Convention

• Product name: TeamHive (in prose, documentation, marketing)
• Domain: teamhive.ai (URLs, email addresses)
• Code references: teamhive (lowercase, no punctuation - variable names, modules, etc.)
• Tagline: "TeamHive: Team layer for AI agents"

Rationale

• Conversational: "TeamHive" flows more naturally than "TeamHive.ai" in speech and writing
• Brand-forward: Clean, memorable brand name that works across all contexts
• Domain flexibility: Can use teamhive.ai as domain while "TeamHive" is the product name (standard pattern like Stripe/stripe.com)
• Value alignment: Name emphasizes the hive/collective intelligence metaphor and team collaboration, which aligns with "team layer for AI agents" positioning

Usage Examples

• ✅ "I'm building with TeamHive"
• ✅ "Check out teamhive.ai"
• ✅ import { teamhive } from '@teamhive/core'
• ❌ "I'm using TeamHive.ai" (awkward in conversation)
• ❌ "AI Team Hive" (too descriptive, not branded)

Impact

Will need to update:

• README and documentation files
• CLAUDE.md files (currently reference "Agent-First Workspace")
• Code comments and developer-facing documentation
• Workspace names in the MCP system
• Repository description and metadata

Decision

Standardize product terminology from "Agent-First Workspace" to TeamHive.

Context

The product was originally referred to as "Agent-First Workspace" internally, but we're now branding it publicly as TeamHive (teamhive.ai). Need consistent terminology across codebase, docs, and conversations.

Naming Convention

• Product name: TeamHive (in prose, documentation, marketing)
• Domain: teamhive.ai (URLs, email addresses)
• Code references: teamhive (lowercase, no punctuation - variable names, modules, etc.)
• Tagline: "TeamHive: Team layer for AI agents"

Rationale

• Conversational: "TeamHive" flows more naturally than "TeamHive.ai" in speech and writing
• Brand-forward: Clean, memorable brand name that works across all contexts
• Domain flexibility: Can use teamhive.ai as domain while "TeamHive" is the product name (standard pattern like Stripe/stripe.com)
• Value alignment: Name emphasizes the hive/collective intelligence metaphor and team collaboration, which aligns with "team layer for AI agents" positioning

Usage Examples

• ✅ "I'm building with TeamHive"
• ✅ "Check out teamhive.ai"
• ✅ import { teamhive } from '@teamhive/core'
• ❌ "I'm using TeamHive.ai" (awkward in conversation)
• ❌ "AI Team Hive" (too descriptive, not branded)

Impact

Will need to update:

• README and documentation files
• CLAUDE.md files (currently reference "Agent-First Workspace")
• Code comments and developer-facing documentation
• Workspace names in the MCP system
• Repository description and metadata