manufosela/karajan-code

卡拉詹法典

主导人工智能驱动开发的环境——你的代理主导，卡拉詹主导。

西班牙语学习 ·文献资料 ·公共路线图

---

你的AI代理（Claude Code、Codex、Copilot、Antigravity、Cursor…）负责编写代码。Karajan管理其发生方式：它安装代理在每个任务中遵循的方法，并通过git门强制执行，使假绿在结构上不可能。

• **RAG before assume ** — kj rag query 回答你的代码库的功能;没有代理猜测。安装时将其布线为原生 MCP 工具（[kj_rag_query），因此查询索引是代理最便宜的路径。开箱即用：本地 Ollama，或内置 ONNX 嵌入器，当无法安装任何东西时;云嵌入器要求明确的敏感性声明和每个区块的个人身份信息（PII）隐去。一个精炼的工程规范（canon）运行：kj rag query --library 提供模式卡（当适用时，不适用，则为规范引用），因此计划指定绿地替代方案，而不是沿用惯性遵循遗留线。

Karajan Code

The environment that governs AI-driven development — your agent orchestrates, Karajan governs.

Leer en Español · Documentation · Public roadmap

---

Your AI agent (Claude Code, Codex, Copilot, Antigravity, Cursor…) writes the code. Karajan governs how it happens: it installs a method your agent follows on every task, and enforces it with git gates that make a false green structurally impossible.

• RAG before assuming — kj rag query answers what your codebase does; no agent guesses. The install wires it as a native MCP tool (kj_rag_query) so querying the index is the agent’s cheapest path. Works out of the box: local Ollama, or the built-in ONNX embedder when nothing can be installed; cloud embedders require an explicit sensitivity declaration and PII-redact every chunk. A distilled engineering canon rides along: kj rag query --library serves pattern cards (when it applies, when it does NOT, the canonical citation) so plans name a greenfield alternative instead of following the legacy line by inertia.
• Card first, on YOUR board — every piece of work is tracked before it starts: kj’s HU Board (kj hu add|move|list), the Planning Game, or the board the project already uses (Linear, Trello, Jira, GitHub Issues) via your agent’s own MCP/tools. Declared, verified at install, never optional — Karajan does not run without a board. ADRs live in git (kj adr add|list).
• Tests prove behavior — the failing test exists first; the suite is never left red.
• Deterministic first, then cross-AI review — kj review --staged runs SonarQube on the changed files before any AI opinion (BLOCKER/CRITICAL reject on the spot), then binds a verdict from a different AI to the sha256 of the exact diff — stamped with the workspace it ran from. Without an approved verdict, the commit does not enter (pre-commit gate).