The Karajan family — one method, one family of tools

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.

npm docs github

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.

web npm

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.

web npm

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.

npm

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.

npm

core

Core the shared ground

The internals the family stands on: a model registry with pricing, shared paths and the small pieces every member reuses — so the family speaks one language instead of seven dialects.

npm

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.

github