<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Documentation on westerweel.work</title><link>https://westerweel.work/en/tags/documentation/</link><description>Recent content in Documentation on westerweel.work</description><generator>Hugo</generator><language>en</language><lastBuildDate>Tue, 14 Jul 2026 16:01:55 +0200</lastBuildDate><atom:link href="https://westerweel.work/en/tags/documentation/index.xml" rel="self" type="application/rss+xml"/><item><title>Documentation that lies is worse than no documentation</title><link>https://westerweel.work/en/posts/2026-07-14-living-documentation-with-gates-and-agents/</link><pubDate>Tue, 14 Jul 2026 00:00:00 +0000</pubDate><guid>https://westerweel.work/en/posts/2026-07-14-living-documentation-with-gates-and-agents/</guid><description>Stale documentation has always been a slow-burning problem, but now that AI agents read that documentation as ground truth, it has become an acute one. How we made documentation &amp;rsquo;living&amp;rsquo; with an enforceable contract, gates that block unverified changes, and an MCP server that gives agents context with provenance — so they cite instead of guess. From 63 findings to zero. And why this pattern doubles as the foundation for a chatbot on your cluster: talking to the devops colleague who is on holiday, with sources attached.</description></item></channel></rss>