Skip to content

Glossary

Guide

Glossary

Seed glossary of KLMS terms. Grows over time. Indexed in docs/canon.md.

  • Principal — Kevin Wong; founder/owner; top of the org.
  • Unit — a functional team with one Director (Lead) and a mission.
  • Director — a Unit Lead; coordinates continuously with peers/members.
  • Agent / employee — a Claude Code subagent (.claude/agents/*.md).
  • The Archives / Archivist — preservation unit; keeps the versioned record.
  • Canon — the documentation map every employee reviews each morning (docs/canon.md).
  • Ideation spec — a JSON entry-point document (from the monorepo) that seeds Ideate.
  • Standard Flow — Ideate → Plan → Build → Grow → Operate (docs/methodology.md).
  • Design research — the evidence-gathering spine across every phase.
  • Money / AI-Usage ledgers — the two parallel, integrated financial ledgers.
  • Cross-rate — the $/unit conversion linking AI usage to money.
  • ERP — the integration backbone over Finance/HR/Records/Operations.
  • SOP — Standard Operating Procedure; a recurring procedure, owned by an agent, lives flat in docs/sop/ under a global SOP-NNN ID (allocated by Operations — docs/sop/registry.md).
  • Job aid — a granular, stranger-executable task quick-reference (JA-###), kept with its unit under docs/units/<unit>/job-aids/.
  • Playbook — a unit’s living digest of durable know-how (recurring patterns, named failure modes, hard numbers, “demons”), Lead-owned, sourced from — not duplicative of — knowledge entries (docs/units/<unit>/playbook.md; knowledge-management.md §4).
  • Unit charter / operating model — the very-high-altitude doc that defines a unit’s mission, what it owns and does not own, its handoffs, and operating rules; Lead-owned, converges upward (docs/units/<unit>/charter.md; master plan §3). For a cluster, the analogous doc is the cluster operating-model (docs/units/<cluster>/operating-model.md) — the cascade boundary the cluster’s unit charters fit inside; not a unit charter.
  • Role manual — the per-agent, high-altitude how-I-work doc; for a solo unit the charter and role manual may collapse into one (docs/units/<unit>/charter.md or manuals/<agent>.md).
  • Knowledge entry — a dated, append-only learning record (docs/knowledge/YYYY-MM-DD-<slug>.md): what we learned · why it matters · next time · links. Governed by supersession, not expiry; the inbox that documentation promotes from (knowledge-management.md).
  • Interface Contract — the fixed, machine-parseable block at the top of every SOP declaring inputs/outputs, in/out handoff triggers, and Definition of Done before handoff (interface-contract-spec.md; master plan §5.1). Owned by Operations (Process Engineer).
  • Handoff Register — the org-wide aggregated edge matrix (producer → artifact → consumer → trigger), one row per declared Interface-Contract edge; a generated artifact (docs/handoff-register.md). Operations owns the mechanism + reconciliation; Q&R provides independent assurance.
  • Trigger registry — the single canonical, controlled vocabulary of exact handoff-trigger phrases an Interface Contract may use (docs/handoff-triggers.md); Operations-owned, frozen in Wave 0. A trigger: value not in the registry is an UNREGISTERED TRIGGER defect.
  • Reconciler — scripts/handoff-reconcile.mjs: the scripted gate that parses every Interface Contract block and emits a single red/green number (unmatched edges · overlaps · unregistered triggers). GREEN = 0 of each.
  • Fan-in / fan-out — handoff shapes the reconciler recognizes: fan-in = many producers feeding one declared sink (placeholder producer, keyed owner|trigger — e.g. the Archivist’s artifact approved intake); fan-out = one producer broadcasting to all agents (e.g. preservation complete). (interface-contract-spec.md §3.1.1.)
  • Cluster operating-model — see Unit charter / operating model.
  • Phase gate (G0–G3) — the documentation program’s four wave/phase gates (docs/documentation-program/tracker.md): G0 = Wave 0 plumbing built + pilot reconciles GREEN; G1 = Wave 1 governance cluster stable; G2 = all three clusters’ Phase-1 DoD met; G3 = Program DoD (register 0 unmatched edges, de-dup → 0, KM reconciled, COO signs → Principal). Distinct from the five Standard-Flow gates (Ideate→Plan→Build→Grow→Operate, docs/methodology.md / SOP-005) — those gate the venture; G0–G3 gate the doc program.
  • ADR — Architecture Decision Record (docs/adr/).
  • DoD — Definition of Done (docs/sop/change-management.md).
  • GR-# (a rule) — an individual Golden Rule, e.g. GR-8 (CLAUDE.md).
  • Golden Rule (the agent/unit) — the Rules & Governance unit/agent that authors and curates the Golden Rules (GR-#) and CONTRIBUTING.md. (Disambiguation: “Golden Rule” capitalized is the unit; GR-# is one of its rules.)
  • first / latest / milestone — the archive’s retained versions per document.