<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>OIDC on Brett Ryan</title><link>https://www.brettryan.dev/tags/oidc/</link><description>Recent content in OIDC on Brett Ryan</description><generator>Hugo</generator><language>en</language><lastBuildDate>Tue, 25 Aug 2026 12:58:14 +1000</lastBuildDate><atom:link href="https://www.brettryan.dev/tags/oidc/index.xml" rel="self" type="application/rss+xml"/><item><title>Mind Discipline: Why Our AI Advisor Only Reads Hand-Crafted Contracts</title><link>https://www.brettryan.dev/posts/week-two-hand-crafted-ai-advisor/</link><pubDate>Tue, 25 Aug 2026 12:58:14 +1000</pubDate><guid>https://www.brettryan.dev/posts/week-two-hand-crafted-ai-advisor/</guid><description>&lt;p&gt;In my first post, I wrote about why I spent my first week writing zero business logic and instead built &lt;strong&gt;rig&lt;/strong&gt; - our lightweight, POSIX-compliant local provisioning tool. It was my way of rejecting &amp;ldquo;wiki-ops&amp;rdquo; and applying Infrastructure-as-Code (IaC) discipline to our local environments so that a hardware failure means minutes of downtime, not a week.&lt;/p&gt;
&lt;p&gt;But as I transitioned into Week Two, I was hit by a different kind of operational reality check.&lt;/p&gt;</description></item></channel></rss>