Open in TheBrain

2013 Keith_A Case for Climate Engineering

Briefing Document: A Case for Climate Engineering by David Keith

Overview

"A Case for Climate Engineering" by David Keith (2013) presents a detailed argument for the consideration and potential implementation of solar geoengineering, specifically stratospheric aerosol injection, as a tool to manage climate risk. Keith, an "oddball environmentalist" and "tinkerer and technophile," approaches the topic from a background in physics and a long-standing interest in climate and energy. He advocates for a nuanced discussion of geoengineering, separating it from carbon removal technologies due to their distinct scientific, technological, cost, and risk profiles. The book explores the technical feasibility, potential benefits, risks, economic implications, and ethical/political challenges associated with deploying solar geoengineering. Keith emphasizes that while geoengineering is not a perfect solution and should not replace emission cuts, it offers a "plausible scenario for managing the human and ecological risks of climate change in a world without politics."

Main Themes and Key Ideas

1. Technical Feasibility and Low Cost of Solar Geoengineering

2. Climate Risk and Inevitable Warming

3. Benefits and Limitations of Solar Geoengineering

4. Risks and Unintended Consequences

5. Ethical, Political, and Social Considerations

Conclusion

Keith concludes that solar geoengineering, while a "joyless choice between unpleasant alternatives," represents a powerful new capacity for humanity. He urges serious research into the technology now to be prepared for "unpleasant surprises in the greenhouse." Despite the significant risks and complex political challenges, he maintains that the technical ease and low cost of stratospheric aerosol injection make it a tool that deserves serious consideration as part of a broader climate risk management strategy, not as a substitute for emissions reductions, but as a potential means to reduce the severity of climate impacts.

NotebookLM can be inaccurate; please double check its responses.