<?xml version="1.0" encoding="utf-8" standalone="yes" ?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>AWS Bedrock on Fabian G. Williams</title>
    <link>https://www.fabswill.com/tags/aws-bedrock/</link>
    <description>Recent content in AWS Bedrock on Fabian G. Williams</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en</language>
    <lastBuildDate>Thu, 21 May 2026 00:00:00 +0000</lastBuildDate>
    
	<atom:link href="https://www.fabswill.com/tags/aws-bedrock/index.xml" rel="self" type="application/rss+xml" />
    
    
    <item>
      <title>Paying Down Supervision Debt: Why the Five Control Points That Decide Whether Your Agent Ships Have Nothing to Do With Your Model</title>
      <link>https://www.fabswill.com/blog/paying-down-supervision-debt-five-control-points/</link>
      <pubDate>Thu, 21 May 2026 00:00:00 +0000</pubDate>
      
      <guid>https://www.fabswill.com/blog/paying-down-supervision-debt-five-control-points/</guid>
      <description>By the end of this post you will know which of the five infrastructure control points your agent stack is shipping without, and you will have a concrete pattern for paying down the observability piece of that debt: a public, consumer-readable audit-trail receipt that satisfies both your security team and your finance team with the same document. The receipt was already in production when the broader practitioner conversation started naming the gap.</description>
    </item>
    
  </channel>
</rss>