Wiki Usage Guide

The operating guide for the Hunexia in-house knowledge wiki. It holds the rules that maintain a single source of truth.

Structure

knowledge/<category>/<slug>.md. Categories: brand · company · offering · marketing · cases · process · org · _meta.

Document Schema (YAML frontmatter, required)

title · slug (globally unique, lowercase ASCII) · category · tags[] (2–7) · owner · status (active|draft|stub|deprecated, completeness axis) · artifact (real|sample, artifact-status axis — decision rule per knowledge/org/governance.md:89: "Decision rule: if the content's source is a real target (…) then real; if it is an invented example or validation fixture, then sample. If unclear, sample (safe side)") · summary (1–2 sentences, the search snippet) · updated (YYYY-MM-DD) · source (내부 기획|외부:URL|commit:sha|대표 결정|추정(미검증)). Optional: related[], subcategory.

The three axes have different roles — status = how complete · artifact = is the content's source real or invented · source = where it came from. Coexistence is normal (e.g., status: draft + artifact: real = the content is a real case but still a draft). artifact: real is a ceiling, not a guarantee — it speaks to the source of the whole document; it does not guarantee that individual numbers in the body are citable. It does not replace per-sentence status tagging (citation whitelists, [measurement pending], etc.).

Slug Rules

<category>-<filename-stem>, lowercase. Example: brand/identity-plan.md → slug: brand-identity-plan. Globally unique. npm run wiki:check verifies the match.

Naming Rules

• Directories and files: English slug-form singular nouns. Body: the document's own language. (Avoids glob/ripgrep instability from Korean NFD normalization.)
• No numeric prefixes. Order is controlled by INDEX.md (auto-generated).
• _* prefix files (e.g., cases/_template.md) and INDEX.md are excluded from indexing (helpers / generated).

Build and Verification

• npm run wiki:index → knowledge/INDEX.md (human table of contents) + knowledge/.index.json (machine cache, shared by skills and web). Commit target.
• npm run wiki:check → schema gate (the equivalent of typecheck). Checks required fields, slug rules, category enum, and owner.

Information Promotion (Hierarchy)

.remember/ (volatile session) → .claude/org/reviews/<name>.md (per-agent persistent) → knowledge/ (verified team fact). Promotion conditions (one or more): ① reproduced 2+ times ② "a fact the whole team must know" ③ session note survives 1+ day and shows value.

Regression-test Scenarios (Re-run When Skills or Schema Change)

1. Tag matching: "What's the brand slogan?" → brand/identity-plan.md ranks #1 → "Connecting Human Potential with AI" cited.
2. Category + multi-document: "Labs development chain?" → 2 hits in org/ → "principal-architect → implementation-lead → code-reviewer".
3. Honest response when no evidence: "Give me the AI coding training price list." → offering/pricing.md (stub) → "No defined price list (placeholder only). Owner confirmation recommended."

Two Views

• Q&A: The skill /wiki (agents / CEO, in a Claude Code session).
• Browsing and search: The static site web/ (Vercel). Consumes the same knowledge/ and .index.json.