Skip to content

Kernos

One runtime, every department. Agents that work inside their remit, stop at the gates you set, and keep running for months without anyone editing the code.

Apache 2.0 Rust · Go · Python · TypeScript v0.1.0

A kernos is a Greek ritual vessel: a single ring with many small cups attached to it, each holding a different offering, all carried as one object. Finance, people, revenue, support, operations, legal and engineering each get their own cup. The ring is shared.

Kernos is an open engine for company-wide automation with language models. It is deliberately empty of business logic: the runtime, the capability model, the policy engine, the connector protocol and the evaluation harness are here, while the workflows, prompts and rules that describe a particular company stay private to that company and load as signed bundles.

Remits

A run carries a signed capability set: the exact tools, data scopes, spend and expiry. The gateway refuses anything outside it, whatever the model was persuaded to try. Read more

Policy and approvals

Which actions need a human is a declarative rule. Approval is a typed record with actor, reason and timestamp, reconstructible months later. Read more

Durable, replayable runs

Every run is an append-only, hash-chained event log. It survives restarts, never repeats an external write, and replays to reproduce every decision. Read more

Running unattended

Contract canaries catch upstream drift before a real run does; every change ships through one evaluate and promote-or-rollback gate. Read more

Start here

  • Quickstart: build, run the acceptance suite, then walk one invoice through the reference bundle, approve it, and replay it.
  • Architecture: the four components, why each is in the language it is, and what talks to what.
  • Write a bundle: describe a workflow as data and load it without a deploy.
  • Kernel API, Gateway API, CLI: the complete reference.

Packages

Every layer ships as a package in its own ecosystem's registry, so you can depend on the part you need rather than adopting the whole platform.

Package Install What it is
kernos cargo install kernos The kernel and control-plane server, and the operator CLI
kernos-core cargo add kernos-core The kernel as a library: event log, replay, scheduler, remits, budgets
kernos-policy cargo add kernos-policy The policy language and evaluator, usable on its own
kernos-sdk pip install kernos-sdk The reasoning worker and the evaluation harness
@kernos/sdk npm install @kernos/sdk The typed TypeScript client
kernos/gateway go get github.com/rhs2/kernos/gateway The gateway and the connect connector SDK
Container images docker pull ghcr.io/rhs2/kernos-kernel Kernel, gateway and worker, also kernos-gateway and kernos-worker
Binaries download Linux and macOS, arm64 and x86_64, with checksums

The source is at github.com/rhs2/kernos, and every one of those artefacts is published from a single version tag by one workflow that runs the whole test suite and the acceptance suite first.