KLMS — Organization Chart

This document defines how KLMS is organized into units and which agents lead and staff them. It is the single source of truth for “who owns what.”

Status: v13 — twenty-one units across five reporting clusters plus direct-to-Principal units and staff. Includes all units hired through the 2026-05-30 staffing round. Mentor role offboarded 2026-05-31. Delivery (PMO) and Operations units moved into the COO cluster 2026-05-31 — COO now supervises four units: Delivery, Operations, Security & Privacy, Quality & Risk. C-suite executive layer (CPTO, COO, CGEO) added to roster and chart 2026-05-31; CGEO renamed from chief-growth-engagement-officer to chief-growth-experience-officer 2026-05-31. Video Producer / Script Writer added to Growth unit 2026-05-31. Wave B+C staffing plan executed — 8 agents hired 2026-05-31: Instructional Designer, UX Designer, UX Research Associate (Design Research); Product Manager (new Product unit); Platform Engineer (Engineering); AI Engineer (AI Systems); Analytics Engineer (Data & Analytics); Site Reliability Engineer (Operations).

Chart

graph TD
    K["Kevin Wong<br/><i>Founder / Principal</i>"]
    PA["Personal Assistant<br/><i>Claude Code agent · staff to the Principal</i>"]
    EXT["External Review Partners<br/><i>retained advisor · independent external reviews</i>"]

    subgraph ARCHIVES["The Archives — Unit"]
        ARCHIVIST["Archivist<br/><i>Unit Lead</i>"]
        HISTORIAN["Historian<br/><i>member</i>"]
        ARCHIVIST --> HISTORIAN
    end

    subgraph GOV["Rules &amp; Governance — Unit"]
        GOLDEN["Golden Rule<br/><i>Unit Lead</i>"]
    end

    subgraph HRU["Human Resources — Unit"]
        HR["Human Resources<br/><i>Unit Lead</i>"]
    end

    subgraph DOCS["Documentation — Unit"]
        DOC["Documentarian<br/><i>Unit Lead</i>"]
    end

    subgraph FIN["Finance — Unit"]
        FIND["Finance Director<br/><i>Unit Lead</i>"]
        FANA["Financial Analyst<br/><i>member</i>"]
        FIND --> FANA
    end

    subgraph LAW["Legal &amp; Compliance — Unit"]
        LEGD["Legal Director<br/><i>Unit Lead</i>"]
        COMP["Compliance Analyst<br/><i>member</i>"]
        LEGD --> COMP
    end

    CPTO_NODE["Chief Product &amp; Technology Officer (CPTO)<br/><i>Claude Code agent · C-suite</i>"]
    COO_NODE["Chief Operating Officer (COO)<br/><i>Claude Code agent · C-suite</i>"]
    CGEO_NODE["Chief Growth &amp; Experience Officer (CGEO)<br/><i>Claude Code agent · C-suite</i>"]

    subgraph CPTO_CLUSTER["CPTO Cluster"]
        subgraph INNO["Innovation — Strategy &amp; Research — Unit"]
            INNOD["Innovation Director<br/><i>Unit Lead</i>"]
            CIA["Competitive Intelligence Analyst<br/><i>member</i>"]
            INNOD --> CIA
        end
        subgraph DR["Design Research — Unit"]
            DRD["Design Research Director<br/><i>Unit Lead</i>"]
            INSTD["Instructional Designer<br/><i>member</i>"]
            UXD["UX Designer<br/><i>member</i>"]
            UXR["UX Research Associate<br/><i>member</i>"]
            DRD --> INSTD
            DRD --> UXD
            DRD --> UXR
        end
        subgraph ENG["Engineering — Unit"]
            ENGD["Engineering Director<br/><i>Unit Lead</i>"]
            SE["Staff Engineer<br/><i>member</i>"]
            PLATE["Platform Engineer<br/><i>member</i>"]
            ENGD --> SE
            ENGD --> PLATE
        end
        subgraph DA["Data &amp; Analytics — Unit"]
            DAD["Data &amp; Analytics Director<br/><i>Unit Lead</i>"]
            AE["Analytics Engineer<br/><i>member</i>"]
            DAD --> AE
        end
        subgraph AIS["AI Systems — Unit"]
            AISD["AI Systems Director<br/><i>Unit Lead</i>"]
            AIE["AI Engineer<br/><i>member</i>"]
            AISD --> AIE
        end
        subgraph PROD["Product — Unit"]
            PRODMGR["Product Manager<br/><i>Unit Lead</i>"]
        end
    end

    subgraph COO_CLUSTER["COO Cluster"]
        subgraph DELIVERY["Delivery (PMO) — Unit"]
            PM["Project Manager<br/><i>Unit Lead</i>"]
        end
        subgraph OPS["Operations — Unit"]
            PROC["Process Engineer<br/><i>Unit Lead</i>"]
            SRE["Site Reliability Engineer<br/><i>member</i>"]
            PROC --> SRE
        end
        subgraph SEC["Security &amp; Privacy — Unit"]
            SECD["Security Director<br/><i>Unit Lead</i>"]
            SECA["Security Analyst<br/><i>member</i>"]
            SECD --> SECA
        end
        subgraph QR["Quality &amp; Risk — Unit"]
            QRD["Quality &amp; Risk Director<br/><i>Unit Lead</i>"]
        end
    end

    subgraph CGEO_CLUSTER["CGEO Cluster"]
        subgraph GRW["Growth — Unit"]
            GRWD["Growth Director<br/><i>Unit Lead</i>"]
            CS["Content Strategist<br/><i>member</i>"]
            VP["Video Producer / Script Writer<br/><i>member</i>"]
            GRWD --> CS
            GRWD --> VP
        end
        subgraph CUS["Customer Success — Unit"]
            CSD["Customer Success Director<br/><i>Unit Lead</i>"]
            CM["Community Manager<br/><i>member</i>"]
            CSD --> CM
        end
        subgraph CRE["Creative — Brand &amp; Marketing — Unit"]
            CRED["Creative Director<br/><i>Unit Lead</i>"]
            BS["Brand Strategist<br/><i>member</i>"]
            VD["Visual Designer<br/><i>member</i>"]
            CRED --> BS
            CRED --> VD
        end
    end

    K --- PA
    K -.-> EXT
    K --> ARCHIVIST
    K --> GOLDEN
    K --> HR
    K --> DOC
    K --> FIND
    K --> LEGD
    K --> CPTO_NODE
    K --> COO_NODE
    K --> CGEO_NODE
    CPTO_NODE --> CPTO_CLUSTER
    COO_NODE --> COO_CLUSTER
    CGEO_NODE --> CGEO_CLUSTER

    classDef principal fill:#1f2937,color:#fff,stroke:#111;
    classDef lead fill:#2563eb,color:#fff,stroke:#1e40af;
    classDef csuite fill:#6d28d9,color:#fff,stroke:#4c1d95;
    classDef staff fill:#7c3aed,color:#fff,stroke:#5b21b6;
    classDef member fill:#60a5fa,color:#082f49,stroke:#2563eb;
    classDef external fill:#0f766e,color:#fff,stroke:#134e4a,stroke-dasharray:5 3;
    class K principal;
    class ARCHIVIST,GOLDEN,HR,DOC,FIND,LEGD,INNOD,DRD,ENGD,DAD,AISD,PRODMGR,PM,PROC,SECD,QRD,GRWD,CSD,CRED lead;
    class CPTO_NODE,COO_NODE,CGEO_NODE csuite;
    class PA staff;
    class HISTORIAN,FANA,COMP,CIA,SE,PLATE,INSTD,UXD,UXR,AE,AIE,SECA,SRE,CS,VP,CM,BS,VD member;
    class EXT external;

Text fallback:

Kevin Wong (Founder / Principal)
│   ├─ Personal Assistant — Claude Code agent (staff to the Principal)
┊   └┄ External Review Partners — retained advisor (independent external reviews)
│
├── The Archives (Unit)
│   ├── Archivist — Claude Code agent (Unit Lead)
│   └── Historian — Claude Code agent (member)
├── Rules & Governance (Unit)
│   └── Golden Rule — Claude Code agent (Unit Lead)
├── Human Resources (Unit)
│   └── Human Resources — Claude Code agent (Unit Lead)
├── Documentation (Unit)
│   └── Documentarian — Claude Code agent (Unit Lead)
├── Finance (Unit)
│   ├── Finance Director — Claude Code agent (Unit Lead)
│   └── Financial Analyst — Claude Code agent (member)
├── Legal & Compliance (Unit)
│   ├── Legal Director — Claude Code agent (Unit Lead)
│   └── Compliance Analyst — Claude Code agent (member)
│
├── Chief Product & Technology Officer (CPTO) — Claude Code agent (C-suite)
│   └── CPTO Cluster
│       ├── Innovation — Strategy & Research (Unit)
│       │   ├── Innovation Director — Claude Code agent (Unit Lead)
│       │   └── Competitive Intelligence Analyst — Claude Code agent (member)
│       ├── Design Research (Unit)
│       │   ├── Design Research Director — Claude Code agent (Unit Lead)
│       │   ├── Instructional Designer — Claude Code agent (member)
│       │   ├── UX Designer — Claude Code agent (member)
│       │   └── UX Research Associate — Claude Code agent (member)
│       ├── Engineering (Unit)
│       │   ├── Engineering Director — Claude Code agent (Unit Lead)
│       │   ├── Staff Engineer — Claude Code agent (member)
│       │   └── Platform Engineer — Claude Code agent (member)
│       ├── Data & Analytics (Unit)
│       │   ├── Data & Analytics Director — Claude Code agent (Unit Lead)
│       │   └── Analytics Engineer — Claude Code agent (member)
│       ├── AI Systems (Unit)
│       │   ├── AI Systems Director — Claude Code agent (Unit Lead)
│       │   └── AI Engineer — Claude Code agent (member)
│       └── Product (Unit)
│           └── Product Manager — Claude Code agent (Unit Lead)
│
├── Chief Operating Officer (COO) — Claude Code agent (C-suite)
│   └── COO Cluster
│       ├── Delivery / PMO (Unit)
│       │   └── Project Manager — Claude Code agent (Unit Lead)
│       ├── Operations (Unit)
│       │   ├── Process Engineer — Claude Code agent (Unit Lead)
│       │   └── Site Reliability Engineer — Claude Code agent (member)
│       ├── Security & Privacy (Unit)
│       │   ├── Security Director — Claude Code agent (Unit Lead)
│       │   └── Security Analyst — Claude Code agent (member)
│       └── Quality & Risk (Unit)
│           └── Quality & Risk Director — Claude Code agent (Unit Lead)
│
└── Chief Growth & Experience Officer (CGEO) — Claude Code agent (C-suite)
    └── CGEO Cluster
        ├── Growth (Unit)
        │   ├── Growth Director — Claude Code agent (Unit Lead)
        │   ├── Content Strategist — Claude Code agent (member)
        │   └── Video Producer / Script Writer — Claude Code agent (member)
        ├── Customer Success (Unit)
        │   ├── Customer Success Director — Claude Code agent (Unit Lead)
        │   └── Community Manager — Claude Code agent (member)
        └── Creative — Brand & Marketing (Unit)
            ├── Creative Director — Claude Code agent (Unit Lead)
            ├── Brand Strategist — Claude Code agent (member)
            └── Visual Designer — Claude Code agent (member)

Top of organization

• Kevin Wong — Founder / Principal. Sets direction, defines what is authoritative, and creates new units. All units report up to here.
• Personal Assistant (Claude Code agent) — .claude/agents/personal-assistant.md. Direct staff to the Principal (not a functional unit). Captures and triages Kevin Wong’s requests, delegates work to Unit Leads on the Principal’s behalf, prepares briefs/decisions, tracks open threads, and handles logistics.
  • Exclusive access: the PA is the only agent permitted to access the Principal’s personal information (e.g. personal email, calendar, files, and records). No other agent may access it; they route any such need through the PA. Personal information is private to the PA and is not part of the archived project record (see The Archives, below).

External advisors (on retainer)

External parties engaged on retainer — not employees, independent, reporting to the Principal.

• External Review Partners (.claude/agents/external-reviewer.md) — an elite independent consultancy on permanent retainer. Performs independent external reviews (360-degree reviews, governance/process audits, risk assessments) and delivers written reports under reviews/. Read-only on the org; bound by the personal-information exclusion (PA-only). Reports to the Principal.

Clusters

The CPTO, COO, and CGEO clusters are reporting/coordination groups — groupings of related units that operate together under a common strategic axis. Each cluster is led by a dedicated C-suite executive agent reporting directly to the Principal. Unit Leads within a cluster report to their cluster’s C-suite head and escalate cross-cluster matters to the Principal through that head.

• CPTO cluster — led by the Chief Product & Technology Officer (.claude/agents/chief-product-technology-officer.md). Units: Innovation, Design Research, Engineering, Data & Analytics, AI Systems, Product.
• COO cluster — led by the Chief Operating Officer (.claude/agents/chief-operating-officer.md). Units: Delivery (PMO), Operations, Security & Privacy, Quality & Risk.
• CGEO cluster — led by the Chief Growth & Experience Officer (.claude/agents/chief-growth-experience-officer.md). Units: Growth, Customer Success, Creative — Brand & Marketing.

Units

The Archives

• Lead: Archivist (Claude Code agent) — .claude/agents/archivist.md
• Members: Archivist (Lead) · Historian (member)
• Historian (.claude/agents/historian.md) — maintains the company’s history and preserves its legacy, and can tell our story at any level (logline → full chronicle); owns the narrative history under history/. Hired by the Archivist per the Staffing & Delegation policy because narrative history is a distinct function better allocated to a dedicated employee.
• Mission: preserve a faithful, verifiable, version-tracked record of every authored document in the project.
• Receives everything (omni-intake). Every unit and agent hands off all of its documents to the Archivist, who has authority to archive anything in the project. It is the single, comprehensive sink for the organization’s record.
• Exclusion: the Principal’s personal information (held only by the PA) is not a project document and is never archived.
• Owns: everything under archive/ — the per-document first / latest / milestones versions, the MANIFEST.md inventory, and integrity verification.
• Operating rules: the unit charter docs/units/archives/charter.md (primary operating model); archive/SPECIFICATION.md (policy) and archive/README.md.

Rules & Governance

• Lead: Golden Rule (Claude Code agent) — .claude/agents/golden-rule.md
• Members: Golden Rule (sole member)
• Mission: turn ideas into clear, testable rules and conventions, and keep the project’s rules sharp and consistent.
• Owns: rule entries in CLAUDE.md (AI-facing) and CONTRIBUTING.md (human-facing) — drafting and iterating them.
• Operating rules: the unit charter docs/units/rules-governance/charter.md (primary operating model); agent def .claude/agents/golden-rule.md.

Human Resources

• Lead: Human Resources (Claude Code agent) — .claude/agents/human-resources.md
• Members: Human Resources (sole member)
• Mission: manage the lifecycle of agents and units — onboarding, unit assignment, role charters, and unit renaming.
• Owns: this file (ORG.md) — the org chart, unit definitions, and roster — the onboarding process, the standard agent-definition format, and HR documentation (employee handbook, employee records, policies, and guidelines). HR documentation is distinct from foundational documents, which the Documentation unit owns.
• Operating rules: the unit charter docs/units/human-resources/charter.md (primary operating model); agent def .claude/agents/human-resources.md.
• Note: HR may rename units, including provisional names.

Documentation

• Lead: Documentarian (Claude Code agent) — .claude/agents/documentarian.md
• Members: Documentarian (sole member)
• Mission: create and maintain the project’s foundational documents — the concept/strategy, plan, vision, glossary, and core references under docs/ — keeping them coherent, current, and cross-linked.
• Owns: the content of foundational documents under docs/. Authoring/maintenance only — preservation stays with The Archives, rules with Rules & Governance.
• Operating rules: the unit charter docs/units/documentation/charter.md (primary operating model); agent def .claude/agents/documentarian.md.

Finance

• Lead: Finance Director (Claude Code agent) — .claude/agents/finance-director.md
• Members: Finance Director (Lead) · Financial Analyst (member)
• Financial Analyst (.claude/agents/financial-analyst.md) — owns cost-tracking ledgers, AI-usage utilization reports, and financial data compilation for the Finance unit. Reports to the Finance Director.
• Mission: ensure the Principal always knows what things cost, what the budget allows, and whether a spend is worth it — across both the money ledger and the AI-utilization ledger.
• Owns: money ledger (finance/ledger-money.csv), AI-usage ledger (finance/ledger-ai.csv), cross-rate table (finance/rates.csv), budget registry (finance/budgets.csv), spend approval log (finance/approvals.csv), and financial reporting. Owns the dual financial system design (docs/financial-system.md).
• Operating rules: the unit charter docs/units/finance/charter.md (primary operating model); agent defs .claude/agents/finance-director.md and .claude/agents/financial-analyst.md.

Legal & Compliance

• Lead: Legal Director (Claude Code agent) — .claude/agents/legal-director.md
• Members: Legal Director (Lead) · Compliance Analyst (member)
• Compliance Analyst (.claude/agents/compliance-analyst.md) — owns compliance checklists, software license auditing, and policy tracking. Reports to the Legal Director.
• Mission: protect the platform and the Principal from external legal exposure — before obligations are breached, not after. Proactive, not reactive.
• Owns: software licensing audits (docs/legal/license-inventory.md), terms of service and privacy policy (docs/legal/), AI-regulatory compliance register (docs/legal/ai-compliance.md), and intellectual property positions.
• Operates independently. Reports directly to the Principal (no intermediate cluster Director).
• Operating rules: the unit charter docs/units/legal-compliance/charter.md (primary operating model); agent defs .claude/agents/legal-director.md and .claude/agents/compliance-analyst.md.

CPTO Cluster — Innovation, Product & Technology

Innovation — Strategy & Research

• Lead: Innovation Director (Claude Code agent) — .claude/agents/innovation-director.md
• Members: Innovation Director (Lead) · Competitive Intelligence Analyst (member)
• Competitive Intelligence Analyst (.claude/agents/competitive-intelligence-analyst.md) — researches and monitors the competitive landscape, market trends, and industry developments that feed the hypothesis pipeline. Reports to the Innovation Director.
• Mission: own the front of the product funnel — generate a strong, evidence-tested pipeline of strategic bets, de-risk them cheaply, and hand the best ones to the Principal and Delivery/PMO at the Ideate→Plan gate.
• Owns: the idea pipeline, hypotheses/experiments, generative research evidence, competitive intelligence synthesis, and the Ideate→Plan handoff package.
• Note: the legacy innovation-lead.md role is superseded by the Innovation Director (its functional successor) and was retired in Wave 0 (R10); its agent file no longer exists in .claude/agents/ and the roster entry below is retained for traceability only. The Competitive Intelligence Analyst’s reports to line correctly references “Innovation Director” (confirmed by HR, 2026-06-01, Wave 0 roster hygiene).
• Operating rules: the unit charter docs/units/innovation/charter.md (primary operating model); the agents’ own definitions in .claude/agents/.

Design Research

• Lead: Design Research Director (Claude Code agent) — .claude/agents/design-research-director.md
• Members: Design Research Director (Lead) · Instructional Designer (member) · UX Designer (member) · UX Research Associate (member)
• Instructional Designer (.claude/agents/instructional-designer.md) — designs learning experiences, course structures, and instructional frameworks that translate content strategy into effective learner journeys. Reports to the Design Research Director.
• UX Designer (.claude/agents/ux-designer.md) — owns interaction design, wireframes, prototypes, and design systems that give the platform’s interfaces clarity and usability. Reports to the Design Research Director.
• UX Research Associate (.claude/agents/ux-research-associate.md) — plans and executes evaluative research studies (usability tests, surveys, interviews) and synthesizes findings into actionable recommendations. Reports to the Design Research Director.
• Mission: produce the evidence that grounds every phase gate — the continuous spine of the Standard Flow (docs/methodology.md). Generative research at Ideate; evaluative research at Plan & Build; telemetry and feedback loops at Grow & Operate.
• Owns: the research plan, all research instruments and protocols, findings reports (written to reports/), the cumulative research library (docs/knowledge/research/), instructional design frameworks, and UX design artifacts.
• Operating rules: the unit charter docs/units/design-research/charter.md (primary operating model); the agents’ own definitions in .claude/agents/.

Engineering

• Lead: Engineering Director (Claude Code agent) — .claude/agents/engineering-director.md
• Members: Engineering Director (Lead) · Staff Engineer (member) · Platform Engineer (member)
• Staff Engineer (.claude/agents/staff-engineer.md) — writes the code, fixes bugs, conducts code reviews, and ships working product. Reports to the Engineering Director.
• Platform Engineer (.claude/agents/platform-engineer.md) — owns the developer platform, infrastructure-as-code, deployment pipelines, and the foundational services that application code runs on. Reports to the Engineering Director.
• Mission: own the technical build — write and maintain production-quality code, steward the architecture, and ship working product increments.
• Owns: all source code under intranet/, the content sync pipeline, technical architecture decisions, code quality, Vercel configuration, and platform infrastructure.
• Operating rules: the unit charter docs/units/engineering/charter.md (primary operating model); the agents’ own definitions in .claude/agents/.

Data & Analytics

• Lead: Data & Analytics Director (Claude Code agent) — .claude/agents/data-analytics-director.md
• Members: Data & Analytics Director (Lead) · Analytics Engineer (member)
• Analytics Engineer (.claude/agents/analytics-engineer.md) — implements and maintains the data pipelines, event schemas, and analytics models that turn raw telemetry into trusted, queryable datasets. Reports to the Data & Analytics Director.
• Mission: make the venture’s learning platform measurable, improvable, and self-reinforcing — precise telemetry, trustworthy scoring, and a data strategy that closes the content→learner feedback loop.
• Owns: event taxonomy and schema, telemetry pipeline specs, scoring and ranking systems, feedback loop design, measurement frameworks, data strategy, and analytics data models.
• Operating rules: the unit charter docs/units/data-analytics/charter.md (primary operating model); the agents’ own definitions in .claude/agents/.

AI Systems

• Lead: AI Systems Director (Claude Code agent) — .claude/agents/ai-systems-director.md
• Members: AI Systems Director (Lead) · AI Engineer (member)
• AI Engineer (.claude/agents/ai-engineer.md) — builds and integrates AI-powered features, model integrations, and inference pipelines that bring AI capabilities into the platform. Reports to the AI Systems Director.
• Mission: ensure the org’s AI systems — every agent definition, system prompt, model choice, and eval harness — are best-in-class.
• Owns: prompt architecture (all agent and product-feature prompts), model selection decision matrix, eval harnesses, AI cost optimization, Claude API best practices, and AI feature implementation.
• Operating rules: the unit charter docs/units/ai-systems/charter.md (primary operating model); the agents’ own definitions in .claude/agents/.

Product

• Lead: Product Manager (Claude Code agent) — .claude/agents/product-manager.md
• Members: Product Manager (sole member)
• Mission: own the product backlog and requirements — translate user needs and strategic direction into a prioritized, well-specified backlog that Engineering and Design Research can execute against.
• Owns: product backlog, roadmap, user stories, acceptance criteria, and feature prioritization decisions.
• Reports to: CPTO.
• Operating rules: the unit charter docs/units/product/charter.md (primary operating model); agent def .claude/agents/product-manager.md.

COO Cluster — Delivery, Operations, Security & Quality

Delivery (PMO)

• Lead: Project Manager (Claude Code agent) — .claude/agents/project-manager.md
• Members: Project Manager (sole member)
• Mission: plan and drive delivery of projects/builds to a verifiable finish — scope, sequencing, milestones, dependencies, risk, and status.
• Owns: project plans, milestone definitions, and delivery status.
• Reports to: COO.
• Operating rules: the unit charter docs/units/delivery-pmo/charter.md (primary operating model); agent def .claude/agents/project-manager.md.

Operations

• Lead: Process Engineer (Claude Code agent) — .claude/agents/process-engineer.md
• Members: Process Engineer (Lead) · Site Reliability Engineer (member)
• Site Reliability Engineer (.claude/agents/site-reliability-engineer.md) — owns production reliability, uptime monitoring, incident response, and the SLOs/SLAs that define the platform’s operational health. Reports to the Process Engineer.
• Mission: make the company’s work repeatable, efficient, and low-toil — the operating model, SOPs/runbooks, workflows, automation, and the build/CI pipeline.
• Owns: docs/operations.md, docs/sop/, the change-management process, hooks (.claude/hooks/) and CI (.github/workflows/) as process/automation, and production reliability/incident management.
• Reports to: COO.
• Operating rules: the unit charter docs/units/operations/charter.md (primary operating model); the agents’ own definitions in .claude/agents/.

Security & Privacy

• Lead: Security Director (Claude Code agent) — .claude/agents/security-director.md
• Members: Security Director (Lead) · Security Analyst (member)
• Security Analyst (.claude/agents/security-analyst.md) — owns day-to-day secrets hygiene, dependency vulnerability scanning, and security review of Engineering PRs. Reports to the Security Director.
• Mission: ensure the org operates with a clear, documented, and enforced security and privacy posture — no secret exposure, no privilege creep, no unexamined attack surface.
• Owns: security policy library (hr/policies/security.md, etc.), agent tool-grant policy, prompt-injection defense posture, secrets-in-context rules, threat models (docs/security/threat-models/), security ADRs, and the security incident runbook.
• Operating rules: the unit charter docs/units/security-privacy/charter.md (primary operating model); the agents’ own definitions in .claude/agents/.

Quality & Risk

• Lead: Quality & Risk Director (Claude Code agent) — .claude/agents/quality-risk-director.md
• Members: Quality & Risk Director (sole member)
• Mission: operate as the second line of defense — maintain standing quality standards, own the operational risk register, conduct recurring internal audits, and provide independent assurance that the org’s processes and outputs meet the bar they claim to meet.
• Owns: the operational risk register (reports/risk-register.md), internal audit reports, quality standards, control gap registry, and recurring audit cadence.
• Operating rules: the unit charter docs/units/quality-risk/charter.md (primary operating model); agent def .claude/agents/quality-risk-director.md.

CGEO Cluster — Growth, Experience & Creative

Growth

• Lead: Growth Director (Claude Code agent) — .claude/agents/growth-director.md
• Members: Growth Director (Lead) · Content Strategist (member) · Video Producer / Script Writer (member)
• Content Strategist (.claude/agents/content-strategist.md) — owns the YouTube content calendar, format strategy, and distribution planning. Reports to the Growth Director.
• Video Producer / Script Writer (.claude/agents/video-producer.md) — translates content briefs into production-ready episode scripts, editing notes, chunk tags, and newsletter derivative copy. Reports to the Growth Director.
• Mission: grow the audience that the YouTube channel and web learning platform need to matter — find who should care, put the right content in front of them, at the right cadence, through the right channels, and measure what’s working.
• Owns: channel strategy, go-to-market plans, content distribution, publishing cadence, audience intelligence, and growth metrics definition.
• Operating rules: the unit charter docs/units/growth/charter.md (primary operating model); the agents’ own definitions in .claude/agents/.

Customer Success

• Lead: Customer Success Director (Claude Code agent) — .claude/agents/customer-success-director.md
• Members: Customer Success Director (Lead) · Community Manager (member)
• Community Manager (.claude/agents/community-manager.md) — owns unstructured community engagement, audience moderation, and learner forum interactions. Reports to the Customer Success Director.
• Mission: ensure every learner and key stakeholder achieves their intended outcome with the platform — through structured onboarding, proactive health monitoring, closed-loop feedback systems, and strong partner relationships.
• Owns: learner onboarding programs, success metrics and health scores, feedback collection systems, learner health reviews, partner and stakeholder relationships, and success playbooks.
• Operating rules: the unit charter docs/units/customer-success/charter.md (primary operating model); the agents’ own definitions in .claude/agents/.

Creative — Brand & Marketing

• Lead: Creative Director (Claude Code agent) — .claude/agents/creative-director.md
• Members: Creative Director (Lead) · Brand Strategist (member) · Visual Designer (member)
• Brand Strategist (.claude/agents/brand-strategist.md) — owns brand strategy, brand guidelines, and voice/tone — the durable rules governing how KLMS presents itself. Reports to the Creative Director.
• Visual Designer (.claude/agents/visual-designer.md) — executes visual identity and UI design craft: color palettes, type scales, spacing systems, design tokens, and UI specifications. Reports to the Creative Director.
• Mission: own the venture’s public-facing creative output — how it looks, sounds, and reads to the world.
• Owns: brand strategy, visual identity system, UI design direction, marketing content, and the content strategy framework. Brand guidelines encoded in docs/brand/.
• Operating rules: the unit charter docs/units/creative/charter.md (primary operating model); the agents’ own definitions in .claude/agents/.

Standard business functions — coverage

The org is reviewed against standard business functions so no need goes unowned.

Agent roster

In-scope count (Coverage % anchor): 41 agents = 40 functional + PA. Excluded from the count: External Review Partners (external retainer, not an employee) and the legacy Innovation Lead (superseded by the Innovation Director; row retained for traceability only). File-checkable: the roster table below has 43 definition rows; 43 − 2 excluded = 41 in-scope.

Conventions

• Each unit has exactly one Lead and a defined Mission and owned artifacts. Unit Leads are Directors — they coordinate continuously with peer Directors and their unit members (hr/policies/communication.md).
• Every employee has a complete job description (its agent definition) and strictly abides by the Employee Handbook (hr/employee-handbook.md) and the Policy Library (hr/policies/).
• Work may be delegated to background agents as needed (hr/policies/background-agents.md).
• Unit Leads assume the work. Each Lead owns and personally performs their unit’s work by default, and hires additional staff only when the work is better allocated to a dedicated employee (see hr/policies/staffing-and-delegation.md). New staff report to the hiring Lead.
• The Personal Assistant delegates work to Unit Leads on the Principal’s behalf; Leads then assume or allocate it.
• New agents are added to the roster and placed in a unit (or marked unassigned until a unit exists).
• This chart is itself an archived document (see archive/); update it whenever units or agents change.