← karajancode.com

The family

One method, one family of tools

Karajan governs AI-driven development. Around it, a family of tools shares the same method, told with the orchestra in mind: the conductor, the memory, the watchman, the music stand with the scores, the libretto. Here is each one, on its own, and who stands on whom.

Karajan Code mascot

Karajan Code the conductor

Governs AI-driven development: your agent writes, the git gates make a false green structurally impossible. Cross-AI review bound to every diff, TDD-first, a Sentinel that blocks inside the session, and a hash-chained ledger of every decision.

kaRAGan

kaRAGan the context engine

RAG, CAG and hybrid answers over your code, docs and data — with a sensitivity policy deciding which model may see what, and secrets kept out of the index. The memory the agent consults before it assumes.

kaWATCHan

kaWATCHan the watchman

Multi-repo vigilance: a shared corpus kept fresh on every merge, cross-repo impact judgment when one change ripples into another repo, and alerts when the docs drift from the code.

atril

atril the music stand

Skills, commands and subagents for every AI CLI, kept in a store no CLI loads up front and resolved only when a task asks for them: search, resolve within a budget, install, route. Fully isolated: it depends on nothing else in the family. A contribution by Jorge del Casar.

libretto

Libretto the stories

The HU Board: the user stories the orchestra plays, who holds each one and what has been played. Shared through GitHub Issues, so two people can work the same repo without minting the same card, with a local copy for when the network is out.

console

Console the admin

The web console of a family instance: corpus health, people's access, and operations run as workflows — every one of them sealed in a hash-chained audit trail you can read after the fact.

governance

Governance the kernel

Policy, Decision and Exception as first-class objects — deterministic, local, domain-agnostic. karajan-code is its first consumer, not its owner: the same kernel can govern any domain, not only code.

core

Core the shared ground

The internals Karajan Code and Libretto stand on: the vector store and retriever, a model registry with pricing, shared paths. Not every member uses it, on purpose: kaRAGan, atril and Governance depend on nothing, so each can be used alone.

radar

Radar in the works

Configurable research intelligence: watching the frontier so the family reacts to what changes. Brewing in the open, not released yet.

Who stands on whom

Read from the package manifests, not from a diagram drawn first. Three pieces stand alone and the others combine them.