P016 Supply-chain assurance overall and neutral hardware
Can an end-to-end chain of assurances cover design, fabrication, packaging and deployment, and who can credibly produce neutral verification hardware?
End-to-end supply-chain assurance and who can build neutral hardware.
Status
Analyzed A design answer to the neutral-producer clause: redundant guarantee processors from each bloc and nested enclosures each built by a different bloc, with the integration details left out of scope; the Proofworks neutral-compute note sketches the alternative of open-sourcing designs down to GDSII and fabricating on trailing nodes, which it judges impossible at the leading edge. The end-to-end chain clause has Ilhan et al.'s (2026) analysis of layered design-phase and manufacturing-phase measures, with the chain itself posed as an open question. Nothing built; no neutral producer identified (the Proofworks prospects note sees no candidate in a US–China scenario). One colour: both clauses are answered by the same hardware supply-chain security community, so the sorting-pass split is not used.
they might instead rely on a design where different countries provide different overlapping components of the design, such that each country can trust the system without trusting all of the components. … security processors could be redundant, such that everything passes through two chips that implement the same specifications, one designed and manufactured by each bloc.
Posed by
- Cankaya (2026), Catching Misreporting About ML Hardware Use by Turning Noise into Signal, Part II:
even with full transparency the system would still be way too complicated for the Verifier to rule out backdoors and collusion with the Prover.
(intro, p.1; lines 29–31)
Also raised in: Harack et al. (2025), Verification for International AI Governance (Oxford AIGI); Shavit (2023), What Does It Take to Catch a Chinchilla? Verifying Rules on Large-Scale Neural Network Training via Compute Monitoring; Ilhan, Withers, Gietz & Harack (2026), Verifiable Semiconductor Manufacturing (Oxford AIGI); Cankaya (2026), A System Overview for Near-Term, Low-Trust AI Compute Verification (v0.2); Cankaya (2026), Research Note: The Fundamentals and Feasibility of Secure Network Taps for Verifying AI Datacenter Use; Cankaya (2026), Suppressing Side Channels in an Untrusted Data Center via Retrofitted Defenses (MIRI); Dean, Verification Plan (AI 2040); Proofworks, Living Verification Documents.
Sub-questions
None with a checkable form.
Sub-questions not yet stated precisely enough to check
| ID | Sub-question |
|---|---|
| P016.1 | How can a chain of assurances cover design, fabrication, packaging and deployment (chiplets, 3D stacking, new transistor architectures) when verification tools lag design complexity and hardware backdoors cannot be patched? |
| P016.2 | Who can produce mutually trusted / credibly neutral verification hardware, given the Prover may control the supply chain and a globally trusted processor supply chain is a large logistical task? |
| P016.3 | Can transceiver DSP supply chains be hardened, and on what timescale? |
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 P016.2: Who can produce mutually trusted / credibly neutral verification hardware, given the Prover may control the supply chain and a globally trusted processor supply chain is a large logistical task?
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