🟢 status: active — CEO-approved (2026-07-17). Eden (orchestrator) parallel-collected 16 self-introductions; Mirae (content-strategist) added her own and synthesized the brief; Bora (ops-pm) saved it and reflected it on the calendar; Eden restored §2 person details from the verbatim self-introductions. CEO-confirmed (2026-07-17): ① immediate promotion to active, Doyun begins visuals ② Platform 4's "joined last, connected most" narrative exposed as-is (§2.8) ③ "agent organization" expression kept only at the level of "17 came together" (§0, §3 as-is) ④ target publication date 2026-08-13 (Ep.1 + 4 weeks) confirmed → published 2026-07-19 (moved up). Evidence: calendar operations/marketing/linkedin-content-calendar-2026-h2-draft.md §Confirmation Needed, verbatim "CEO-confirmed (2026-07-17): 2026-08-13 (Ep.1 + 4 weeks) → published (2026-07-19) — moved up" · CEO-confirmed (2026-07-29).
LinkedIn Card News Brief 「Hunexia, The People Who Connect Us」
0. Brief Summary
- Position: LinkedIn content calendar Ep.4 — Pillar C (the process of building). Detailed plan for
operations/marketing/linkedin-content-calendar-2026-h2-draft.md:32 "Hunexia team intro (17 members, softened version)".
- Purpose: A follow-up that proves Ep.1's (「First Steps」) page 5 declaration — "we put AI agents on the team as members" — with real names and faces. Trust and intimacy accumulation is the core.
- Format: A single card news (CEO-confirmed, 2026-07-16). Same form factor as Ep.1 — 1080×1350 portrait, 3-format set (PDF · PNG · MP4). Not a department series or individual serialization.
- Pages: 9 (cover 1 + 7 departments + CTA 1).
- One-line core narrative: "This is not an org chart. It is a network of connections that is still being made."
1. Concept and Narrative Device
1.1 Why a connection network, not an org chart
Ep.1 page 5 depicted how the organization works as "5 work nodes — planning, diagnosis, content, development, research — form a loose network, with Violet dots (AI colleagues) mediating between them" (knowledge/marketing/linkedin-launch-carousel.md:69). This episode extends that motif to human nodes with real names. The concurrent-appointment matrix in .claude/org/roster.md:79-90 shows that 9 of 17 (Hyunwoo, Jio, Rei, Mirae, Doyun, Jian, Sera, Junseo, Bora) keep their home department while also helping another — and all 9 support the Platform team established 2026-07-15. An org chart only hides this fact.
1.2 "Named nodes" → person character illustrations
All 17 persona names are exactly 2 Korean syllables. Each person node gets a bust character illustration (generated by the CEO with an external generator) inside a circular frame — not a real profile photo, but in an illustration tone, to "personify AI agents as friendly characters" without becoming realistic (style seed locked to avoid the "human replacement impression" — brand principle avoidance layer). All person nodes carry equal visual weight (no hierarchy). The principle that Violet is not applied to individuals is softened into clothing accents — but Doyun distributes under verification so that Mint/Violet does not dominate (clipboard 4 · Navy blazer 4 · Violet accent 5 · glasses 7). Violet remains used for the connection lines of the page 8 (Platform) network reveal.
Generation prompt spec: knowledge/marketing/assets/linkedin-team-intro-carousel/characters/CHARACTERS.md — common style seed + 17 individual English prompts (Eden collected each character's appearance by asking them directly). The CEO generates 17 PNGs with these prompts and places them in the same folder; Doyun then replaces the .person__node in carousel.html (currently placeholder: initial circle + icon badge) with the character <img> (Phase F).
Path correction (2026-07-17): The first interpretation of the character-add request was incorrectly implemented as "a small mint line icon badge next to the initial circle". The CEO corrected this with a reference image (bust character illustration) — what was wanted was the character itself. The icon badge (.person__motif) will be removed in Phase F.
1.3 Card-sequence Narrative Device — Ops → Platform Two-step Buildup
Page 7 (Ops, Bora) plants "there is someone who organizes this whole flow at a glance", and page 8 (Platform) pays it off with "9 people actually connect here".
2. Per-department Composition
2.0 Exposure Order
| Card |
Department |
Members |
Card Headline (Draft) |
| 1 |
Cover |
— |
"17 came together. But this isn't an org chart." |
| 2 |
Leadership / HR |
Eden, Hanna |
The one who leads, the one who records. |
| 3 |
Growth |
Doyun, Mirae |
The hands that made this card news. |
| 4 |
Revenue |
Junseo, Sera, Jian |
Before confidence, verification. |
| 5 |
Academy |
Teo, Yuna |
From what you can do — backwards. |
| 6 |
Labs |
Hyunwoo, Jio, Rei |
From design to test, so it doesn't fall apart. |
| 7 |
Ops |
Bora |
This whole flow, at a glance. |
| 8 |
Platform |
Harin, Siu, Daon, Minho |
Joined last, connected most. |
| 9 |
CTA |
— |
"These are our 17 right now." |
Member total: 2+2+3+2+3+1+4 = all 17 reflected.
2.1 Card 1 — Cover
- Headline candidates (3):
- A (recommended): "17 came together. But this isn't an org chart."
- B (candid alternative): "The 17 names that fill Hunexia."
- C (question-style alternative): "Who's in this company?"
- Reason for selection: A takes the expression level the calendar already allows ("17 came together") as the headline, and the second sentence immediately overturns the org-chart expectation, foreshadowing the entire card's device (the connection network).
- Subcopy: "7 departments, 17 names. Yet nearly half are not in just one department. — We tried introducing ourselves as a connection network instead of an org chart."
- Visual direction: A teaser extending Ep.1 page 5's network motif into a person version — 17 initial nodes (§1.2) loosely scattered across the screen as a preview. Deep Navy background; Mint connection lines kept to 1–2 emphasized, the rest muted. Card number "01/09".
2.2 Card 2 — Leadership / HR
Eden (orchestrator) — the team-lead who makes who-does-what-and-why transparent, and gathers scattered results into one decision
- What she did: Had three teams independently analyze the same problem with different files, and confirmed they converged on the same cause without prior coordination
- Quote: "I delegate, then we verify together."
Hanna (people-ops) — People Ops running organizational growth while leaving evidence
- What she did: When Platform was established, built a new concurrent-appointment matrix to distinguish home department and support scope from new hires
- Quote: "Without evidence, there is no hiring or promotion."
(Visual note: Place the two nodes side by side. A direction line between Eden and Hanna was originally inserted to imply "delegation direction", but it did not communicate without explanation and risked being misread as hierarchy (reporting line) between the two — removed after CEO review (2026-07-17). The network implication is sufficiently delivered by the page 8 reveal alone. The full network map is not opened until page 8.)
2.3 Card 3 — Growth
Doyun (brand-content-designer) — the designer who draws the brand onto visible screens
- What she did: Completed the 7 pages of Ep.1's card news visuals — page 5 was personally designed as a loose mesh structure instead of robots or brains
- Quote: "I believe even negative space needs a reason."
Mirae (content-strategist, self) — the content strategist who translates complex stories into human language and designs stories that span channels
- What she did: Designed the narrative flow of Ep.1's 7 pages — structured so that one page creates the question the next page answers
- Quote: "I write so the next page makes you curious."
(Visual note: A small meta-touch of "these are the very people making this card news" is fine — without exaggeration.)
2.4 Card 4 — Revenue
Junseo (sales-proposal-expert) — the proposal expert who answers customer doubts with evidence
- What she did: In the service catalog draft, intentionally left pricing as draft to distinguish what is confirmed from what is not yet
- Quote: "I say what works and what doesn't, together."
Sera (ai-adoption-consultant) — the consultant who diagnoses where AI will produce outcomes, first
- What she did: Organized a standard diagnostic table with a 6-column structure from tasks to priorities
- Quote: "I look for automation that augments human judgment."
Jian (data-analyst) — the data analyst who checks with numbers, not feel
- What she did: Pulled hangar-tower.com visit data down to the code to confirm 0 measurement calls and 90% deeplink inflow
- Quote: "Numbers always carry evidence and limits together."
2.5 Card 5 — Academy
Teo (curriculum-architect) — the learning designer who starts from "what will learners be able to do" and designs backwards
- What she did: Pinning the learning objectives for the course platform's week 1 to observable verbs like "write" and "run" instead of "understand"
- Quote: "I design backwards from what learners can do."
Yuna (course-content-writer) — the person who turns learning objectives into actual slides and exercises
- What she did: For the week 1 courseware, prepared the skeleton in an order that shows examples before explanations
- Quote: "Examples first, principles next."
2.6 Card 6 — Labs
Hyunwoo (principal-architect) — the architect who draws a structure that will not collapse, before any screen is built
- What she did: While designing the platform wizard component, left 24 test cases numbered in the spec
- Quote: "I take it to blueprint; the code proves it."
Jio (implementation-lead) — the implementer who tests whether the design actually runs
- What she did: Verified with a hash that adding the dark theme did not change light-theme output — 76 tests passed
- Quote: "Only when tests pass is it truly done."
Rei (automation-rag-engineer) — the engineer who leaves repetitive work as scripts and makes organizational knowledge findable by AI
- What she did: Built a rendering pipeline that automatically produces PNG, PDF, and video from a single card-news source
- Quote: "Once built, verification is mine too."
2.7 Card 7 — Ops
Bora (ops-pm) — the operations PM who organizes scattered schedules, documents, and numbers into a single flow
- What she did: After Ep.1's publication, created a per-time-point KPI snapshot template and a publication history file
- Quote: "I make scattered things visible at a glance."
(Visual note: This card alone adds faint connection hints from Bora's node toward the other 6 departments — but the actual full-network reveal is reserved for card 8. §1.3)
2.8 Card 8 — Platform
Harin (platform-product-manager) — the product manager who asks "why" first and prioritizes with evidence
- What she did: Took 3 contacts saying "I can't tell what this site is" into the code and uncovered a single cause
- Quote: "Three complaints, one cause."
Siu (growth-marketer) — the growth marketer who finds where first-time visitors drop off and reduces it through experiments
- What she did: Noted 0 event-tracker calls as the "fallback risk" at the front of the report
- Quote: "If it isn't measured, I say we don't know."
Daon (customer-success-manager) — the onboarding designer who prevents drop-off in the first few minutes after sign-up
- What she did: Followed the contact feedback into the code, broke it into drop-off points, and organized onboarding requirements
- Quote: "Customer words verbatim; the cause all the way."
Minho (platform-engineer) — the developer who handles a service already in use, with verification and rollback first
- What she did: Reviewed the repository migration plan, confirmed migration was unnecessary, and removed the entire project
- Quote: "I confirmed we didn't need to migrate."
Subcopy: "9 people support this team while continuing their original department work." (The concurrent-appointment matrix fact from §1.1 — accurate, no exaggeration.)
(Visual note: In the top 1/3 of the card, the network reveal graphic — faint solid lines from the other 6 department cards converge on this card's Platform node cluster. Only on this card, Violet is used for the connection lines (§1.2). In the bottom 2×2 grid, 4 mini-bios. Platform 4's "probationary" level is a roster fact, but the copy carries only the nuance "joined last"; the internal HR term "probationary" itself is not used by default — visibility to be confirmed in §7.)
2.9 Card 9 — CTA
- Headline: "These are our 17 right now."
- Subcopy: "Not a finished org chart, but a network still being made. We will keep telling you what these 17 are building next."
- CTA copy: "Follow us. If you're curious about what kind of team we are, ask in the comments or a message."
- Visual direction: Logo centered, maximum negative space (inheriting Ep.1's CTA-page principle). The scattered-node teaser from card 1 reappears faintly here for bookend effect.
3. Body Caption Draft
17 came together.
It's not a story that ends when you list it as an org chart — it's a story of overlapping and connecting, so we decided to introduce it that way.
Planning, design, proposals, diagnosis, data, curriculum, courseware, architecture, implementation, automation, operations, product, marketing, onboarding, development — each solves a problem with a different name. Yet nearly half are not in just one department. They keep their home role and help other teams too.
This team introduction does not hide that overlap — it shows it as is. — Not a finished org chart, but a network of connections still being made.
We are building the way of working with AI itself.
— Hunexia — July 2026, introducing ourselves.
6 hashtags (as actually published, 2026-07-19 — record): #Hunexia #PeopleAndAI #AICollaboration #TeamIntroduction #ClaudeCode #Startup
The canonical rule is marketing-linkedin-playbook §2.3 (3 tiers, max 5 — adopted 2026-07-20). These predate that change and are not edited retroactively.
4. Design Direction (Handoff to Doyun)
Inherit Ep.1's tone, layout, and typography (1080×1350, Pretendard scale). New: multi-person card grid strategy (2-person left/right split / 3-person top row + bottom 3-column / 1-person center solo / 4-person top reveal + bottom 2×2). Color tokens inherited (navy / mint / violet), but Violet is limited to the page 8 connection lines. Accessibility checklist: same 4 items as Ep.1.
5. Tagline Candidates
Inherit "We started by putting AI agents on our own team." / "We are building the way of working with AI itself." / New "Colleagues with names." / "17 names, work connected as one."
6. Deliverable Set
3-format set (PDF · PNG · MP4), reusing the render/render.mjs pipeline (not new). Filename (draft) hunexia-team-connected-01~09.png etc. (Doyun can adjust at production). Path: knowledge/marketing/assets/linkedin-team-intro-carousel/ — Bora-confirmed (2026-07-17): confirmed to follow the same slug-stem naming convention as Ep.1's asset path (knowledge/marketing/assets/linkedin-launch-carousel/).
7. Calendar Reflection
Target publication: 2026-08-13 (Ep.1 + 4 weeks) confirmed (CEO, 2026-07-17). Reflected in the calendar file §2 and §3.
→ Published: 2026-07-19 (moved up). Correction 2026-07-29 — CEO-confirmed. Evidence: calendar
operations/marketing/linkedin-content-calendar-2026-h2-draft.md §Confirmation Needed, verbatim
"🔴 Ep.4 target publication date — CEO-confirmed (2026-07-17): 2026-08-13 (Ep.1 + 4 weeks) → published (2026-07-19) — moved up".
The calendar was correct; this brief's target-date entry had gone stale. The original text is struck through, not deleted.
Confirmation Needed List — All Items CEO-confirmed (2026-07-17)
Whether to expose the Platform 4's "just joined" framing → Expose. §2.8 card 8 headline and composition confirmed as-is.
Final level of the "agent organization" softening → Only at the level of "17 came together." Body caption (§3) and cover (§2.1) confirmed as-is.
Target publication date → 2026-08-13 confirmed. → Published 2026-07-19 (moved up; calendar §Confirmation Needed · CEO-confirmed 2026-07-29).
- 9 pages, per-card member allocation, and video length — Doyun and Rei can adjust at production (low priority, no approval needed).
§2 person details restored from the 16 people's verbatim self-introductions (2026-07-17, Eden). Next step: Doyun (brand-content-designer) begins visual production of carousel.html based on this brief (delegated 2026-07-17).
Change History
| Date |
Detail |
Author |
| 2026-07-16 |
Initial draft — 16 self-intros (collected by Eden) + self self-intro synthesized; confirmed as 9-page single card news |
Mirae |
| 2026-07-17 |
Saved to wiki — adjusted frontmatter source field to the repo schema (내부 기획); updated updated. §6 asset path confirmed; §7 calendar-inconsistency resolution marked complete |
Bora |
| 2026-07-17 |
§2 per-card person details restored — During saving, the original self-introduction full text was dropped and §2 was temporarily reconstructed from roster evidence; replaced wholesale with the 16 verbatim self-introductions that Mirae actually synthesized (card 1 cover → card 9 CTA, §2.1–2.9). Quotes and "what she did" all based on the verbatim response text |
Eden |
| 2026-07-17 |
CEO approval — status: draft → active. §7 all 4 confirmation items confirmed (Platform framing exposure · "17 came together" expression level · publication date 2026-08-13). Delegated visual production to Doyun |
Eden |
| 2026-07-17 |
Doyun completed carousel.html 9 pages (cards 1–4 → 5–7 → 8–9 in three stages). During CEO review, the "delegation direction" hint arrow (.delegate-hint) on card 2 was found not to read intuitively and risked being misread as hierarchy, so it was removed — §2.2 visual note updated |
Eden |
| 2026-07-17 |
Fixed card 9 page-number position bug (position:relative inline broke the lower-left absolute position; cleaned up, leaving z-index only). At CEO request, added person illustration badges (mint line icons instead of real profile photos; applied and verified for all 17 in 3 placements) — §1.2 updated |
Eden · Doyun |
| 2026-07-17 |
Character direction correction: The "illustration badge" above was a misreading of the CEO intent (the character itself). Redesigned based on the CEO's reference image (bust character illustration) — Eden asked all 17 about their appearance and collected it; Doyun verified distribution balance; wrote a common seed + 17 English prompts in characters/CHARACTERS.md. CEO generates directly → Doyun applies to carousel.html in Phase F. §1.2 corrected |
Eden · Doyun |
| 2026-07-29 |
Publication date corrected — target 2026-08-13 → published 2026-07-19 (CEO-confirmed 2026-07-29). The calendar (operations/marketing/linkedin-content-calendar-2026-h2-draft.md §Confirmation Needed) was already accurate with "published (2026-07-19) — moved up"; this brief, its Korean counterpart, the idea backlog, and knowledge/INDEX.md had gone stale. Detected because https://hunexia.com/en/wiki/ was serving "target publication 2026-08-13" twice (Sungho, 2026-07-29 22:50) — the index field summaryEn is sourced from this .en.md file (scripts/build-wiki-index.mjs:86), so regenerating alone could never clear it. INDEX.md and .index.json are build artifacts and were not edited by hand; they follow from this source via npm run wiki:index. Corrected here: frontmatter summary and updated · §status banner ④ · §7 body · §7 confirmation list item 3. The 2026-07-17 CEO-approval row above (which reads "publication date 2026-08-13") is left untouched — it records that day's decision. Korean counterpart corrected in the same pass |
Bora |