Projects / ki-techne-harness
A runnable personal-controller execution fabric for the ecosystem.
Where the agentic harness publishes capabilities an agent can use, the Techne harness provides somewhere for work to actually run: a Kubernetes-based personal controller and execution fabric that a single operator can stand up and keep. It is infrastructure for the ecosystem rather than a source of knowledge or capability semantics.
Public platform repository · source
The problem
What this is for.
Agentic work eventually needs somewhere to run that is not a terminal you have to keep open. The Techne Harness is that somewhere: a Kubernetes-based personal controller and execution fabric sized for one operator to stand up and keep running, rather than for a platform team to administer.
Whose problem
Whether it is yours.
You want this if agent work has outgrown your laptop and should run on infrastructure you control. It assumes you are comfortable operating Kubernetes; nothing here hides that from you.
Capabilities
What it actually does.
- A dependency-free Telegram-to-Kubernetes controller, with its own tests.
- Kubernetes resources for the controller and for the execution targets it dispatches to.
- Replaceable AWS proof infrastructure, kept separable so the fabric is not tied to one cloud.
- Harness lifecycle operations that sit behind the techne operator command.
- Packaged controller-host and target-host deployment payloads.
State
How finished it is.
Public source, developed as a product monorepo rather than released as a package. The operator command line is released separately, from tools-techne, which owns the command grammar, installer, diagnostics and manual.
Using it
How to start.
Public source. Clone the repository and follow its own operating documentation to stand a fabric up.
Boundaries
What it deliberately does not do.
It runs work; it defines neither capability semantics nor standards. It stores no credentials and no canonical operational state, both of which stay in their own systems. Knowledge Islands Principal's Engineering Practice remains the authority for the engineering architecture this implements.
Authority
What this repository owns.
Execution infrastructure. It runs work; it defines neither capabilities nor standards.
That boundary is deliberate. The ecosystem separates philosophy, engineering discipline, capability semantics, portable standards, and executable behaviour so that none of them can quietly absorb another. The full directory shows where this project sits relative to the rest.
Nearby
Other projects of the same kind.
homebrew-tap— The Homebrew tap that packages the released Knowledge Islands command-line tools.packages-stoa— Stoa: web components and styles that static sites share, rendered at build time.ki-website— The public publication layer — this site.
See every public project, or go straight to the released command-line tools.