Terms  /  System Transparency  /  Accountability Gap
06 · System Transparency

Accountability Gap

No one — human or system — can explain why a specific output was produced.

The Accountability Gap is the ultimate consequence of opacity. When something goes wrong — a bug, a security vulnerability, a broken deployment — and nobody can explain how it happened, you've fallen into the Accountability Gap. The human didn't write the code. The agent can't explain its reasoning after the fact. The system doesn't log its decision process. The result is an outcome with no author, no explanation, and no clear path to prevention. In regulated industries, the Accountability Gap isn't just problematic — it's potentially illegal.

Example
A production system fails because an AI-generated configuration had an incorrect timeout value. The team investigates: the developer didn't set the value (the agent did). The agent's reasoning isn't logged. The prompt that led to the configuration is lost (session expired). The system doesn't record which model version was used or what context was provided. Nobody can explain why the timeout was set to 50ms instead of 5000ms. The post-mortem concludes with "we think the AI made an error" — which is not an explanation, it's an admission of an Accountability Gap.

More in System Transparency