Community

Kno is designed to be extended, and everyone who uses it has something to add. Here is how participation works, from first star to core contribution.

The participation ladder

You do not need permission, and you do not need to start deep. Each rung is a real contribution:

Discover, read the mental model. One page, and the rest makes sense.
Try, run the quickstart. It costs nothing.
Star, stars are signal, not currency. The repo is uknoAI/kno.
Use, point Kno at a real provider behind a budget cap. Something breaks? That is a bug report waiting to happen.
Discuss, usage questions and open-ended discussion live in the issue tracker.
Report, issues follow templates, with labels bug, enhancement, or adapter. Security reports have a separate path.
Improve docs, the cookbook is task-shaped on purpose. A recipe for your stack is a contribution.
Build an adapter or judge, Ring-1 adapters and judge prompts are the natural on-ramps. See where to start.
Core contribution, the loop is open: plan first, adversarial review, then code.
Repeat, the debt ledger is public, every entry has a repayment trigger, and repayment is ordinary work.

How we work

Before you write code, read CONTRIBUTING.md , the short version: the vocabulary is law, plan first, review adversarially, then code. Good-first-issue is a curated pipeline, not a label of neglect: each one has context, a plan, and a clear completion condition.

Extend Kno

Surface	What it adds	Status
Adapters	New data sources, JSONL, CSV, Markdown, Langfuse, LangSmith, Zendesk recipes ship today	Open
Judges	Evaluation logic for new kinds of cases	Open
Goals	Optimization targets for select	Open
Providers	New agent runtimes, `openai:`, `anthropic:`, `exec:`, `fake:` ship today	Open
Core	The valuation engine itself	Open

Also

The roadmap is public, including what is deliberately out of scope.
The debt ledger is public on purpose, every accepted piece of debt has a repayment trigger.
The Code of Conduct applies everywhere.