Enterprise AI Governance  ·  August 14, 2026

The Investigation Gap:
Why Enterprise AI Needs Evidence Accountability

LLMs produce fluent answers, not defensible ones. Introducing Investigation Provenance, Answer Debt, and Kill Threshold Governance: the three primitives enterprises need before AI conclusions can be trusted in regulated decisions.

Arjun Jaggi  ·  18 min read  ·  Framework + Decision Tools
0
Existing enterprise AI frameworks with formal evidence provenance requirements
6
Evidence record tables required for a traceable AI investigation
4
Human checkpoints required before any claim becomes a deliverable
605
Tests passing in the only open-source implementation of this pattern (Zorp, pre-alpha)

Executive Brief

Every enterprise using AI to answer hard questions (due diligence, clinical pathway evaluation, fraud signal validation, exposure estimation) faces a structural problem that no current governance framework names or resolves. The problem is not that AI gives wrong answers. The problem is that AI gives answers with no accountable record of how they were reached.

A wrong answer with a traceable evidence record is a recoverable error. A wrong answer with no record is a liability. The distinction matters in every regulated industry, in every board-level AI review, and in every context where a human signature follows an AI conclusion.

This article introduces three original constructs that close this gap. Investigation Provenance is the traceable chain from question to evidence to claim that makes an AI conclusion auditable. Answer Debt is the organizational liability that accumulates when AI conclusions circulate without that chain. Kill Threshold Governance is the discipline of committing stopping criteria before an investigation begins, so results cannot be silently cherry-picked after the fact.

These constructs are grounded in an emerging open-source implementation called Zorp (aviskaar/zorp, MIT, pre-alpha), which applies pre-registration discipline borrowed from clinical trial methodology to AI-driven investigation. The patterns it demonstrates are not product-specific. They describe an architectural layer that enterprise AI is currently missing.

"A confident answer is not a defensible one. An LLM will produce a fluent answer to a hard question in seconds. What it will not do is tell you whether to believe it, what evidence it weighed, or what it found that pointed the other way."

The Gap No Framework Names

enterprise AI governance frameworks [1] addresses risk categorization, output monitoring, and human oversight at the organizational level. applicable AI governance standards [2] addresses AI management system requirements. Both are governance frameworks for AI systems. Neither addresses the investigative accountability layer: the question of whether an AI conclusion is traceable to the evidence that produced it, and whether that evidence was gathered under conditions that prevent post-hoc selection.

This is not a minor omission. It is the precise gap that creates enterprise liability in regulated decisions. Consider three common scenarios:

In each case, the answer is plausible. In each case, the answer is not defensible. The distinction becomes material when a regulator asks, a court asks, or a risk committee asks: show me what this conclusion is accountable to.

Definition: Answer Debt

Answer Debt is the organizational liability that accumulates when AI conclusions circulate without a traceable evidence record. Like technical debt, it is invisible until it is called in. Unlike technical debt, it may be called in by a regulator, a court, or a board rather than an engineering team. Answer Debt compounds when AI conclusions are used as inputs to subsequent decisions, because the provenance gap propagates forward through every downstream use of the original conclusion.

Fig. 1: The Investigation Accountability Stack

Fig. 1: The Investigation Accountability Stack
LAYER 4: ANSWER LAYER Delivered Artifact · Co-written from evidence record only Human signs off before any claim leaves the stack LAYER 3: EVIDENCE RECORD tracks · preregistrations · experiments · metrics checkpoints · validations: typed, queryable, retained LAYER 2: INVESTIGATION HARNESS validate · investigate · co-write · deliver human checkpoint gate between every stage LAYER 1: PRE-REGISTRATION hypothesis · metric · kill threshold committed to git before any evidence exists KILL THRESHOLD GOVERNANCE Human-set. Hash-verified. Cannot be moved by the agent. Stops the run when crossed. Records why it was killed.
  • Nosek, B.A., et al. (2018). "The preregistration revolution." Proceedings of the National Academy of Sciences, 115(11), 2600-2606. DOI: 10.1073/pnas.1708274114.
  • Aviskaar (2026). "Zorp: A Research Agent for Scientific Discovery." Open-source project, pre-alpha. MIT license. zorp.dev. github.com/aviskaar/zorp.
  • Excited about AI, innovation, and growth?

    Start a conversation