[D] Your logging setup is not governance. Here’s the difference.
Summary
Discusses the difference between observability (logging agent actions) and governance (blocking prohibited actions before execution), emphasizing that teams often conflate them and should treat them as separate problems with separate tooling.
Similar Articles
Are you storing AI agent action logs in the same DB as your application? Because that's not an audit log.
Discusses the importance of proper audit logging for AI agents, emphasizing the need for append-only, hash-chained logs that prevent tampering, rather than storing logs in the same writable application database.
Most agent observability feels like crash footage
The author argues that current agent observability provides a trace of actions but lacks runtime justification for why actions were permitted, which is critical for production deployments involving money, data, or communications.
When an agent documents its own audit log, things get weird
The author discusses a failure mode encountered while building Sentience Governor, a Python library for Claude Code that monitors agent actions and produces audit reports. The AI sometimes reconstructed explanations from raw traces, blurring the line between measured facts and probabilistic interpretation.
Mechanical Enforcement for LLM Governance:Evidence of Governance-Task Decoupling in Financial Decision Systems
This paper introduces five governance metrics to quantify policy compliance at the decision rationale level for LLMs in regulated financial workflows, finding that mechanical enforcement (operating outside the model's interpretive loop) reduces non-informative deferrals by 73% and reveals governance-task decoupling: text-only governance degrades on both dimensions under stress, while mechanical enforcement preserves governance quality even as task performance drops.
The Log Is the Agent
This paper introduces ActiveGraph, a runtime that makes the append-only event log the central source of truth for agentic systems, enabling deterministic replay, cheap forking, and end-to-end lineage from goals to model calls.