Decision

Rebrand from TeamHive to HiveNative.

Assets Secured

Asset	Value	Status
Domain	hivenative.com	✅ Purchased
Twitter/X	@hivenativehq	✅ Secured
LinkedIn	/company/hivenative	✅ Secured
GitHub	/hivenative	✅ Secured

Rationale

Why HiveNative

1. Thesis-encoded: Directly captures the "agent-native" differentiator vs. legacy tools with AI bolted on
2. Industry resonance: Echoes cloud-native, mobile-native — developers instantly understand the paradigm shift
3. Keeps Hive: Preserves the collective intelligence / coordination metaphor from TeamHive
4. Ambition signal: "Native" implies built-for, not adapted-for — signals we're not just another tool
5. Clear pronunciation: No spelling confusion or explanation needed

The core message

Microsoft is bolting Copilot onto Office. Google is adding Gemini to Docs. They're adapting legacy tools.

HiveNative is built native to how work will happen — humans orchestrate, agents execute.

Naming Convention

• Product name: HiveNative (in prose, documentation, marketing)
• Domain: hivenative.com
• Social: @hivenativehq
• Code references: hivenative (lowercase, no punctuation)

Tagline Options (TBD)

• "Built for agents, not adapted for them"
• "The agent-native workspace"
• "Work, native to AI"

Origin

Emerged from @Naming Exploration: untitled.new (Feb 2026) naming exploration using untitled.new, building on @Naming Tournament Results naming tournament. The generated candidates (Chorus, Conduct, Quorum, etc.) felt like "another dev tool" rather than capturing the "kill Microsoft Office" ambition. HiveNative was developed in conversation as a compound that encodes the core thesis.

Supersedes

This decision supersedes @Standardize product name to TeamHive (Standardize product name to TeamHive).

Decision

Rebrand from TeamHive to HiveNative.

Assets Secured

Asset	Value	Status
Domain	hivenative.com	✅ Purchased
Twitter/X	@hivenativehq	✅ Secured
LinkedIn	/company/hivenative	✅ Secured
GitHub	/hivenative	✅ Secured

Rationale

Why HiveNative

1. Thesis-encoded: Directly captures the "agent-native" differentiator vs. legacy tools with AI bolted on
2. Industry resonance: Echoes cloud-native, mobile-native — developers instantly understand the paradigm shift
3. Keeps Hive: Preserves the collective intelligence / coordination metaphor from TeamHive
4. Ambition signal: "Native" implies built-for, not adapted-for — signals we're not just another tool
5. Clear pronunciation: No spelling confusion or explanation needed

The core message

Microsoft is bolting Copilot onto Office. Google is adding Gemini to Docs. They're adapting legacy tools.

HiveNative is built native to how work will happen — humans orchestrate, agents execute.

Naming Convention

• Product name: HiveNative (in prose, documentation, marketing)
• Domain: hivenative.com
• Social: @hivenativehq
• Code references: hivenative (lowercase, no punctuation)

Tagline Options (TBD)

• "Built for agents, not adapted for them"
• "The agent-native workspace"
• "Work, native to AI"

Origin

Emerged from @Naming Exploration: untitled.new (Feb 2026) naming exploration using untitled.new, building on @Naming Tournament Results naming tournament. The generated candidates (Chorus, Conduct, Quorum, etc.) felt like "another dev tool" rather than capturing the "kill Microsoft Office" ambition. HiveNative was developed in conversation as a compound that encodes the core thesis.

Supersedes

This decision supersedes @Standardize product name to TeamHive (Standardize product name to TeamHive).