<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Compliance Automation on AI Governance, HITRUST, and ONC Support</title><link>https://aiassuranceauditor.com/tags/compliance-automation/</link><description>Recent content in Compliance Automation on AI Governance, HITRUST, and ONC Support</description><generator>Hugo</generator><language>en</language><copyright>&lt;a href="https://creativecommons.org/licenses/by-nc/4.0/" target="_blank" rel="noopener">CC BY-NC 4.0&lt;/a></copyright><lastBuildDate>Mon, 18 May 2026 08:00:00 -0400</lastBuildDate><atom:link href="https://aiassuranceauditor.com/tags/compliance-automation/index.xml" rel="self" type="application/rss+xml"/><item><title>Use the LLM Once. Then Never Again.</title><link>https://aiassuranceauditor.com/posts/2026/05/use-the-llm-once/</link><pubDate>Mon, 18 May 2026 08:00:00 -0400</pubDate><guid>https://aiassuranceauditor.com/posts/2026/05/use-the-llm-once/</guid><description>&lt;p>When you build with Claude, the default move is to put the model in the request path. User clicks a button, server calls the API, response goes back. It feels modern. It also makes every click cost money, take seconds, and produce a subtly different answer each time.&lt;/p>
&lt;p>There&amp;rsquo;s a quieter pattern that works better for a lot of the AI work we&amp;rsquo;ve shipped: &lt;strong>call Claude once during development, bake the answer into a JSON file checked into the repo, and at runtime do nothing but a dictionary lookup.&lt;/strong> The model isn&amp;rsquo;t in the path. It&amp;rsquo;s in the build.&lt;/p></description></item></channel></rss>