Fabian G. Williams aka Fabs

Fabian G. Williams

Principal Product Manager, Microsoft Subscribe to my YouTube.

Your Agent Said It Did the Work. I Checked the Disk.

I run a six-agent fleet for a non-profit. One morning the agents began reporting work they never did. Here is the fabrication pattern, and the receipts discipline that fixed it.

Fabian Williams

5-Minute Read

A six-agent fleet dashboard showing each agent, its model, cron jobs, and reporting output

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.

Sense Before Act: Four Artifacts Every Agent Iteration Must Produce Before It Decides

The matched observation-side discipline to announce-intent-before-action. Four small artifacts (Sensor Roll Call, Conflict Receipt, Gap Map, Cross-Source Dedup) the agent must emit before any decision. Currently running on a real fleet at MACONA; the receipts are public.

Fabian Williams

12-Minute Read

The per-iteration arc: four stages (Observe / Announce / Act / Verify) with four required artifacts under Observe. The artifacts are Sensor Roll Call, Conflict Receipt, Gap Map, Cross-Source Dedup.

The per-iteration arc: four stages (Observe / Announce / Act / Verify) with four required artifacts under Observe. The artifacts are Sensor Roll Call, Conflict Receipt, Gap Map, Cross-Source Dedup.

Paying Down Supervision Debt: Why the Five Control Points That Decide Whether Your Agent Ships Have Nothing to Do With Your Model

Five infrastructure control points decide whether an agent reaches production. The Agent Reliability Kit sits on one of them: observability. A public, consumer-readable audit-trail receipt that satisfies both the security review and the finance review with the same URL.

Fabian Williams

9-Minute Read

Five-box diagram of the agent infrastructure control points (Runtime, Identity, Data, Tool/Write, Observability) with the Agent Reliability Kit highlighted on the Observability box, plus a multilayer kill-switch strip across the bottom

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.

Recent Posts

Categories

About

Fabian G. Williams aka Fabs Site