<?xml version="1.0" encoding="UTF-8"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Brent Burgess</title><description>Writing and case studies on data architecture and AI automation.</description><link>https://brentburgess.com</link><language>en</language><atom:link href="https://brentburgess.com/rss.xml" rel="self" type="application/rss+xml"/><item><title>A sample audit plan: a small site’s analytics with promises to keep</title><link>https://brentburgess.com/writing/audit-plan-analytics-with-promises-to-keep</link><guid isPermaLink="true">https://brentburgess.com/writing/audit-plan-analytics-with-promises-to-keep</guid><description>The written plan an audit ends in, done for real on this site’s own analytics pipeline: five findings, the order to fix them, and what to automate first.</description><pubDate>Mon, 19 Oct 2026 12:00:00 GMT</pubDate><category>Writing</category></item><item><title>Only what the site publishes: a read-only MCP server for AI agents</title><link>https://brentburgess.com/work/mcp-server</link><guid isPermaLink="true">https://brentburgess.com/work/mcp-server</guid><description>How this site answers AI agents: a read-only MCP server on its Cloudflare Worker, built from one public file and held to the site’s publishing rules by tests.</description><pubDate>Mon, 19 Oct 2026 12:00:00 GMT</pubDate><category>Case study</category></item><item><title>Tested before it is published: this site’s nightly data pipeline</title><link>https://brentburgess.com/work/nightly-data-pipeline</link><guid isPermaLink="true">https://brentburgess.com/work/nightly-data-pipeline</guid><description>How a nightly Python, dbt and DuckDB pipeline keeps this site’s analytics as a permanent record and tests every number against the privacy page’s rules.</description><pubDate>Mon, 19 Oct 2026 12:00:00 GMT</pubDate><category>Case study</category></item><item><title>Five rules from an AI pipeline, applied to a data platform</title><link>https://brentburgess.com/writing/five-rules-from-an-ai-pipeline</link><guid isPermaLink="true">https://brentburgess.com/writing/five-rules-from-an-ai-pipeline</guid><description>Five rules I would carry into any data platform, each learned in production on my AI and Python publishing pipeline, and what each looks like in a warehouse.</description><pubDate>Fri, 16 Oct 2026 12:00:00 GMT</pubDate><category>Writing</category></item><item><title>One track, five releases: Sleep Anchor’s AI and Python pipeline</title><link>https://brentburgess.com/work/sleep-anchor</link><guid isPermaLink="true">https://brentburgess.com/work/sleep-anchor</guid><description>How one person runs a sleep-music catalog: AI generates each track, and a Python pipeline checks, renders and publishes it to YouTube, podcasts and streaming.</description><pubDate>Sun, 11 Oct 2026 12:00:00 GMT</pubDate><category>Case study</category></item></channel></rss>