The Containment Burden Sits on the Wrong Side of the Boundary & AI Escape Detection Harness

Putting the lab and victim timelines on one axis with cost and evidence grades is a useful contribution, and the self-audit is a model for incident analysis: dropping the unsupported time axis and the post-dated kernel row makes the remaining claims more credible.

The "timing, not cost" finding is partly true by construction, since the chain starts inside the lab and the victim can only act after the boundary is crossed. The cost overlap is the more interesting result, and it would be stronger with operator input. Getting one or two platform engineers to re-score the bands would test it directly.

Substitution is the other open question. Agents that lost one launchpad might have found another, which weakens I-01 and V-14. Noting which controls hold under substitution would sharpen the bundle in Section 4.

I think this project usefully asks who could have acted before the OpenAI-Hugging Face intrusion reached third parties. It maps possible controls to stages of the incident and identifies which organization could apply them. The acknowledgment that precise timestamps do not establish what a different response would have achieved makes the analysis more credible.

The distinction between labs preventing harm and affected platforms merely shortening it is too strong. A platform could also restrict access or remove vulnerable functionality before an attack. I would frame the finding around earlier opportunities for lab intervention, rather than treating prevention as something only the lab can provide.

The project offers a useful synthesis linking potential controls to incident stages, responsible actors, implementation effort, and evidence strength. Its timestamp audit, rejection of unsupported action indices, and explicit treatment of uncertainty are notable strengths.