P111 Escalation and attribution of findings
What escalation ladder, graded-evidence aggregation and attribution procedure resolve ambiguous findings and assign a violation to the responsible party?
Escalation ladders for ambiguous findings, aggregation of graded evidence, and attribution of a violation to the responsible party.
Status
Analyzed A draft treaty article (Article XI, modelled on Articles IX, XII and XIV of the Chemical Weapons Convention): notification, 36-hour acknowledgement and 5-day clarification, Executive Council adjudication with a challenge inspection, then graded measures (added monitoring, hardware relinquishment, sanctions, protective actions); a proposal, untested. Aggregating graded evidence (many sub-threshold acts) and attributing a violation to the responsible actor (cloud provider versus customer, runs split across providers) have no design; Moon et al.'s call for an agency able to unmask evaders is framing.
The Concerned Party notifies the Requested Party of their concern, while also sharing their concern with the Director-General and Executive Council. The Requested Party will acknowledge this notification within 36 hours, and provide clarification within 5 days.
Raised in: Baker, Kulp, Marks, Brundage & Heim (2025), Verifying International Agreements on AI: Six Layers of Verification for Rules on Large-Scale AI Development and Deployment (RAND WR-A4077-1); Scher & Thiergart (2024), Mechanisms to Verify International Agreements About AI Development (MIRI); Aarne & Petrie (2025), International Security Applications of Flexible Hardware-Enabled Guarantees (flexHEG Part 3); Cankaya (2026), Compute Verification FAQs; Ansari (2026), Hardware-Level Governance of AI Compute: A Feasibility Taxonomy for Regulatory Compliance and Treaty Verification; Daley (2026), Proving the Negative: Three Warnings from Arms Control for the Age of AI (War on the Rocks); Moon, Vedula, Geneson & Bar-on (2025), Strategies and Detection Gaps in a Game-Theoretic Model of Compute Governance (RAND RRA3686-1).
Sub-questions
| ID | Sub-question | What the sources report |
|---|---|---|
| P111.1 | With a stated number of providers sharing flagged-account records, what is the detection probability for a run split across providers/jurisdictions, and how is it accounted for? | open |
Sub-questions not yet stated precisely enough to check
| ID | Sub-question |
|---|---|
| P111.2 | What pre-agreed escalation ladder / incremental-disclosure procedure resolves ambiguous findings (clarification, focused investigation, intrusive measures, pauses), including access rights when a classifier flags a violation? |
| P111.3 | How should graded evidence (many small sub-threshold violations, a continuum of suspicious acts) be aggregated into a compliance decision? |
| P111.4 | How is a violation attributed to the responsible party (cloud provider vs user; corporate vs state-backed; which actor controls which devices)? |
| P111.5 | Can know-your-customer rules withstand evaders using shell organizations, and does that require an agency able to unmask the evader and compel disclosure? |
Possibly relevant work found by automated search
Found by AI agents searching for this problem's sub-questions, mostly by keyword and citation in the OpenAlex scholarly database and on the web; a second AI pass reviewed each one, and we spot-checked some by hand. They seemed reasonably related, as far as one can tell from outside each paper's field. Some come from neighbouring fields, such as arms control and financial audit, and bear on the problem by analogy. Not reviewed against the status above; a paper listed here does not change that status. 928 of 1052 quotes checked word for word against the paper's text.
For P111.1: With a stated number of providers sharing flagged-account records, what is the detection probability for a run split across providers/jurisdictions, and how is it accounted for?
For P111.2: What pre-agreed escalation ladder / incremental-disclosure procedure resolves ambiguous findings (clarification, focused investigation, intrusive measures, pauses), including access rights when a classifier flags a violation?
For P111.3: How should graded evidence (many small sub-threshold violations, a continuum of suspicious acts) be aggregated into a compliance decision?
* Full text not reviewed; more likely to contain errors.
Data
- problems.csv — one row per problem
- problem_status.csv — status, scope and evidence per problem
- problem_sources.csv — the posed-by quote and other documents per problem
- leaves.csv — all sub-questions, including those without a checkable form
- leaf_sources.csv — every source row behind each sub-question