Back
The Long, Contentious Battle to Regulate Gain-of-Function Work
webRelevant background for AI safety researchers studying dual-use research governance, as analogous regulatory challenges around dangerous capabilities research may inform how AI development oversight frameworks are designed and enforced.
Metadata
Importance: 52/100news articleanalysis
Summary
This article traces the decades-long regulatory struggle over gain-of-function (GOF) research, examining how scientists, policymakers, and biosecurity experts have clashed over defining, overseeing, and limiting experiments that enhance pathogen transmissibility or lethality. It highlights the persistent gaps in federal oversight and the difficulty of establishing enforceable international norms for dual-use biological research.
Key Points
- •Gain-of-function research remains poorly defined in regulatory frameworks, making consistent oversight difficult and allowing potentially dangerous work to proceed under ambiguous classifications.
- •U.S. federal policy has oscillated between moratoria and resumed funding, reflecting deep disagreement among scientists and officials about acceptable risk thresholds.
- •International coordination on GOF regulation is largely absent, raising concerns that restrictions in one country may simply shift risky research elsewhere.
- •The debate intersects biosecurity, scientific freedom, and pandemic preparedness, making consensus extremely difficult to reach among stakeholders.
- •High-profile controversies, including debates around COVID-19 origins, have intensified public and political scrutiny of GOF oversight failures.
Cited by 1 page
| Page | Type | Quality |
|---|---|---|
| Bioweapons Risk | Risk | 91.0 |
Cached Content Preview
HTTP 200Fetched Apr 9, 202637 KB
The Long, Contentious Battle to Regulate Gain-of-Function Work
Close
Comments are automatically closed one year after article publication. Archived comments are below.
eddie
December 11, 2024 at 6:38 pm
Do you think that Lyme Disease came out of gain-of-function research at Plum Island?
Close
Republish
The Latest
Opinion: Scientific Journals Need Fact-Checkers
The Push for Artificial Inheritance
DNA Archive to Identify Missing Migrants Vanishes
How Much Are Rocket Launches Polluting the Skies?
Inside the U.S. Effort to Sequence Measles Genomes
Opinion: Prediction Markets’ Risk to Public Health
Why Swedish Schools Are Bringing Back Books
Nuclear Safety Protections in Federal Crosshairs
0%
25%
50%
75%
100%
Share
Comment
Share this Story
Share on Facebook (Opens in new window)
Facebook
Share on X (Opens in new window)
X
Share on Reddit (Opens in new window)
Reddit
Share on FlipBoard (Opens in new window)
FlipBoard
Copy
I n early 2012, federal officials summoned Michael Imperiale from his home in Ann Arbor, Michigan, to a large conference room in Bethesda, Maryland. There, they handed the virologist drafts of two scientific papers. A foreign government had deemed one draft’s contents so risky that it could not be sent via the postal service or attached to an email.
UNLEASHED
Living in the Age of Risky Science: An Undark Special Series.
The drafts detailed attempts to alter a lethal avian influenza virus, potentially granting it the ability to spread among humans. Such work, according to the U.S. officials who had funded it, was vital for preparing for a potential flu pandemic. But some scientists wondered whether the research itself could spark a cataclysm. Might someone read the papers, which contained details of how the pathogens had been engineered, and use them as blueprints for bioterrorism?
Months before, Imperiale and more than a dozen colleagues had recommended that earlier drafts of the papers be published with some details redacted. But that halfway option wasn’t going to fly. Now they needed to make a choice: Was it worthwhile to publish the papers in full? Or should the manuscripts, with their potential for misuse, not be published at all?
The meeting helped launch a new era of debate over pathogen research. In the ensuing years, the field would be forced to
... (truncated, 37 KB total)Resource ID:
f132e9a4c94af7d3 | Stable ID: M2IwYzYxZG