The Agent Read the Whole Spec. It Didn't Need To.
Part 6 of the KCP series. Previous: What Happens When Your Agent Needs Knowledge From Five Teams?
Part 6 of the KCP series. Previous: What Happens When Your Agent Needs Knowledge From Five Teams?
Part 8 of the KCP series. Previous: Who Let the Agent In?
Part 4 of the KCP series. Previous: Add knowledge.yaml to Your Project in Five Minutes
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.
Part 5 of the KCP series. Previous: How Do You Tell an Agent "This Data Cannot Leave the Building"?
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.
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.
Part 7 of the KCP series. Previous: The Agent Read the Whole Spec. It Didn't Need To.
A practical walkthrough of the KCP adoption gradient — from the minimum viable manifest to a full knowledge graph. No theory. Just the steps.
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.