Incident Twins: What Logs Can Establish After an Agent Stops
Rohith Yanambaka Venkata
Submitted to AI Incident Response Sprint. Sprint projects are early-stage work by participants, not Apart Research publications.
After an agent stops, what can its logs establish about accepted work? Incident Twins checks whether retained evidence rules out in-scope commitments during a fixed post-stop interval. Study 1 uses scripted responses in Pydantic AI. Three asynchronous pairs have byte-identical configured native/controller records but opposite outcomes. Terminal receipts and a separate pending-work check distinguish outcome evidence from collection coverage. Study 2 tests whether effects can commit without audit records. In 30 process-interruption runs, separate transactions leave such gaps. A joint effect/audit transaction with a complete scoped snapshot resolves all 15 comparator runs. A simple query matches all 30 measured runs, but concludes on a contradictory control that the richer checker rejects. Study 2’s raw records differ: its opposing examples match only on declared selected fields. Neither study establishes permanent containment or permission to resume. I list what an operator should retain. The resulting verdict depends on explicit scope and trust.
Reviews
I like that the project asks a very specific and practical question: what can we actually conclude from the evidence after an agent has stopped? The experiments are thoughtful, especially the use of paired outcomes and contradictory controls rather than only showing successful cases. My main suggestion would be to test this on more realistic agent systems and failure modes, since the current setup is still fairly controlled.
Cite this project
@misc{venkata2026incident,
title = {{Incident Twins: What Logs Can Establish After an Agent Stops}},
author = {Rohith Yanambaka Venkata},
year = {2026},
month = sep,
note = {Submitted to AI Incident Response Sprint, an Apart Research Sprint},
howpublished = {\url{https://apartresearch.com/sprints/projects/incident-twins-what-logs-can-establish-after-an-agent-stops-bywm}},
url = {https://apartresearch.com/sprints/projects/incident-twins-what-logs-can-establish-after-an-agent-stops-bywm}
}More from AI Incident Response Sprint
- View project: Adaptive AI-Based Containment of Autonomous Cyber Attacks: A Reproducible Docker Cyber Range Study
Adaptive AI-Based Containment of Autonomous Cyber Attacks: A Reproducible Docker Cyber Range Study
Saarlanders
The study evaluates whether an incident-history-reasoning defender outperforms a fixed response policy against an autonomous LLM attacker changing paths after containment. Using a minimal, isolated Docker cyber range …
- View project: When the Evaluation Is the Incident: Testing AI Incident-Reporting Regimes on the OpenAI–Hugging Face Intrusion
When the Evaluation Is the Incident: Testing AI Incident-Reporting Regimes on the OpenAI–Hugging Face Intrusion
Arathi
AI incident-reporting regimes are being introduced in fast succession to address the concerns that exist in the public sphere and government on the risks associated with frontier AI systems, yet we have limited insight …
- View project: A Recomputable Containment Record for Evaluation Sandboxes
A Recomputable Containment Record for Evaluation Sandboxes
Shadow
In this paper, I address the critical issue of AI agents escaping evaluation sandboxes (as seen in the July 2026 incidents where monitors failed) by proposing an externally audit-able containment layer that doesn't rely …