kolm  /  community

kolm community.

Where engineers compiling .kolm artifacts talk shop. Four surfaces below: a Discord for synchronous help, GitHub Discussions for durable threads, an HN launch post for the wide audience, and an X/Twitter thread for the short read. Direct line is founders@kolm.ai.

Where we hang out.

Pick the surface that matches the question. Discord for live debugging. GitHub for "here is a manifest, does the K-score look right." HN and X are launch surfaces, not support channels.

01 . live chat

Discord

discord.gg/kolm

Joining beta. The invite is gated for the first 90 days to keep signal-to-noise high. DM founders@kolm.ai for an invite. Five channels: welcome, announcements, help, showcase, compliance-q-and-a.

02 . long form

GitHub Discussions

github.com/sneaky-hippo/kolmogorov-stack

Open. No invite required. The right surface for "here is a reproducer," "here is a manifest," "here is a spec question on RS-1." Threads stay searchable across releases.

03 . launch

HN launch thread

news.ycombinator.com (link from /community/hn-launch)

The Show HN post template and after-post checklist. Live URL drops in here when the post goes up. Comments on the post are the canonical FAQ for the first 72 hours.

04 . short read

X/Twitter thread

7 tweets, each <=280 chars

Pre-written launch thread. Each tweet is in a copy-able box with a visible character count. Hook, problem, artifact, number, verify, pricing, CTA.

Contributor guide.

Five short answers to the questions every new contributor asks. The long form lives in CONTRIBUTING.md in the repo. Start with the docs and the RS-1 spec if you want to read before you write.

  • What can I work on? The repo has good-first-issue and help-wanted labels on GitHub. Backend adapters, compliance pack mappings, and CLI verbs are the easiest places to start.
  • How do I run the tests? npm test for the CLI and SDK, pytest for the Python runtime, ./scripts/e2e-flow.sh for the 9-stage end-to-end. Everything is gated by signed receipts.
  • What is the review bar? One signed-off review from a core maintainer. K-score regressions block merge. Em-dashes block merge (we use plain hyphens).
  • How do I sign my commits? git commit -S. Add your public key to your GitHub profile. The verify-on-PR Action checks the signature.
  • What if I want to write a research article? Open a Discussion first with the outline. We bias toward shipping fewer, longer pieces over many short ones. Templates in /research.

Code of conduct.

Contributor Covenant 2.1. The full text is in CODE_OF_CONDUCT.md in the repo. Short version: be the engineer you would want to debug a 3am incident with. Disagree on the technical substance, not the person. Report violations to founders@kolm.ai and they will be read within 24 hours.

One additional kolm-specific rule: do not paste customer PHI, customer credentials, or any private data into any community surface. The whole product is built around the premise that those things stay on your hardware. Honor that here too.

Direct line.

If the question is sensitive, embargoed, or you would rather not post in public: founders@kolm.ai. PGP key on /security. Response time is under one business day for most things, under one hour for security disclosures.