Devops

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 ’living’ 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.

A skill for an AI agent is a markdown file. That’s exactly the problem: anyone can drop one, nobody knows if it’s any good. Here’s how I turn them into a curated, signed, shareable library — and why the point isn’t the skills, it’s the curation.

npm yanks malicious versions within 24-48 hours; PyPI quarantines new uploads within hours. A seven-day cooldown — five config lines — turns that window into your defence.

An LXC, Tailscale, tmux, and an SSH key per device. Persistent, multi-device, nothing in a black box.

Why I want a place of my own next to GitHub and LinkedIn — and what’ll show up here.