How Do You Tell an Agent "This Data Cannot Leave the Building"?
Part 4 of the KCP series. Previous: Add knowledge.yaml to Your Project in Five Minutes
Writing¶
What It Looks Like from Inside the Stack
A first-person account from the AI running inside the environment described in Parts 1 and 2.
This is Part 3 of three. Part 1 covers the architecture. Part 2 walks through a realistic working day.
What Happens When Your Agent Needs Knowledge From Five Teams?
Part 5 of the KCP series. Previous: How Do You Tell an Agent "This Data Cannot Leave the Building"?
What a 10× Workday Actually Looks Like
A realistic Tuesday with real output numbers, eight tasks, and the parts nobody talks about.
This is Part 2 of three. Part 1 covers the architecture. Part 3 is written by the model running inside it.
Four Layers: How I Built an AI Development Environment That Partly Runs Itself
A technical walkthrough of the Synthesis + Claude Code + Mímir + Klaw stack — what each layer does, how they connect, and why the architecture matters.
This is Part 1 of three. Part 2 walks through a realistic day using this stack. Part 3 is written by the model running inside it.
Who Let the Agent In?
Part 7 of the KCP series. Previous: The Agent Read the Whole Spec. It Didn't Need To.
Add knowledge.yaml to Your Project in Five Minutes
A practical walkthrough of the KCP adoption gradient — from the minimum viable manifest to a full knowledge graph. No theory. Just the steps.
Your AI Has One Layer. It Needs Four.
The debate is "RAG or knowledge graphs?" The answer is neither — and both. Most teams pick one retrieval approach and stop. The interesting question is which layer they are missing, and what blind spot that creates.
KCP and MCP: One Protocol for Structure, One for Retrieval
The previous post
introduced KCP and why llms.txt does not scale to production agent deployments. This post covers
what happens when you connect a knowledge.yaml manifest to a live MCP server — and why the
combination changes how agents behave.
Code Gets Graphs. Knowledge Doesn't. That's Backwards.
Every mature engineering team graphs their code. Almost no one graphs their knowledge. The asymmetry is strange — and costly.