Proposal: Execution Provenance and Forensic Replay for Significant AI Model Behavior

I am proposing an execution-provenance capability for significant or anomalous AI executions.

The objective is not to expose private chain-of-thought or make every model computation human-readable. The objective is to preserve sufficient observable execution history, dependencies, environmental state and tool activity that an authorized investigator could reconstruct an important execution after the fact, identify the earliest observable divergence, replay or functionally reproduce the behavior where technically feasible, and perturb controlled variables to determine what changed the outcome.

In short: an evidentiary layer around an AI execution.

A conventional conversation transcript establishes what was communicated. Conventional telemetry may establish that particular operations occurred. Neither necessarily provides a unified evidentiary representation of the causal sequence connecting the initial request, interpretation, retrieved information, state transitions, branching decisions, tool actions, external consequences, and final result.

This proposal suggests an internal capability—AI Execution Provenance—designed to preserve sufficient, appropriately controlled evidence of selected model executions to permit subsequent reconstruction, analysis, replay and controlled perturbation.

This proposed capability is not conventional application logging. It is an evidentiary execution-provenance layer that associates causally significant events with an execution graph, allowing authorized investigators to reconstruct an execution after the fact and, where technically feasible, reproduce and perturb it under controlled conditions.

The purpose is not to expose private model reasoning to users, nor to assume that neural-network computation can be represented as a simple human-readable chain of thought.

The purpose is to answer four engineering questions:

What happened?

Why did it happen?

Can it be reproduced?

What changes the outcome?

I have deliberately avoided assuming that OpenAI lacks any of these capabilities. The proposal may already overlap with existing telemetry, evaluation or internal forensic systems. If so, I would be interested in knowing whether the architectural distinction described here—particularly preservation of an authoritative execution record followed by independent reconstruction, replay and perturbation—is already represented internally.

I wrote a PDF document to better explain this that I would be happy to share if anyone reading this is interested. Thank you for reading and I appreciate your time.

Best regards, John

Thanks for the thoughtful proposal. Agents SDK tracing covers part of the observable execution record: https://openai.github.io/openai-agents-python/tracing/. The broader forensic replay and controlled-perturbation proposal goes further. Thanks for sharing this—we’ll pass the remaining request to the product team. We don’t have a timeline to share.