Skip to content

KLMS — Company Chronicle

Guide

KLMS — Company Chronicle

Maintained by the Historian (The Archives). The living narrative of how KLMS came to be. Tellable at any level — start with the logline and go as deep as you like.

Logline

From an empty repository to a self-organizing company of Claude Code agents that build, govern, document, and remember.

In brief

KLMS began as an empty repo. It started with a CLAUDE.md scaffold, then captured its founding concept — a “show the work” learning platform with a dual flywheel. To protect that founding vision, it built a preservation Archive (first / latest / milestones, checksum-verified), then grew an org led by the Principal (Kevin Wong) with functional units — The Archives, Rules & Governance, Human Resources, Documentation — staffed by purpose-built agents, plus a Personal Assistant. It wrote its own Golden Rules, trained HR to hire, set staffing policy, and appointed a Historian to keep the story.

Timeline (milestones)

  1. Empty repository — no code, no history.
  2. CLAUDE.md scaffold — first guidance for AI assistants.
  3. Founding concept captured (docs/concept.md) — the channel + dual-flywheel learning platform; designated the protected cornerstone.
  4. Operational-review prompt stored, then sharpened into a reusable spec.
  5. The Archives established — verbatim, checksum-verified preservation.
  6. Versioned archive policy — keep first + latest (+ milestones, TBD).
  7. Org chart created — Kevin Wong at the top; The Archives as the first unit.
  8. Rules & Governance + Human Resources units; Golden Rules GR-1/2/3.
  9. Documentation unit — the Documentarian for foundational documents.
  10. Personal Assistant hired — exclusive keeper of the Principal’s personal information.
  11. HR trained to hire; Staffing & Delegation policy set — Leads assume the work, and hire when it’s better allocated.
  12. Historian appointed — to maintain history and preserve legacy.
  13. Repository staged as a reusable template — scaffolding genericized; a one-command instantiation helper added.
  14. Acquisition of stack-agents — absorbed the proven agent-lifecycle pattern; /agents:hire|train|review|combine|fire commands wired to HR.
  15. Operations layer — SessionStart/SessionEnd hooks, a daily Notion briefing
    • day’s report cadence, and a hardened hiring/onboarding pipeline with a standard-business-function coverage map.
  16. External Review Partners retained; first independent 360° review delivered.
  17. Positioned as an AI business ideator, incubator, builder & operator — the template is the product.
  18. Merged to main — the work promoted to a conventional mainline.
  19. AI-as-economy + ERP entered Plan — a parallel money + AI-usage financial system, and an ERP backbone + intranet program (build deferred).
  20. Documentation foundations — CONTRIBUTING, LICENSE, glossary, the macro→job-aid canon, getting-started, an ADR log, a security policy, and automated manifest upkeep (scripts/archive-manifest.sh); milestones defined.
  21. Three hires for the first build — a Project Manager (Delivery/PMO), a Process Engineer (Operations), and an Innovation Lead (Innovation) join as Unit Leads; the org grows to seven units as the intranet build begins.
  22. First product slice — the Intranet — a lean static portal (intranet/, Astro + Tailwind) ships locally: a Dashboard, Document browser, agent Chatter, and People/org view, reading the repo as the source of truth. The company has its first working front end (ADR-0006).
  23. Experts, educated, equipped — a Standard that every employee is a top expert who stays current; a Resource Access policy + an Access-Request SOP (SOP-001) for what they lack; and a cumulative knowledge base (docs/knowledge/) so the company gets smarter over time.
  24. The Archivist is tooled with GitHub (ADR-0007) — the first deliberate agent tooling, least-privilege. The documentation system lands: a change-management SOP + DoD (SOP-002), an operating model, doc templates, a user manual, the first job aid, and a lean ERP needs-analysis.
  25. Intranet goes to deploy — decided GitHub-connected Vercel behind single-user Vercel Authentication (ADR-0008); the repo is made deploy-ready with a runbook (SOP-003, AR-002). The live chatter store stays deferred. The first product slice steps toward a real URL.
  26. Pre-deploy security audit — a full sweep (secrets, PII, deps, least-privilege, CI/hooks, auth posture): no critical/high issues, clear to deploy behind the auth gate. Tightened the External Reviewer to read-only tools and hardened .gitignore against secrets.
  27. Secrets management + deploy budget — managed secret stores + a CI quality gate (ci.yml) and SOP-004; and, to stop burning the 100/day Vercel limit, no preview deploys, path-gated builds, and batched pushes (ADR-0009).
  28. Second 360 + course-correction — an independent review (B/B+): operational risks fixed and real product shipped, but the venture hasn’t started. Acted on the operational findings: scoped the PA to least-privilege, made the daily-reports cadence honest (manual until secrets), and set a hiring freeze.

Going deeper

For a chapter or full chronicle, the Historian draws on archive/MANIFEST.md, the document versions under archive/documents/, git history, and how ORG.md evolved. Ask for the altitude you want.