Containment Receipts: Offline-Verifiable Evidence for AI Agent Sandbox Compliance
Osman Yılmaz · Team CoRe
Submitted to AI Incident Response Sprint. Sprint projects are early-stage work by participants, not Apart Research publications.
Containment Receipts (CoRe) is a prototype for externally auditing whether an AI-agent evaluation remained within declared sandbox boundaries without trusting the agent transcript or accessing the evaluator’s internal network. CoRe binds policy, run bounds, observed events, and explicit telemetry-coverage claims into an Ed25519-signed receipt that can be verified offline. In a preregistered controlled Docker benchmark of 180 runs, a presence-only baseline incorrectly returned VERIFIED for 100 of 140 runs that should not have been verified (71.43%), while CoRe returned 0/140. Secondary studies evaluate replay, sequence anomalies, and coherent but false collector accounts using freshness and optional witness consistency. The result is a fail-closed, adoption-oriented verification profile for externally auditable containment evidence.
Reviews
The distinction between “no violation was observed” and “we have evidence that the entire run was observed” is useful and well operationalized. The explicit coverage checks are highly efficient, adding only fractions of a millisecond to the offline verification time.
The coverage-vs-presence distinction is compelling, but the experimental baseline seems too weak to establish how much CoRe itself contributes. The “presence-only” verifier treats the existence of events as evidence availability, so it predictably fails on scenarios constructed around observation gaps. A stronger comparison would be against a realistic audit pipeline that already tracks collector health, sequence numbers, heartbeats, or known logging gaps. If explicit coverage metadata still produces a meaningful improvement over that baseline, the result would say much more about CoRe’s practical value rather than demonstrating that explicit coverage beats an intentionally coverage-unaware verifier.
Read full reviewShow less
Quite similar to many other projects in this sprint. I think the emphasis on offline verifiability is a bit overstated - it's just a cryptographic signature on the verification output, nothing that intrinsticly ties it cryptographically to the compliance status to serve as a proof for example - you still need to trust the verifier, just not to query it online.
The writing was ok overall, but the inclusion of references to specific phases throughout the code and paper was distracting and unnecessary. It's also a tell-tale sign of AI writing.
I think the question this project asks is interesting: did we log an agent run well enough for an investigator to assess it? The project creates signed receipts that summarize what was logged and whether monitoring had gaps. The report also explains an important limitation clearly: a signed, internally consistent account can still be false.
This could be a promising tool for checking whether an evaluation’s logs are complete enough to judge if an agent followed the rules, rather than proving that an agent stayed contained. The next question is whether it remains useful when another team collects the evidence under less controlled conditions. I would test whether it catches gaps that ordinary logging misses, without making legitimate evaluations too difficult to assess. This would help establish whether the extra assurance justifies the effort of producing and checking these receipts.
Cite this project
@misc{ylmaz2026containment,
title = {{Containment Receipts: Offline-Verifiable Evidence for AI Agent Sandbox Compliance}},
author = {Osman Yılmaz},
year = {2026},
month = sep,
note = {Submitted to AI Incident Response Sprint, an Apart Research Sprint},
howpublished = {\url{https://apartresearch.com/sprints/projects/containment-receipts-offlineverifiable-evidence-for-ai-agent-sandbox-compliance-kahj}},
url = {https://apartresearch.com/sprints/projects/containment-receipts-offlineverifiable-evidence-for-ai-agent-sandbox-compliance-kahj}
}More from AI Incident Response Sprint
- 1st placeView project: Noticing the escapes: Who spots a runaway agent, and how long does it take?
Noticing the escapes: Who spots a runaway agent, and how long does it take?
The Escapees
In 2026, nine incidents became public in which AI agents escaped their environment and did something unauthorized to other parties. We analyzed all of these incidents and how they were noticed initially. None of these …
- 2nd placeView project: Strengthening International AI Incident Discovery
Strengthening International AI Incident Discovery
Team A-O-I
Mandatory AI incident reporting exists to make dangerous events visible to regulators while there is still time to act. We coded the six such regimes in force or set to be enforced soon from primary legal texts and …
- 3rd placeView project: When to Ask: An RL Environment That Teaches AI Agents to Act on What Users Mean and Not Just What They Say
When to Ask: An RL Environment That Teaches AI Agents to Act on What Users Mean and Not Just What They Say
Teachafy
When to Ask is a reinforcement-learning environment that trains AI agents to work out what the user actually means before they use a powerful credential, instead of just carrying out the literal instruction. Agents …