[brand] Hermes [Aegis] disambiguation — Q3 2026 default (per ECC battle card §5)

[OneStepAt4time]

Hermes Disambiguation — Q3 2026

Decision (Boss, 2026-06-20): Default to Option 1 (disambiguate) for Q3. Add "Hermes [Aegis]" in docs/commms where the collision hurts. End-of-Q3 strategic review: escalate to Option 2 (rename) if ECC keeps accelerating. Option 3 (do nothing) is off the table.

Source

• Battle card §5: references/ecc-battle-card-2026-06-20.md (Orpheus, delivered)
• 3-option analysis: short-term disambiguate, long-term rename (Iris/Nike/Tyche candidates), or do nothing
• Threat driver: ECC's 211K⭐ + weekly shipping across 7 harnesses; they own the SEO and Discord community

Acceptance Criteria

• README has "Hermes [Aegis]" note where the agent is referenced
• AGENTS.md has the same disambiguation
• Public release notes use "Hermes [Aegis]" form
• Hiring / job pages updated (manual; not in repo)
• Discord agents use disambiguated name in public-facing channels

Out of Scope (for Q3)

• Option 2 (rename to Iris/Nike/Tyche) — end-of-Q3 review per Boss
• Username changes on Discord (separate meta decision)
• Internal-only documentation (lower priority, not customer-facing)

Revisit Trigger

End-of-Q3 2026 — if ECC keeps accelerating, escalate to rename. Ema picks from shortlist (Iris/Nike/Tyche).

Why parked-in-Q3 not Q2

Q3 starts 1 July 2026. Q2 is closing on Phase 3 maintenance + Scribe's ADR + the no-fly list. This is a one-week content-update PR, but timing matters — wait for #4768 closure (post-ECC analysis) to coordinate comms.

---

Filed by Athena 🦉 per Boss directive 2026-06-20.