Approach | What government would actually do | Main benefit | Main drawback / risk | Practicality |
Apply existing laws | Use consumer protection, fraud, discrimination, privacy, securities, product-liability, employment and criminal laws when AI causes ordinary legally cognizable harms | Immediate and technology-neutral. Doesn't require government to predict which AI capabilities will matter | Existing laws may not fit novel harms; enforcement is often after the damage occurs | Very high |
Mandatory disclosure, transparency | Require companies to disclose model capabilities, limitations, training-data summaries, evaluations, ownership, incidents, etc. | Gives customers, regulators and researchers information without directly controlling development | Disclosure can become expensive paperwork; sensitive information can reveal IP or security vulnerabilities; disclosures don't necessarily make systems safer | Very high |
Independent testing, audits | Require frontier or high-risk systems to undergo standardized safety, cybersecurity, bias, privacy or performance testing before deployment | Creates an external check on company self-assessment; potentially catches problems before deployment | Hard to define meaningful tests for rapidly changing models; auditors can become a new bureaucracy; "passing" a benchmark may create false confidence | High |
Risk-management standards | Require companies to maintain documented processes for identifying, measuring and mitigating AI risks—similar to financial, aviation or cybersecurity risk management | Regulates process rather than a particular technology; adaptable as AI changes | Companies can satisfy procedures without actually reducing risk; standards can become box-checking exercises | Very high |
Incident reporting | Require developers/deployers to report serious AI failures, security breaches, dangerous behavior or loss of control to regulators | Creates a feedback system for regulators and researchers; particularly useful when risks are initially poorly understood | Companies may under-report; determining what constitutes a "serious" incident is difficult; reporting could expose security-sensitive information | High |
Liability, duty of care | Make developers or deployers financially responsible when AI causes foreseeable harm, potentially through negligence, product liability or a specific AI duty of care | Uses economic incentives rather than prescriptive technical rules; encourages companies to internalize externalities | Liability can discourage experimentation; causation can be extremely difficult when many parties contribute to an AI system | High, especially sector-by-sector |
Sector-specific regulation | Give FDA, FAA, financial regulators, healthcare regulators, employment regulators, etc. authority over AI used in their domains | Probably the most natural approach because the risk of an AI system depends heavily on what it does | Creates multiple regulatory regimes; can slow adoption and produce inconsistent requirements | Very high |
Prohibit particular applications | Ban specified uses—e.g., certain forms of biometric surveillance, manipulation, autonomous weapons, discriminatory decision-making or fraud | Very clear red lines; prevents particularly unacceptable uses regardless of technical sophistication | Defining the prohibited category is difficult; legitimate and harmful uses can look technically similar; enforcement can be evaded | High for narrow uses |
High-risk classification | Create categories such as "high-risk AI" and impose enhanced testing, documentation, human oversight and monitoring on them | Focuses regulation where potential harm is greatest rather than regulating every chatbot | Classification disputes; innovation may migrate around regulatory boundaries | High |
Frontier-model requirements | Impose additional obligations on the largest/most capable models—risk evaluations, cybersecurity, incident reporting, red-team testing, safety plans, etc. | Concentrates regulation on the relatively small number of firms developing frontier systems | Capability thresholds quickly become obsolete; could protect incumbents by making it harder for startups to compete | Medium-high |
Government licensing / pre-approval | Require a company to obtain government permission before training or releasing models above a specified capability/compute threshold | Gives government the strongest ability to stop genuinely dangerous systems before deployment | Extremely intrusive; government must determine what constitutes dangerous capability; potentially slows beneficial innovation and entrenches existing firms | Low-medium |
Regulate compute | Require reporting/licensing for very large AI-training runs or data centers; track high-end chips and compute clusters | Targets the physical bottleneck underlying frontier AI rather than trying to regulate every model | Compute becomes cheaper/more distributed; companies can optimize algorithms or move overseas; difficult to distinguish benign from dangerous compute | Medium |
Chip/export controls | Restrict advanced AI chips, semiconductor equipment or model weights from particular countries/entities | Useful when the objective is national security, because chips are tangible and controllable | Doesn't directly address domestic AI harms; encourages substitution, stockpiling and indigenous foreign capacity | High for national-security objectives |
Competition, antitrust policy | Challenge acquisitions, exclusive cloud/model/chip arrangements, discriminatory access, tying and potentially vertical integration | Addresses the possibility that AI becomes concentrated among a handful of firms and preserves competitive access to compute/models | Antitrust remedies are slow; breaking up or restricting efficient integration could reduce economies of scale | High |
Interoperability, portability | Require APIs, data portability, model portability or interoperability between AI services | Reduces switching costs and makes it easier for startups to compete | Standardization can freeze technology prematurely and potentially reduce security | Medium |
Copyright, training-data rules | Require licensing, compensation, opt-outs, attribution or disclosure concerning copyrighted training material | Protects creators and establishes property rights around a major AI input | Could substantially increase model costs; licensing billions of works is technically difficult; may advantage firms with large legal budgets | Medium |
Privacy, data regulation | Restrict collection and use of personal data for training and inference; require consent, minimization and deletion | Addresses a concrete existing harm without regulating AI as such | Reduces useful training data; enforcement and cross-border data issues are difficult | High |
AI-generated-content labeling | Require disclosure/watermarking of synthetic images, video, audio or text | Helps people distinguish synthetic from human-created material and can improve provenance | Watermarks can be removed; detection becomes harder as models improve; doesn't solve persuasion/misinformation itself | Medium-high |
Government procurement rules | Government agencies purchase only AI satisfying specified security, transparency, privacy or performance requirements | Government can use its enormous purchasing power without regulating the entire private economy | Primarily affects government suppliers; procurement standards can become politicized or overly restrictive | Very high |
Taxes, fees on AI or compute | Tax AI usage, high-end compute, AI profits or automation; use revenue for worker transition, social insurance, etc. | Addresses distributional effects while allowing firms to continue innovating | Difficult to identify the tax base; could discourage productive investment and push activity offshore | Medium |
Worker-transition policies | Expand unemployment insurance, retraining, wage insurance, portable benefits or education rather than restricting AI | Deals with the consequences of AI rather than trying to stop AI; preserves productivity benefits | Expensive; difficult to target assistance toward genuinely displaced workers | Very high |
International agreements | Establish common standards for dangerous capabilities, testing, incident reporting, chip controls and military uses | Reduces regulatory arbitrage and makes some global risks manageable | Extremely difficult because countries have different economic and national-security interests | Low-medium, but potentially important |