<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Audit Trails on Fabian G. Williams</title><link>https://www.fabswill.com/tags/audit-trails/</link><description>Recent content in Audit Trails on Fabian G. Williams</description><image><title>Fabian G. Williams</title><url>https://www.fabswill.com/img/main/logo.jpg</url><link>https://www.fabswill.com/img/main/logo.jpg</link></image><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sat, 16 May 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://www.fabswill.com/tags/audit-trails/index.xml" rel="self" type="application/rss+xml"/><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>I built a public MCP-callable storefront. The same endpoint produced an identical audit-trail receipt from hosted Claude Desktop AND from Qwen3.6 27B running fully offline on my MacBook. Same six supervision checks. Same receipt page. One artifact that satisfies both the security audit and the finance billing conversation.</description></item></channel></rss>