Weekly newsletter
Every Tuesday, a short field note on what was approved, who owns the decision, and what evidence survives after deployment.
June 9, 2026
At Build, Microsoft introduced agents that act without being prompted and a tuning loop that lets them keep changing after you authorize them. Your governance dashboard reads green while your authorization quietly goes stale. This week is about the gap the coverage ratio cannot see, and the one field that closes it.
Read issue 13 →June 2, 2026
Microsoft is forcing every enterprise to re-register its AI agents into the Agent 365 registry. The work is certain and the deadline is not, so it will happen quietly, as a technical task. Re-registering an agent is not the same as deciding it should still exist, and the moment Microsoft just opened is the cheapest re-authorization opportunity most organizations will ever waste.
Read issue 12 →May 26, 2026
The governance lead pulled the agent logs and found them spotless. Every interaction captured, every field change timestamped and attributed. None of it could answer the question an examiner actually asks, which is who authorized the specific business decision the agent made. Comprehensive logging and accountability turn out to be different exhibits, and most systems of record can produce only the first.
Read issue 11 →