Operating Model (Invocation, Delegation)
How the agent organization runs. The CEO → team-lead → expert invocation flow, delegation rules, and the authority boundary between day-to-day work and HR changes.
Hunexia works with a human CEO and an AI agent organization.
CEO (human) → team-lead orchestrator (Eden) → experts. HR is run by people-ops (Hanna).
| Department | Agent (persona) — Role |
|---|---|
| Leadership / HR | orchestrator (Eden) dispatch, synthesis, hiring manager · people-ops (Hanna) hiring, performance, evolution |
| Growth | content-strategist (Mirae) blog, social, YouTube · brand-content-designer (Doyun) card news, thumbnails, landing |
| Revenue | sales-proposal-expert (Junseo) proposals, RFPs · ai-adoption-consultant (Sera) adoption diagnosis, automation opportunities · data-analyst (Jian) data analysis, reports, ROI |
| Academy | curriculum-architect (Teo) curriculum and assessment design · course-content-writer (Yuna) slides, courseware, exercises |
| Labs | principal-architect (Hyunwoo) design → implementation-lead (Jio) implementation → code-reviewer review · automation-rag-engineer (Rei) automation, RAG |
| Ops | ops-pm (Bora) projects, schedules, documents, research |
| Platform | platform-product-manager (Harin) roadmap, backlog, PRD · growth-marketer (Siu) funnel, experiments · customer-success-manager (Daon) onboarding, cases · platform-engineer (Minho) platform code, operations |
Each agent has a unique persona (SOUL 4-part: Identity / Style / Avoid / Defaults). Roster: .claude/org/roster.md.
A dedicated department for the company's first product, the mini-project platform (hangar-tower.com). Established by CEO directive as the organization's first product-dedicated structure.
.claude/org/roster.md.principal-architect (design) → implementation-lead (implementation) → code-reviewer (review). Design and implementation are separated to protect quality.
The same applies to the Platform engineering team: Hyunwoo (design) → platform-engineer (Minho, implementation) → code-reviewer (review).
Package and repository assets have design and technical owners separate from department affiliation. Design decisions = design owner; code / build / deploy = technical owner.
@hunexia/design-system (this repo §6): Design owner brand-content-designer (Doyun) — token system, color, typography, dark-mode design, etc. (design decisions). Technical owner Labs chain (principal-architect Hyunwoo → implementation-lead Jio) — token JSON, component code, build pipeline. npm release deferred until the external web service launches.web/ (company homepage landing / + wiki /wiki, §5 · §8): Role-split (CEO-confirmed 2026-07-17, different from the DS dual model because it is a complex asset) — content owners brand-content-designer (Doyun, visuals) and content-strategist (Mirae, copy), technical owner Labs (implementation-lead Jio), infrastructure = CEO, operations owner = ops-pm. Public release deferred (pending CEO infrastructure discussion).Details and roster: .claude/org/roster.md Asset Ownership table.
How the agent organization runs. The CEO → team-lead → expert invocation flow, delegation rules, and the authority boundary between day-to-day work and HR changes.
The HR system for the agent organization. Procedures for hiring, performance review, and career levels, with CEO approval gates. Every organizational change is recorded as a git commit.
A curated recommendation for fitting the global skill ecosystem to Hunexia's real practice. Classifies into Tier 1 (adopt now), Tier 2 (conditional), and not-recommended, with MCP authentication/installation status and the unified code-review standard.