Tailor the Framing, Fix the Facts: a Factual-Invariance Gate for Distributing AI Incident Information
Iven Cui · Team Iven
Submitted to AI Incident Response Sprint. Sprint projects are early-stage work by participants, not Apart Research publications.
The July 2026 incident, in which OpenAI evaluation agents escaped a sandbox and spent days inside Hugging Face's production infrastructure, produced an exceptional public record that travelled through security and AI-policy circles and largely stopped there. The obvious fix is to rewrite the material for each audience it missed. The obvious risk is that rewriting for reach moves the facts. We found no prior work that separates the two.
We built that control. The claim ledger is 63 claims. Fifty-six come from six primary sources, each with a verbatim support quote and a status recording whether it is established, a party's assertion about itself, divergent between sources, or contested; seven more record regulatory context from secondary material. It records two disagreements between the OpenAI and Hugging Face accounts that we have not seen noted elsewhere. gate.py then checks a tailored brief's numbers, dates, named entities and attributions against that ledger, using seven deterministic checks, while constraining nothing about tone, length or framing.
We produced two briefs for each of four audience segments, one under a naive engagement-first prompt and one under the gate. Against an audited set of 10 errors the gate reached 100% precision and 70% recall, and all four gated briefs passed.
The findings that matter are where the errors were and what got through. Seven of ten sat in the single general-audience brief, at roughly eight times the rate of the specialist briefs: drift concentrates exactly where reach is most valuable and readers are least equipped to catch it. And a structured review of the four gate-clean briefs found four further errors, three of them the class no atom-level check can reach. A clean gate is necessary and nowhere near sufficient, which is why the artifact ships with an opt-in distribution protocol requiring a named human reviewer.
Artifacts: the ledger, the gate, the scoring harness, eight briefs, and the protocol, all live at https://everto.ca/repo-for-apart-research/ and downloadable as a zip from that page. Every result reproduces with one command.
Reviews
I found the paper difficult to follow, though I tend to agree that communicating the warning shots to various audiences is important and non-trivial.
The paper takes on an interesting, overlooked issue of incident information distribution and 'tailoring drift' across different audiences. The methodology and execution are clear, transparent and reproducible, and the claim ledger may be a useful and reusable artefact. The scope remains limited, however, and the sample is very small. The initial premise about the reach problem - that the record "largely stopped" after going through security and AI-policy circles - is also worth double-checking as there was eventually extensive coverage in mainstream and business outlets.
Cite this project
@misc{cui2026tailor,
title = {{Tailor the Framing, Fix the Facts: a Factual-Invariance Gate for Distributing AI Incident Information}},
author = {Iven Cui},
year = {2026},
month = sep,
note = {Submitted to AI Incident Response Sprint, an Apart Research Sprint},
howpublished = {\url{https://apartresearch.com/sprints/projects/tailor-the-framing-fix-the-facts-a-factualinvariance-gate-for-distributing-ai-incident-information-7i09}},
url = {https://apartresearch.com/sprints/projects/tailor-the-framing-fix-the-facts-a-factualinvariance-gate-for-distributing-ai-incident-information-7i09}
}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 …