✅ status: active — CEO-approved (2026-07-16). Recommendations accepted: goal = awareness · core message confirmed · publication in July · serialization. Doyun (brand-content-designer) begins the 6-page visual → publish after completion.

LinkedIn Card News Brief 「Hunexia, First Steps」

0. Brief Summary

• Series name: Hunexia — First Steps
• Purpose: The first official external declaration of the company's existence and direction (awareness-focused)
• Format: LinkedIn PDF card news (document carousel) — reflects that document posts are the top format on 2026 LinkedIn, with an average 6.6% engagement rate
• Pages: 7 (option C confirmed, 2026-07-16). Original 6 + new page 5 (how we work · dogfooding). Sequence: question → diagnosis → perspective → identity → how we work (new) → business → invitation.
• Size: 1080×1350 (portrait, optimized for mobile feed) recommended
• One-line core narrative: "A company has started that is less concerned with what to use AI for, and more with how to attach it reliably to real practice."

1. Per-page Composition

Page 1 — Cover / Hook

• Role: Stop the feed scroll. Compress the message.
• Headline candidates (3):
  • A (recommended main): "We ask less 'what can we do with AI' and more 'how can we attach it to real practice.'"
  • B (candid alternative): "Connecting human potential with AI. — Hunexia's first step."
  • C (softened curiosity): "There's an AI company that starts a little differently."
  • Reason for selection: A takes the language the ICP actually uses ("how to attach AI reliably to real practice") and makes the target reader stop and think "this is our story." B is the orthodox declarative form; C is weaker as a hook but useful when candor is preferred.
• Subcopy: "Hunexia — July 2026, first steps."
• Visual direction:
  • Deep Navy dark background; anchor the logo (H×X symbol) small at lower left or lower right
  • Wide negative space for the headline, left-aligned
  • A single Mint accent line (underline or short horizontal) to focus attention
  • Strictly prohibited: neon gradients, clichéd robot / brain / infinity imagery, cold machine aesthetics

Page 2 — Problem Diagnosis (in the reader's language)

• Role: Identify the reader and build empathy for "why we started this company."
• Headline: "Most start here. — 'What can we do with AI?'"
• Subcopy: "But any organization that has tried to attach AI to real practice even once asks a different question. 'How can we use it reliably, verifiably, alongside human judgment?' We started from that second question."
• Visual direction: Contrast layout between the two questions. The upper question in gray/muted (skeptical, abstract nuance); the lower in Mint accent and heavier weight. A transition arrow or marker in the middle.

Page 3 — Our Perspective (Philosophy)

• Role: Declare the human-centric philosophy. Pre-empt the "human replacement" misunderstanding.
• Headline: "AI does not replace people. It augments human judgment."
• Subcopy: "Reduce repetitive work, support decisions, and let people focus on more human work. We put the people who work with the technology first, not just the technology."
• Visual direction: A brand graphic motif in which two nodes meet at a central connection point (network / connecting line). One node is Navy, one is Mint, the connection is Violet. The direction of "people and AI facing each other" from the brand identity plan §8.2. Strictly prohibited: handshake between robot and human hands.

Page 4 — About Hunexia (Identity)

• Role: State the company name, mission, and slogan cleanly.
• Headline: "Hunexia. Human + Nexus + AI."
• Subcopy: "The connection point where people and AI meet. We build the technology and experiences that let people and AI collaborate naturally."
• Caption (small): "Connecting Human Potential with AI"
• Visual direction: A typographic graphic decoding the name (a structure in which Human + Nexus + AI combine into Hunexia). Wordmark centered, Mint/Violet accents. Aim for "what the name means" rather than a "planting a flag" feeling.

Page 5 — How Our Organization Works (Dogfooding) — New (Option C, 2026-07-16)

• Role: An evidence page that "human-centric" is not just words. Supports the page 4 (identity) declaration with practice. Paired with page 3 (perspective / philosophy) to form a philosophy → evidence triplet.
• Headline candidates (3):
  • A (CEO-confirmed 2026-07-16): "If 'human-centric' is not to be just words, we believed our own organization had to move that way first."
  • B (declarative alternative): "From day one, Hunexia works with AI agents as team members."
  • C (concrete daily alternative): "Planning, diagnosis, content design, development, research — we coordinate the day alongside AI colleagues."
• Subcopy: "So from the start, Hunexia has worked with AI agents alongside us as team members. Planning and diagnosis, content design, development, and research — we coordinate the day with AI colleagues each holding their own role. The operating rhythm, logo, and design system were also built within this collaboration from the start. — This is not a polished showcase; it is a process we are still building."
• Visual direction: Must differentiate from page 3 (1:1 abstract relation) — multiple work nodes (planning, diagnosis, content, development, research — 5) form a loose network, with Violet dots (AI colleagues) mediating between them. Background var(--hx-surface). Navy = human work nodes, Mint = connection, Violet = AI mediation points. Strictly prohibited: people-count vs AI-count contrast ("humans N / AI M") · org-chart hierarchy (with "employment" nuance) · robots, brains, infinity symbols.

Page 6 — What We Do (Business Areas)

• Role: Show the scope of activity broadly; do not mention specific packages or prices (draft status).
• Headline: "AI applied in real practice. Verifiable automation."
• Subcopy (as chip / icon grid): Place the following 5 with line icons
  • AI collaboration and coding training (Academy area)
  • Enterprise AI adoption diagnosis and consulting
  • Workplace automation and AI agents
  • RAG / organizational knowledge connection
  • Prompt and context engineering
• Closing line: "Tying education and technology implementation on one axis — designing the way an organization works with AI itself."
• Visual direction: 2×3 or 1×5 chip grid. Line icons (per brand §11.3 — linear, consistent stroke). No 3D / dimensional icons.

Page 7 — CTA (Invitation)

• Role: Encourage follow, comment, DM. An invitation tone, not aggressive marketing.
• Headline: "We've taken the first step. Build it with us."
• Subcopy: "We are not yet at the stage of talking about flashy results. But we know where we are going. — We will share practical insights, the process of building, and stories of people and AI collaborating."
• CTA copy: "Follow us. If something resonates, let's talk in the comments or a message."
• Visual direction: Logo centered, maximum negative space. A short Mint line to imply "direction of travel". Aggressive buttons / red arrows / exaggerated emblems strictly prohibited.

2. Narrative Flow Across Cards

Question (1) → Diagnosis (2) → Perspective (3) → Identity (4) → How we work (5, new) → Practice (6) → Invitation (7). Designed so that one page creates the question the next page answers:

• Page 1 creates "What do you mean, started differently?" → page 2 answers
• Page 2 creates "Then what's your perspective?" → page 3 answers
• Page 3 creates "Who are you?" → page 4 answers
• Page 4 creates "Human-centric in words only, really?" → page 5 answers (dogfooding evidence)
• Page 5 creates "What do you actually do?" → page 6 answers
• Page 6 creates "How can we be part of it?" → page 7 invites

This keeps the reader turning pages because "I want to see what's next" (secures dwell time → acts as an engagement signal in the 2026 algorithm).

3. LinkedIn Post Body Caption (CEO-approved — Option B, benchmarking CEO style, 2026-07-16)

We ask less "what can we do with AI" and more "how can we attach it reliably to real practice."

Hunexia is an organization where a human CEO and AI agents work together. Planning, content, development, education — in each area, AI participates as a team member. People own direction and judgment; AI owns execution and review.

🤝 The way we collaborate every day is itself what we offer. AI does not replace people, nor does it do everything automatically. In a direction that augments human judgment, we move forward — verifying in real practice.

— Hunexia — July 2026, voluntarily.

Benchmarking basis: Cross-analysis of 2 samples of the CEO's LinkedIn posts — the "not A but B" contrast-declaration opening (common) + sample 1 (minimal declaration) skeleton + sample 2 (structured) paragraph breaks. Hashtags follow the CEO style (none in body).

8 hashtags — intent: #ClaudeCode and #RAG reach the relevant practitioner communities (a topic-authority signal in the 2026 algorithm); #PeopleAndAI and #AICollaboration align with the brand message; #StartupLaunch ties to the launch timing context. These 8 are the record of what was actually published on 2026-07-16.

The canonical rule is marketing-linkedin-playbook §2.3 (3 tiers, max 5 — adopted 2026-07-20). The 8 above predate that change and are not edited retroactively; later episodes follow §2.3.

4. Design Direction (Handoff to Doyun, brand-content-designer)

Tone

• Professional yet warm; technical yet human-centric. Neon / cyberpunk / cold machine aesthetics are strictly prohibited (brand §7.2, §12.3).
• A "quiet but clear first greeting" rather than a "planting the flag" declaration. Exclude exaggerated / provocative card-news conventions (red arrows, "shocking", excessive exclamation marks).

Layout Principles

• Size: 1080×1350 (portrait). One page visible in the mobile feed without scrolling.
• Negative space: 80–96px left/right, 96–120px top/bottom. No clutter.
• Alignment: Left-align by default (headline). Same alignment across cards for consistency.
• Card number: Lower-right or lower-left, small "01 / 07" (Pretendard Regular, muted) — option C, 7-page system.

Typography Scale (Pretendard-based, mapped to --hx-* tokens)

• Headline: Pretendard Bold, ≈56–64pt → var(--hx-text-display) or var(--hx-text-h1)
• Main subcopy: Pretendard Medium/SemiBold, ≈28–32pt → var(--hx-text-h2) or var(--hx-text-h3)
• Body: Pretendard Regular, ≈22–24pt → var(--hx-text-body)
• Caption / card number: Pretendard Regular, ≈16–18pt → var(--hx-text-caption)
• Emphasis on technical terms / token names: JetBrains Mono where applicable

Color Token Mapping (@hunexia/design-system semantic + ramp)

Use	Token	Value
Background (dark page)	var(--hx-navy-900)	dark navy — trust, declaration
Background (light page)	var(--hx-surface)	surface — body readability
Headline / emphasis (light page)	var(--hx-content)	default body color
Headline / emphasis (dark page)	var(--hx-content-inverse)	for navy background
Accent / connection	var(--hx-accent) (Mint family)	#16BBA0 — growth, possibility
AI / intelligence node	var(--hx-violet-500) or ramp	#8B7CF0 — AI symbol
Secondary / caption	var(--hx-muted)	muted text
Divider	var(--hx-line)	subtle divider

• Mint is limited to 1–2 points per page (no excess, to avoid a neon feel).
• Violet is used only for elements carrying an "AI" meaning.
• Light theme only; no dark-mode variant needed.

Mint Accent Mapping Rule (what — where the accent goes, added 2026-07-16)

Recurrence prevention: On Ep.1 page 1, the Mint accent was placed on the closing phrase ("we ask") by mistake and moved to the core message ("how to attach AI to real practice"). The lesson: do not stop at "let's add a Mint"; specify which word it lands on.

• Mint accent = only on the core differentiating message / core noun phrase / core question.
  • Examples: "how to attach AI to real practice" (page 1), "augment" (page 3), "had to move that way" (page 5).
• No accent on closing phrases, particles, or auxiliary verbs (e.g., "we ask", "is", "~does"). These use the body color (light page = content, dark page = on-brand white).
• In a "not A, but B" contrast, Mint goes on the contrasted core value (B). The pre-value (A) before "not" is muted/gray to bring out the contrast.

Graphic Motifs

• Allowed: The connecting-line · node · intersection · expansion-structure motifs in brand identity §11.1.
• Prohibited: Robot-hand-meets-human-hand, brain shapes, simple use of the infinity symbol, neon cyberpunk, future cities disconnected from reality.

Accessibility / Verification Checklist (Before Doyun Handoff)

• Headline-to-background contrast meets WCAG AA
• Verify the headline fits within 2 lines at a 375px mobile viewport
• Verify the message reads when the thumbnail (page 1) is 50% cropped in the feed
• Verify hierarchy is maintained in monochrome print
• Verify the Mint accent lands on a core keyword (differentiating message) — check that accents are absent from closing phrases and particles (accent mapping rule §4, 2026-07-16)

---

5. Core Message Tagline Candidates (Pending CEO Selection, 2026-07-16)

Core: "A company built with AI — with AI agents as team members." "Built with AI" is softened to avoid subject confusion (the impression that AI, not people, built the company). 5 candidates (written by Mirae); the CEO picks one per use.

#	Phrase	Use	Tone
1	"A company founded by people, an organization that works with AI agents."	Slogan type — about page · business card · company profile sub	Most honest. Avoids "built with AI" exaggeration and subject confusion
2 ✅	"We started by putting AI agents on our own team."	Adopted — new page 5 accent line	Compresses the dogfooding essence. "We started by" = the weight of practice
3	"We practice 'human-centric' — even ourselves."	Caption hook · series recurring opener	The paradoxical trust of "even ourselves". States the process nature
4 ✅	"We are building the way of working with AI itself."	Adopted — series tagline (consistent across blog, YouTube)	Aligns with the core + the differentiator of "way design". Most versatile
5	"From AI as a tool, to AI as a teammate."	Card accent · bridge between page 3 ↔ page 5	The "tool → teammate" transition direction. Avoids binary denial

✅ CEO-confirmed (2026-07-16): Headline A + taglines 2 (new page 5 accent line) and 4 (series tagline). Reflected in Doyun's visual (new page 5).

---

6. Deliverables — 3-format Set (Card-news Standard, Derived from a Single Source)

One card news = a standard 3-format set (PDF, image, video). Derived from a single source (carousel.html) for reuse across LinkedIn, blog, Instagram, YouTube, email, and company profile. Location: knowledge/marketing/assets/linkedin-launch-carousel/.

Format	File	Spec	Use
Image	hunexia-first-steps-01~07.png	1080×1350 PNG-24, 7 pages	LinkedIn image carousel · Instagram · social
PDF	hunexia-first-steps.pdf	1080×1350 7 pages	Company profile · blog · email · print
Video	hunexia-first-steps.mp4	1080×1350 4:5, 28 seconds, H.264, silent	LinkedIn video · Instagram feed · YouTube Shorts

• Single source: carousel.html (re-rendering produces all 3 — one source of truth).
• Rendering pipeline: render/render.mjs (Puppeteer + ffmpeg). Future episodes (Ep.2–4) can re-render via the same pipeline.
• Copy compression (2 sentences) applied to 5 pages in the video only — confirmed by Mirae (content-strategist). Image and PDF keep the original 4 sentences.
• BGM: Silent first cut (if the CEO decides, an ffmpeg mix line can add it).
• Review: Doyun (brand-content-designer) visual review pass — copy-compression balance, tone, and color confirmed. (Initial 9:16 padded version → CEO feedback removed ~30% top/bottom padding, switched to 4:5 unpadded — 2026-07-16)
• PDF metadata: Title="Hunexia — First Steps" included. Author is omitted due to a Chrome headless limitation (kept as-is per CEO approval 2026-07-16; if needed, post-process via exiftool -Author=Hunexia).
• BGM: Silence confirmed (CEO-approved 2026-07-16). If music is added, an ffmpeg mix line can produce a separate version.