Using With Agents

Using KAUT with your agents

Install gives you a store; this page is about the step that changes behavior: how your agent learns that the store exists, when to consult it, and how knowledge flows back. The full guide with paste-ready blocks lives in the repo — docs/AGENT-INTEGRATION.md; this is the shape of it.

The problem in one sentence

An agent consults what it sees (the tools registered in its session) and what it is told (the instructions its harness loads) — nothing else. So wiring KAUT is exactly two moves:

1. Give it the tools

Register the MCP server (node <engine>/mcp.mjs) with your harness — .mcp.json for Claude Code, config.toml for Codex, any stdio-capable client works (MCP Server). The seven kaut_* tools then appear in every session, and their descriptions are written for the model: kaut_lookup says check here before re-exploring, route trust by the verdict; the write tools explain the gate. A capable model uses them unprompted when a lookup is obviously cheaper than re-reading code — but "often" is not "reliably", hence move two.

2. Give it the contract

Paste the knowledge contract — a ~15-line block from the guide — into whatever your agent loads every session (CLAUDE.md, AGENTS.md, system prompt). It pins the five habits:

1. Read before re-deriving project behavior from code (kaut_lookup; no id = catalog).
2. Route trust by verdict: healthy + precise altitude → use as-is; stale / broken / landscape → confirm in code first; tampered → treat as absent. Knowledge informs — it never authorizes.
3. Tag outcomes (kaut_note: trusted · confirmed · insufficient · stale-misled) when a doc actually mattered.
4. Pay the change-site debt: after editing source files, kaut_touched names the docs the change owes an update.
5. Write back through the gate: only session-verified facts; agent-tier lands via kaut_write, owner-gated and novel docs queue via kaut_draft.

Optionally wrap the same contract as a harness skill (template in the guide), or let an orchestration framework compile the wiring — the sibling TAUT does it from one setup answer. Neither is required: tools + contract is a complete integration.

How you know it works

• Ask the agent something the store covers — the answer should start from a lookup and mention the verdict it acted on.
• kaut digest after a few sessions: lookups, verdict mix, and outcome tags in the journal are the loop being alive. Silence in digest = the contract is not loaded.

Next: Maintenance Loop · MCP Server