Principal Product Manager, Microsoft Subscribe to my YouTube.
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.
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.
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.
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.
Update, 2026-05-19: A2A agent-card now live at mcp.adotob.com/.well-known/agent.json, published 24 hours after Nate B Jones’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.
Fabian G. Williams aka Fabs Site