<?xml version="1.0" encoding="utf-8" standalone="yes" ?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>observability on Fabian G. Williams</title>
    <link>https://www.fabswill.com/tags/observability/</link>
    <description>Recent content in observability on Fabian G. Williams</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en</language>
    <lastBuildDate>Sun, 07 Jun 2026 00:00:00 +0000</lastBuildDate>
    
	<atom:link href="https://www.fabswill.com/tags/observability/index.xml" rel="self" type="application/rss+xml" />
    
    
    <item>
      <title>Your Agent Said It Did the Work. I Checked the Disk.</title>
      <link>https://www.fabswill.com/blog/your-agent-said-it-did-the-work/</link>
      <pubDate>Sun, 07 Jun 2026 00:00:00 +0000</pubDate>
      
      <guid>https://www.fabswill.com/blog/your-agent-said-it-did-the-work/</guid>
      <description>Every morning one of my agents sends me a clean status report. Posts cross-posted. Messages delivered. Contacts processed. For a while I read those reports the way you read a receipt from a cashier you trust. Then the automation started giving me time back, so I sat down to run a retrospective and checked the reports against what was actually on disk. The trust did not survive contact with the evidence.</description>
    </item>
    
    <item>
      <title>Sense Before Act: Four Artifacts Every Agent Iteration Must Produce Before It Decides</title>
      <link>https://www.fabswill.com/blog/sense-before-act-four-artifacts-every-agent-iteration/</link>
      <pubDate>Tue, 26 May 2026 00:00:00 +0000</pubDate>
      
      <guid>https://www.fabswill.com/blog/sense-before-act-four-artifacts-every-agent-iteration/</guid>
      <description>By the end of this post you will know what every iteration of every production agent must produce BEFORE it decides anything: four small artifacts that catch the failures sharper prompts cannot prevent. You will know why &amp;ldquo;tell the model to be careful&amp;rdquo; never worked as a defense, and why the only durable fix is structural. And you will know what the discipline looks like in code, because we have been running it at MACONA for months and the receipts are public.</description>
    </item>
    
    <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>
    
    <item>
      <title>One Agent Receipt, Two Buyers: Why Protocol-Neutral MCP Audit Trails Matter for Both Security AND Finance</title>
      <link>https://www.fabswill.com/blog/one-agent-receipt-two-buyers-protocol-neutral-mcp-audit-trails/</link>
      <pubDate>Sat, 16 May 2026 00:00:00 +0000</pubDate>
      
      <guid>https://www.fabswill.com/blog/one-agent-receipt-two-buyers-protocol-neutral-mcp-audit-trails/</guid>
      <description>Update, 2026-05-19: A2A agent-card now live at mcp.adotob.com/.well-known/agent.json, published 24 hours after Nate B Jones&amp;rsquo;s IO-2026 video named the agent-card primitive as the second of the four core agent-protocol layers. Three of the four layers of the open-protocol stack are now live in the storefront: MCP for tool access, A2A for agent discovery, and AG-UI manifested as the public receipt page. AP2/X402 is reserved for the MVP-2 paid Stripe flow.</description>
    </item>
    
    <item>
      <title>Agent &#43; Local Model &#43; Evals — One‑Pager</title>
      <link>https://www.fabswill.com/blog/2025-08-10-agent-plus-local-model-plus-evals-onepager/</link>
      <pubDate>Sun, 10 Aug 2025 00:00:00 +0000</pubDate>
      
      <guid>https://www.fabswill.com/blog/2025-08-10-agent-plus-local-model-plus-evals-onepager/</guid>
      <description>🚀 Purpose If you’ve ever wondered how to compare a locally‑hosted LLM with a hosted OpenAI model side‑by‑side, while keeping the whole experiment observable from end‑to‑end, you’re in the right place. This one‑pager walks you through the starter repo that stitches together three distinct paths:
   Path Stack Observability     A .NET 8 + Semantic Kernel + Ollama (local model) Azure Monitor (OTEL)   B OpenAI Agents SDK (TypeScript/Node) OpenAI Logs → optional OTLP → Azure Monitor   C Python Evals (OpenAI‑provided) Same prompts, same metrics    The goal?</description>
    </item>
    
    <item>
      <title>Debugging GenAI with NLWeb and OpenTelemetry: A Real-Time Visibility Win</title>
      <link>https://www.fabswill.com/blog/capswithopentelemetryandnlweb/</link>
      <pubDate>Wed, 21 May 2025 00:00:00 +0000</pubDate>
      
      <guid>https://www.fabswill.com/blog/capswithopentelemetryandnlweb/</guid>
      <description>🧠 Debugging GenAI with NLWeb and OpenTelemetry: A Real-Time Visibility Win 
 “If you can’t see it, you can’t debug it.”
That’s been the challenge with GenAI and Copilot-style plugins — until now.
 🎯 Goal I wanted to trace and troubleshoot my Copilot agent plugin activity using OpenTelemetry.
The stretch goal? Pipe that into a natural-language search experience using NLWeb,
so I could ask questions like:
 &amp;ldquo;What plugins were used?</description>
    </item>
    
  </channel>
</rss>