P048 Monitoring data sources and intelligence
Can non-technical data sources (payment and customer-identity records, financial intelligence, cloud metadata) identify large AI-chip rentals or purchases, and how reliably?
Non-technical monitoring data sources and intelligence.
Terms: KYC (know-your-customer): the customer-identity records firms must collect; used here as a non-technical signal of who is renting or buying large amounts of AI compute.
Status
Analyzed Design and feasibility argument: compute providers as KYC-style intermediaries using billing records and non-confidential metadata to classify large training and inference workloads and account for compute; no recall or precision for identifying chip rentals is measured, and detailed workload properties are said to need confidential computing. Ansari notes metadata collection stops at individual providers (no cross-provider or on-premises coverage); Leklem & Maheshwari propose a monitoring network fed by cloud API patterns and export data; Scher's 'might also use financial intelligence' is a one-line suggestion. Payment-record and financial-intelligence methods have no analysis.
Several of these techniques could be used in real-time to establish whether a customer is engaging in an activity that might be subject to regulatory oversight. If compute providers were to implement these techniques, they could likely distinguish whether their customers are engaging in activities such as training a large model, or engaging in inference at scale, as well as quantify the amount of compute consumed by large workloads
Posed by
- Ansari (2026), Hardware-Level Governance of AI Compute: A Feasibility Taxonomy for Regulatory Compliance and Treaty Verification:
metadata collection is confined to individual providers and does not extend to on-premises compute or cross-provider aggregation
(§3.1 M1, p.4; L234–235) - Wasil, Reed, Miller & Barnett (2024), Verification Methods for International AI Agreements:
Many AI-related purchases may" … "have legitimate alternate uses, making it difficult to distinguish between authorized and unauthorized" … "activities.
(Table 1 (Financial intelligence row); L729–733)
Also raised in: Scher (2026), Verifying Restrictions on Frontier AI Research (MIRI); Leklem & Maheshwari (2026), How Should We 'Inspect' Artificial Intelligence? (AMC Insights).
Sub-questions
| ID | Sub-question | What the sources report |
|---|---|---|
| P048.1 | Can payment / KYC / financial-intelligence records identify AI chip rentals above a stated number of GPU-hours with what recall and precision, given dual-use purchases and bank secrecy? | implied by a source, not stated as open |
| P048.2 | Can cloud-provider metadata collection extend beyond individual providers to on-premises compute and cross-provider aggregation? | partly answered |
Sub-questions not yet stated precisely enough to check
| ID | Sub-question |
|---|---|
| P048.3 | Which data streams (power-grid, semiconductor export, cloud API patterns, voluntary telemetry) should make up a primary global monitoring layer, and what does each detect? |
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 P048.3: Which data streams (power-grid, semiconductor export, cloud API patterns, voluntary telemetry) should make up a primary global monitoring layer, and what does each detect?
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