Restricted Data: The Nuclear Secrecy Blog

Meditations | Redactions

The Problem of Redaction

by Alex Wellerstein, published April 12th, 2013

Redaction is one of those practices we take for granted, but it is actually pretty strange if you think about it. I mean, who would imagine that the state would say, “well, all of this is totally safe for public consumption, except for a part right here, which is too awful to be legally visible, so I’ll just blot out that part. Maybe I’ll do it in black, maybe in white, maybe I’ll add DELETED in big bold letters, just so I know that you saw that I deleted it.”

From Hans Bethe’s “Memorandum on the History of the Thermonuclear Program” (1952), which features some really provocative DELETED stamps. A minimally-redacted version assembled from many differently redacted copies by Chuck Hansen is available here.

From a security perspective, it’s actually rather generous. The redactor is often giving us the context of the secret, the length of the material kept from us (a word? a sentence? a paragraph? a page?), and helpfully drawing our eye to the parts of the document that still contain juicy bits. The Onion’s spoof from a few years back, “CIA Realizes It’s Been Using Black Highlighters All These Years,” is only slightly off from the real truth. Blacking something out is only a step away from highlighting its importance, and the void makes us curious. In fact, learning what was actually in there can be quite anticlimactic, just as learning how a magician does their trick (“the guy in the audience is in on the trick”).

And, of course, the way the US declassification system is set up virtually guarantees that multiple, differently-redacted copies of documents will eventually exist. Carbon copies of the same documents exist in multiple agencies, and each agency can be separately petitioned for copies of their files, and they will send them to individual reviewers, and they will each review their guides and try and interpret them. There’s very little centralization, and lots of individual discretion in interpreting the guides.

The National Security Archive recently posted an Electronic Briefing Book that was very critical of this approach. In their case, they pointed out that a given paragraph in a once-secret document that was deemed by the redactor to be completely safe in 2001 was in 2003 deemed secret again, and then, in 2007, reaffirmed safe, and then, in 2012, again secret. “There often seems little logic to redaction decisions, which depend on the whim of the individual reviewer, with no appreciation of either the passage of time or the interests of history and accountability,” writes Michael Dobbs.

This sort of thing happens all the time, of course. In the National Security Archive’s Chuck Hansen papers there are bundles of little stapled “books” he would create of multiply, differently-redacted copies of the same document. They are a fun thing to browse through, viewing four different versions of the same page, each somewhat differently hacked up.

A page from a 1951 meeting transcript of the General Advisory Committee, from the Hansen files. Animated to show how he staples three different copies together. Some documents contain five or more separate versions of each page. For closer inspections of the page, click here.

In the case of Hansen’s papers, these differences came about because he was filing Freedom of Information Act requests (or looking at the results of other’s requests) over extended periods of time to different agencies. The passage of time is important, because guides change in the meantime (usually towards making things less secret; “reclassification” is tricky). And the multiple sites means you are getting completely different redactors looking at it, often with different priorities or expertise.

Two different redactors, working with the exact same guides, can come up with very different interpretations. This is arguably inherent to any kind of classifying system, not just one for security classifications. (Taxonomy is a vicious profession.) The guides that I have seen (all historical ones, of course) are basically lists of statements and classifications. Sometimes the statements are very precise and technical, referencing specific facts or numbers. Sometimes they are incredibly broad, referencing entire fields of study. And they can vary quite a bit — sometimes they are specific technical facts, sometimes they are broad programmatic facts, sometimes they are just information about meetings that have been held. There aren’t any items that, from a distance, resemble flies, but it’s not too far off from Borges’ mythical encyclopedia.

The statements try to be clear, but if you imagine applying them to a real-life document, you can see where lots of individual discretion would come into the picture. Is fact X implied by sentence Y? Is it derivable, if paired with sentence Z? And so on. And there’s a deeper problem, too: if two redactors identify the same fact as being classified, how much of the surrounding context do they also snip out with it? Even a stray preposition can give away information, like whether the classified word is singular or plural. What starts as an apparently straightforward exercise in cutting out secrets quickly becomes a strange deconstructionist enterprise.

One of my favorite examples of differently redacted documents came to me through two Freedom of Information Act requests to the same agency at about the same time. Basically, two different people (I presume) at the Department of Energy looked at this document from 1970, and this was the result:

In one, the top excerpt is deemed declassified and the bottom classified. In the other, the reverse. Put them together, and you have it all. (While I’m at it, I’ll also just add that a lot of classified technical data looks more or less like the above: completely opaque if you aren’t a specialist. That doesn’t mean it isn’t important to somebody, of course. It is one of the reasons I am resistant to any calls for “common sense” classification, because I think we are well beyond the “common” here.) In this case, the irony is double, because what they’re de/classifying are excerpts from classification guides… very meta, no?¹

What’s going on here? Did the redactors really interpret their guidelines in exactly the opposite ways? Or are both of these borderline cases where discretion was required? Or was it just an accident? Any of these could be plausible explanations, though I suspect they are each borderline cases and their juxtaposition is just a coincidence. I don’t actually see this as a symptom of dysfunction, though. I see it as a natural result of the kind of declassification system we have. It’s the function, not the dysfunction — it’s just that the function is set up to have these kinds of results.

The idea that you can slot all knowledge into neat little categories that perfectly overlap with our security concerns is already a problematic one, as Peter Galison has argued. Galison’s argument is that security classification systems assume that knowledge is “atomic,” which is to say, comes in discrete bundles that can be disconnected from other knowledge (read “atomic” like “atomic theory” and not “atomic bomb”). The study of knowledge (either from first principles or historically) shows exactly the opposite — knowledge is constituted by sending out lots of little tendrils to other bits of knowledge, and knowledge of the natural world is necessarily interconnected. If you know a little bit about one thing you often know a little bit about everything similar to it.

For this archive copy of a 1947 meeting of the General Advisory Committee, all of the raw numbers were cut out with X-Acto knives. Somewhere, one hopes, is an un-mutilated version. In some cases, numbers like these were initially omitted in drawing up the original documents, and a separate sheet of numbers would be kept in a safe, to be produced only when necessary.

This is a good philosophical point, one that arguably is a lot stronger for scientific facts than many others (the number of initiators, for example, is a lot less easily connected to other facts than is, say, the chemistry of plutonium), but I would just add that layered on top of this is the practical problem of trying to get multiple human beings to agree on the implementations of these classifications. That is, the classification are already problematic, and now you’re trying to get people to interpret them uniformly? Impossible… unless you opt for maximum conservatism and a minimum of discretion. Which isn’t what anybody is calling for.

In theory, you can read the classification history of a document from all of its messy stamps and scribblings. They aren’t just for show; they tell you what it’s been through, and how to regard it now.

Declassification can be arbitrary, or at least appear arbitrary to those of us locked outside of the process. (It is one of the symptoms of secrecy that the logic of the redactor is itself usually secret.) But to me, the real sin of our current system is the lack of resources put towards it, which makes the whole thing run slow and leads to huge backlogs. When the system is running at a swift pace, you can at least know what it is they’re holding back from you, compare it to other sources, file appeals, draw attention to it, and so on. When it takes years to start processing requests (as is the case with the National Archives, in my experience; it varies a lot by agency), much less actually declassify them, there is a real impediment to research and public knowledge. I’d rather declassification be arbitrary and fast than conservative and slow.

That individual redactors individually interpreting the guidelines according to the standards they are told to use come up with different results doesn’t bother me as much. There is going to be a certain amount of error in any large system, especially one that deals with borderline cases and allows individual discretion. Sometimes you win, sometimes you lose, but it’s being able to play the game in the first place that matters the most to me.

The document is a discussion of instances in which classification guidelines are based on strict numerical limits, as opposed to general concepts. Citation is: Murray L. Nash to Theos Thomson (3 November 1970), “AEC Classification Guidance Based on Numerical Limits,” part of SECY-625, Department of Energy Archives, RG 326, Collection 6 Secretariat, Box 7832, Folder 6, “O&M 7 Laser Classification Panel. The top was received as the response to a FOIA request I made in 2008, the bottom another one in 2010. Both were part of FOIA requests relating to declassification decisions relating to inertial confinement fusion; the memo in question was part of information given to a panel of scientists regarding creating new fusion classification guidelines. [↩]

Tags: 1940s, Atomic Energy Commission, Declassification, J. Robert Oppenheimer, Klaus Fuchs, Leslie Groves, Manhattan Project
Posted in Meditations, Redactions | This post has footnotes | 11 Comments »

Visions

The 36-Hour War: Life Magazine, 1945

by Alex Wellerstein, published April 5th, 2013

When NUKEMAP first got very hot, the Washington Post’s blog declared its popularity a sign of our jittery times. Those were Iranian jittery times, if we remember back all the way to a year ago — today we are jittery again, this time regarding North Korea. And so people are flocking to the NUKEMAP again, trying to see what North Korea’s latest weapons would do to their cities if they were used. I’m almost tempted to push out the new one early, just to take advantage of the interest, but I have faith that we will be jittery again whenever the new one is done. Nuclear jitters aren’t a new thing.

Visualizing nuclear war is an old media pastime. How old? One of the most vivid early depictions of this sort of atomic apocalyptic thinking come from Life magazine’s issue of November 19, 1945 — only a few months after Hiroshima and Nagasaki.

From the cover of the issue, you’d have little to suspect about its contents. “Ah, big belts! Fascinating! I love big belts!”

But once you get beyond that, the interior stories are much more interesting. For people interested in World War II and the Cold War, there are a lot of great stories in here: articles about what should be done with postwar China, what was going on in postwar Poland (with some impressive, awful photographs), plus an article on occupied Tokyo (with some amazing illustrations), and another on the OSS (spies!). There was even, at the very end, a reproduction of the Jack Aeby photo of the “Trinity” test, in full color (which was apparently just “orange,” after going through Life’s printing processes).

But the real stunner story of the issue was something much more grim. Once you get past a lot of fluffy stuff, you’re greeted with this horror:

“The 36-Hour War.” This long, feature story is a description of what nuclear war in the future will look like. It was based on a report by General “Hap” Arnold, the chief of the Army Air Forces during World War II and the later founder of Project RAND, which became the RAND Corporation, the epitome of a Cold War think tank. (He was also, incidentally, the guy who gave Curtis LeMay his job in the Pacific theatre.)

The report in question was the “Third Report of the Commanding General of the Army Air Forces to the Secretary of War.” Hunting around a bit, I eventually located a copy of the original online, if you’d like to look at it. It was published only a week before the Life story on it, which is pretty impressive given the illustrations involved in the article. The report is concerned both with summarizing what had happened in the air war during World War II on both the European and Pacific fronts, as well as a concluding section on “Air Power and the Future,” which is the subject of the “36-Hour War” article. Like many strategic bombing advocates, Arnold downplayed the importance of the bomb for World War II, emphasizing that the only reason the atomic bombs, or any bombs, could be delivered at will was because they had already won strategic superiority over the island. It’s the future where Arnold thought atomic weapons will really matter.

And it’s a grim future: rockets plus nuclear weapons equals “the ghastliest of all wars,” according to Life. The implications of ICBMs somewhat understood well over a decade before they were technologically realized.

The Life story starts with a large illustration of Washington, DC, getting nuked (hey, at least it’s not New York again, right? But why are they nuking RFK Stadium?), and then follows with a two-page spread showing 13 “key U.S. centers” getting wiped out by the Soviet Union. “Within a few seconds atomic bombs have exploded over New York, Chicago, San Francisco, Los Angeles, Philadelphia, Boulder Dam, New Orleans, Denver, Washington, Salt Lake City, Seattle, Kansas City, and Knoxville.” (Sorry, Boston, but you didn’t rate! Austin, you are fine for now!) They guess that 10 million people would be killed in the initial attack. “The enemy’s purpose is not to destroy industry, which is an objective only in the long old-fashioned wars like the last one, but to paralyze the U.S. by destroying its people.”

Amusingly, the Life writer suggests that these Soviet missiles came from silos in equatorial Africa, “secretly built in the jungle to escape detection by the UNO Security Council.” Ah, the naiveté of 1945, believing that it would be a taboo of some sort to build ICBM sites! Believing that some kind of international order would be assembled that might affect the conduct of nuclear war! Sigh.

But on the whole the Life story is not bad (except for the ending, which I’ll get to). On the page above, it talks about radar as an early warning technique which they claim would give perhaps 30 minutes warning in the event of an ICBM attack. But they also point out that radar can be evaded by low-altitude missiles and smuggled atomic bobs. And they recognize that 30 minutes is really not that long of a period in time — “even 30 minutes is too little time for men to control the weapons of atomic war.” At best, they suggest, such warning could be used to fire defensive rockets at the incoming rockets, a topic they cover on the next page.

“Our Defensive Machines Stop Few Attackers.” Dang. In this hypothetical future, the US has a missile defense system that works pretty much like you’d expect one to work today — maybe it might destroy a few of them, “but inevitably it would miss some of the time.” The illustration above shows the enemy rocket “coasting through space” in its final descent, with the interceptor missile coming up from the ground. Some nice copy: “When the two collide, the atomic explosion will appear to observers on the earth as a brilliant new star.” It doesn’t actually work that way, but whatever, it’s a nice sentence.

In his report, Arnold outlines three approaches to “defense” against atomic attack. First, you basically try to make sure nobody is making nuclear weapons. Not a bad start, you have to admit. Second, you should try and develop defenses against launched attacks — e.g. missile and bomber defense. A bit more problematic. Third, you redesign the entire country to make it harder to attack with nukes. This is basically the “dispersal” theory of defense — if you don’t have all of your infrastructure and people living in a few, centralized locations, then the vulnerability to all but the most apocalyptic attacks is a lot lower.

But finally, he emphasizes — in the manner befitting a general, I suppose — that the best defense is a good offense. That is, deterrence. And to do that, you need a good second-strike capability, to use the lingo of a later time.

The Life writer and illustrator decided to combine both of these last two ideas, creating a rather amazing fantasy nuclear installation. Take a look at that spread — it’s a huge underground city devoted to producing ICBMs and launching them en masse. It has underground streets and underground cars and underground trains. I’m not sure that Arnold was suggesting anything like this, but it’s pretty amazing. It doesn’t seem very practical, for a lot of reasons (those firing tubes look pretty vulnerable to attack, which would moot the whole installation), but it’s wonderfully imaginative for 1945. Philip K. Dick wrote about crazy installations like this in some of his short stories, but those were written in the 1950s and 1960s.

Towards the “war’s end,” enemy troops would show up. This is because, according to the Life writers, “in spite of the apocalyptic destruction caused by its atomic bombs, an enemy nation would have to invade the U.S. to win the war.” Win the war? Here you see a little bit of divergence from what would be a more common narrative: that nuclear war is really just about a “knock-out punch,” as opposed to conventional notions of taking over a country.

The illustration above is pretty interesting. OK, obvious cheesecake fantasy going on there, as gas-masked Soviet thugs step over the somehow-still-beautiful corpse of a telephone operator whose blouse has almost been knocked open by atomic bombs. The Soviet soldiers are attempting to repair the telephone infrastructure and get the country back up to (occupied) speed, and are walking around destroyed streets with bazookas (a less-sung wonder-weapon of WWII). The Life staff estimate that 40 million would be dead at this point “and all cities of more than 50,000 population have been leveled.” New York’s Fifth Avenue is merely a “lane through the debris.”

But, but! Have some hope! Improbably, “as it is destroyed, the U.S. is fighting back. The enemy airborne troops are wiped out. U.S. rockets lay waste the enemy’s cities. U.S. airborne troops successfully occupy his country. The U.S. wins the atomic war.” Wait, what? We won the war? How? A little hand-waving was all that was needed. I know, they nuked all our major cities and landed troops with bazookas, but don’t worry, we managed to (within 36-hours, mind you!) launch a devastating counterattack that included occupying his country. Well. I am relieved and can move on to the article on big belts, no?

Well, hooray. Of course, the country has been reduced to radioactive rubble — “By the marble lions of the New York Public Library, U.S. technicians test the rubble of the shattered city for radioactivity.” But chin up — we won the war!

It’s an amazing place for the article to just… end. A preview of un-defendable, horrible destruction, and then a quick deus ex machina that resolves it. And what a resolution! 40 million dead, no more big cities, but don’t worry, we got ’em back! It’s really not very satisfying. It has the whiff of a heavy, least-minute editorial hand: “we can’t end on such a grim note, and then expect them to just move on to other articles. We’ve gotta win, in the end! Give ’em some hope!”

One wonders: what was the public supposed to take away from this? Support for international control of the bomb? Support for better defenses? Fear of the future? It’s really a wonderful mess, the sort of thing you’d expect only a few months after the bomb made its debut, to be sure. Not all of the clichés had codified, the genre was still new.

Speaking of which — remember that devastating sequence from Fog of War, where Robert McNamara describes the firebombing of Japan, telling you what percentage of each Japanese city was destroyed, and then telling you an American-sized equivalent? The Arnold report in question did it first, and may have been the source for the data (the percentages and cities seem to match exactly):

Which makes a wonderful full-circle, doesn’t it? Something originally used to brag about performance has now become a touchstone for explaining the barbarity of the Pacific campaign.

Tags: 1940s, Bad ideas, Civil Defense, Graphic design, Hiroshima, Nagasaki, Soviet Union, Speculation, Trinity
Posted in Visions | 16 Comments »

Meditations

Narratives of Manhattan Project secrecy

by Alex Wellerstein, published March 29th, 2013

Secrecy suffused every aspect of the Manhattan Project; it was always in the background, as a context. But it’s also a topic in and of itself — people love to talk about the secrecy of the work, and they’ve loved to talk about it since the Project was made public. In the 1940s there was something of a small industry of articles, books, and clichés regarding how secret the atomic bomb was kept. Of course, the irony is… it wasn’t really kept all that well, if you consider “keeping the secret” to involve “not letting the Soviet Union know pretty much everything about the atomic bomb.” (Which was, according to General Groves, one of the goals.)

It’s easy to get sucked into the mystique of secrecy. One way I’ve found that is useful to help people think critically about secrecy (including myself) is to focus on the narratives of secrecy. That is, instead of talking about secrecy itself, look instead at how people talk about secrecy, how they frame it, how it plays a role in stories they tell about the Manhattan Project.

One of many early articles in the genre of Manhattan Project secrecy: “How We Kept the Atomic Bomb Secret,” from the Saturday Evening Post, November 1945.

My first example of this is the most obvious one, because it is the official one. We might call this one the narrative of the “best-kept secret,” because this is how the Army originally advertised it. Basically, the “best-kept secret” narrative is about how the Manhattan Project was sooo super-secret, that nobody found out about it, despite its ridiculous size and expense. The Army emphasized this very early on, and, in fact, Groves got into some trouble because there were so many stories about how great their secrecy was, revealing too much about the “sources and methods” of counterintelligence work.

The truth is, even without the knowledge of the spying (which they didn’t have in 1945), this narrative is somewhat false even on its own terms. There were leaks about the Manhattan Project (and atomic bombs and energy in general) printed in major press outlets in the United States and abroad. It was considered an “open secret” among Washington politicos and journalists that the Army was working on a new super-weapon that involved atomic energy just prior to its use. Now, it certainly could have been worse, but it’s not clear whether the Army (or the Office of Censorship) had much control over that.

Panel from FEYNMAN by Jim Ottaviani and Leland Myrick.

We might contrast that with the sort of narrative of secrecy that comes up with regards to many participants’ tales of being at places like Los Alamos. Richard Feynman’s narrative of secrecy is one of absurd secrecy — of ridiculous adherence to stupid rules. In Feynman’s narratives, secrecy is a form of idiotic bureaucracy, imposed by rigid, lesser minds. It’s the sort of thing that a trickster spirit like Feynman can’t resist teasing, whether he’s cracking safes, teasing guards about holes in the fence, or finding elaborate ways to irritate the local censor in his correspondence with his wife. All participants’ narratives are not necessarily absurd, but they are almost always about the totalitarian nature of secrecy. I don’t mean “fascist/communist” here — I mean the original sense of the word, which is to say, the Manhattan Project secrecy regime was one that infused every aspect of human life for those who lived under it. It was not simply a workplace procedure, because there was no real division between work and life at the Manhattan Project sites. (Even recreational sports were considered an essential part of the Oak Ridge secrecy regime, for example.)

So we might isolate two separate narratives here — “secrecy is ridiculous” and “secrecy is totalitarian” — with an understanding that no single narrative is necessarily exclusive of being combined with others.¹

“Beyond loyalty, the harsh requirements of security”: Time magazine’s stark coverage of the 1954 security hearing of J. Robert Oppenheimer.

But the Feynman approach looks perhaps unreasonably jolly when we contrast it to the narrative of J. Robert Oppenheimer and his students, for whom secrecy became something more sinister: an excuse to blacklist, a means of punishment. Oppenheimer did fine during the Manhattan Project, but the legacy of secrecy caught up with him in his 1954 security hearing, which effectively ended his government career. For his students and friends, the outcomes were often as bad if not worse. His brother, Frank, for example, found himself essentially blacklisted from all research, even from the opportunity to leave the country and start over. (It had a happy ending, of course, because without being blacklisted, he might never have founded the Exploratorium, but let’s just ignore that for a moment.)

For a lot of the scientists involved in the Manhattan Project, secrecy ended up putting their careers on the line, sometimes even their lives on the line. In response to (fairly ungrounded) suspicions about Oppenheimer’s student Rossi Lomanitz, for example, Groves actually removed his draft deferment and had him sent into the dangerous Pacific Theatre. This narrative of secrecy is what we might classically call the “tragic” narrative of secrecy — it involves a fall from grace. It emphasizes the rather sinister undertones and consequences of secrecy regimes, especially during the period of McCarthyism.

The original “best-kept secret” story, released on August 9, 1945 (the day of the Nagasaki bombing).

So what other narratives are there? Here is a short list, in no particular order, that I compiled for a talk I gave at a workshop some weeks ago. I don’t claim it to be exhaustive, or definitive. Arguably some of these are somewhat redundant, as well. But I found compiling it a useful way for me to think myself around these narratives, and how many there were:

“Secrecy is essential”: early accounts, “best-kept secret” stories
“Secrecy is totalitarian”: secret site participants’ accounts
“Secrecy is absurd”: e.g. Feynman’s safes and fences
- Common hybrid: “Secrecy is absurdly totalitarian”
“Secrecy is counterproductive”: arguments by Leo Szilard et al., that secrecy slowed them down (related to the “absurd” narrative)
“Secrecy is ineffective”: the post-Fuchs understanding — there were lots of spies
“Secrecy is undemocratic”: secrecy reduces democratic participation in important decisions, like the decision to use the bomb; fairly important to revisionist accounts
“Secrecy is tragic”: ruinous effects of McCarthyism and spy fears on the lives of many scientists
“Secrecy is corrupt”: late/post-Cold War, environmental and health concerns

It’s notable that almost all of these are negative narratives. I don’t think that’s just bias on my part — positive stories about secrecy fit into only a handful of genres, whereas there are so many different ways that secrecy is talked about as negative. Something to dwell on.

What does talking about these sorts of things get us? Being aware that there are multiple “stock” narratives helps us be more conscious about the narratives we talk about and tap into. You can’t really get out of talking through narratives if you have an interest in being readable, but you can be conscious about your deployment of them. For me, making sense of secrecy in an intellectual, analytical fashion requires being able to see when people are invoking one narrative or another. And it keeps us from falling into traps. The “absurd” narrative is fun, for example, but characterizing the Manhattan Project experience of secrecy makes too much light of the real consequences of it.

As an historian, what I’m really trying to do here is develop a new narrative of secrecy — that of the meta-narrative, One Narrative to Rule Them All, the narrative that tells the story of how the other narratives came about (a history of narratives, if you will). Part of talking about secrecy historically is looking at how narratives are created, how they are made plausible, how they circulate, and where they come from. Because these things don’t just appear out of “nowhere”: for each of these narratives, there is deep history, and often a specific, singular origin instance. (For some, it is pretty clear: Klaus Fuchs really makes the “ineffective” narrative spring to live; Leo Szilard and the Scientists’ Movement push very hard for the “counterproductive” narrative in late 1945; the “best-kept secret” approach was a deliberate public relations push by the government.)

As a citizen more broadly, though, being conscious about narratives is important for parsing out present day issues as well. How may of these narratives have been invoked by all sides in the discussions of WikiLeaks, for example? How do these narratives shape public perceptions of issues revolving around secrecy, and public trust? Realizing that there are distinct narratives of secrecy is only the first step.

Both of these might classically be considered “comic” narratives of secrecy, under a strict narratological definition. But I’m not really a huge fan of strict narratological definitions in this context — they are too broad. [↩]

Tags: 1940s, 1950s, Espionage, Historiography, J. Robert Oppenheimer, Klaus Fuchs, Leo Szilard, Leslie Groves, Los Alamos, Manhattan Project, Musings
Posted in Meditations | This post has footnotes | 18 Comments »

Visions

Hiroshima and Nagasaki in color

by Alex Wellerstein, published March 22nd, 2013

I’ve been on the road all this week, so there’s not too much of a post today! (The one last week was double-sized, though.) But I thought I’d share some interesting images that have captivated me over the last week or so.

Most of the photos we are familiar with of Hiroshima and Nagasaki are black and white. The effect is one of a dusty, barren landscape — they look like abandoned cities on the moon. On top of that, almost all photos of the cities from the ground were taken after the bodies had been cleaned up and the streets cleared — most were taken no earlier than late September 1945, and many of the “classic” ones are actually from mid-to-late 1946, a year or so later. The net effect is that the cities were somehow neatly “vaporized.” This is a false impression.

Color photographs of the city, however, are far more striking. What was a city of dust now looks like a city of rubble. It becomes, in some unconscious way, more believable, more recent, less distant. It becomes more “real.”¹

The effects of the bomb also become a bit more clear, though there is still a lot missing. The atomic bombs used during World War II killed most of its victims by burning and crushing them — the classic medieval tortures, made wholesale by technology but not much more modern. (Only about 15-20% of the people at the cities died truly “modern” deaths, from the radiation effects.)

The above photograph is of Hiroshima, apparently taken in March 1946 — some eight months after the bombing. You can tell a lot has been cleaned up: the roads, for example, are very clear. There are no obvious corpses. A few reinforced buildings are standing, but not much else is. There are some telephone or electricity poles up; I don’t know whether those were added after the attack, or were somehow still standing despite it (blast effects can be complicated).

The photo above is labeled as being of Hiroshima in the autumn of 1945. Superficially, when compared to the one before it, one thinks that the damage looks a lot lighter. There are a lot of poles and trees and a few shack-like structures in the foreground, and some factory-looking buildings in the background. But there’s still a lot of rubble — a lot of places that just aren’t there anymore. (I’m a little suspicious about whether this photo is identified correctly, to be honest.)

The above photograph was taken by the photographer J.R. Eyerman sometime in the fall of 1945. It’s a rare color view from the ground, as opposed to being from aircraft or from a high vantage point. It’s a vivid look at the twisted jungle of pipes, bricks, concrete, wood, trees, and other unidentified objects. Imagine the struggle of trying to make your way through that.

Another of Hiroshima from March 1946. Compare it to the one above, and how different a perception one has. It’s not that one of these is wrong, per se; they’re both of Hiroshima, and they both give away a different sense of the damage. In trying to get a sense of scale for these things, I find mixing up the modes of perception to be pretty important. One needs to understand what this looks like at the ground level, but then one needs to realize the extent to which that damage applied.

The above two are both of Nagasaki from around October 1945. Again, notice the almost capricious nature of this kind of damage: some of those trees look not so badly off, next to structures that have collapsed to the point of non-identification. The presence of people also lets you get a sense of the scale from the human point of view. A big ruinous mess.

This is listed as the damage outside a school in Nagasaki, taken just a few weeks after the bombs were dropped. Without knowing what this looked like before the attack, it’s hard to get a sense for what we’re looking at, but it appears the windows of the school are probably all blown in (there isn’t any glare or reflection), and those are some pretty big trees to see snapped about.

Hiroshima’s financial district, date unknown. Again, note the apparent capriciousness of the damage. The truth is, the construction of the buildings in question matters quite a bit. But don’t be too fooled — being inside a burning concrete building whose windows are blown in isn’t that great. You can tell the one in the middle has no remaining glass and some ominous-looking charring around the windows.

And here is one of the Hiroshima Gas Company and the Honkawa Elementary School. I think the latter really emphasizes the horror of “strategic” bombing, where burning elementary schools become acceptable as “collateral damage.” The famous dome at the upper right hand corner of the photo was directly underneath the explosion; the school was about 800 feet from there.

There are two ways you can go wrong in making sense of the scale of the bombings of Hiroshima and Nagasaki. The first is to see the bombs as instant vaporizers, to see the bombs as Everything Killers that just zap cities out of existence. This isn’t the case. They kill by crushing and burning and irradiating. They don’t turn you to dust. They don’t freeze you and turn you into a stop-motion skeleton, like in The Day After. For some, death was instantaneous, but for a lot of others, it was a much more protracted affair.

The other way to misunderstand it is to downplay it. Ah, a number of large buildings survived! It’s not so bad, then, right? Maybe the whole nuke thing has been exaggerated! Well, unless you are, you know, not in one of those buildings, and even if you are, it’s a pretty awful thing. Yes, you can approximate the city-wide effects of early atomic bombs with a fleet of conventional bombers dropping napalm — which personally I consider just as much a weapon of mass destruction as anything else, and yes, napalming cities is “conventional” in the sense that it is not a nuclear, biological, or chemical weapon, but let’s not forget that it’s not exactly an everyday occurrence. But being napalmed is not exactly a walk in the park for those being bombed, either.

So what’s the right view? An ugly, troublesome, disturbing one; right between those extremes. The atomic bomb was a weapon used to inflict tremendous human suffering. (This is true whether you think its use was justified or not.) If an atomic bomb were to go off over your city, the damage would be horrifying, the death toll staggering. But it’s a level of destruction that people should try to appreciate for what it is — a realistic possibility, not a clean science-fiction ending or a blow to be shrugged off.

That’s the perception I’m always searching for. The color photographs add a little bit to that, to keep one from the misconceptions, to keep one from seeing these wrecked cities as sanitary piles of dust.

These come from here and there on the Internet, but two very nice galleries I got a number of them from are here, here, and here. I’ve done some color correction on the photos, which understandably have faded a bit over time. [↩]

Tags: 1940s, Hiroshima, Manhattan Project, Nagasaki
Posted in Visions | This post has footnotes | 11 Comments »

Meditations | Redactions

Death of a patent clerk

by Alex Wellerstein, published March 15th, 2013

This post is a bit longer than most, but the story is a bit more involved than most. It’s got a little bit of everything — if by “everything” one means atomic patents and mysterious deaths.

Four of my favorite atomic patents — the nuclear reactor, the Calutron, the triggered spark gap, and the barometric fuse

Manhattan Project inventions: Patents 2,708,656, 2,709,222, 3,956,658, and 3,358,605.

During the Manhattan Project, one of the odder activities that was undertaken — approved directly by Roosevelt and Churchill — was to try and file secret patent applications for every single invention that was developed while trying to build the atomic bomb. I have written about this at length in various places and won’t repeat all of that here. Basically, the people working on the bomb project weren’t sure of what would happen after the war, and so were trying to make sure they had iron-clad legal control over the bomb, and the secret patent applications were a way to guarantee government control of nuclear technology with regards to private contractors, private scientists, and universities.

The person who was in charge of all of this work was Captain Robert A. Lavender, USN (Ret.). Lavender was the chief patent officer of the Office for Scientific Research and Development (OSRD), which headed up the civilian functions of the bomb project. Lavender was basically a Navy lawyer who knew intellectual property law inside and out. His job, basically, was to make sure that all of those secret patent applications were properly filed. He knew his stuff and he got it done. By the time the Atomic Energy Commission took over the job, Lavender’s office had docketed reports on over 5,600 different inventions relating to the atomic bomb, with some 2,100 separate patent applications ready to be filed — in secret.

Now, one of the ironies of the Manhattan Project patent program is that it pretty much operated in an opposite way than the rest of the bomb work. The bomb program was defined by its secrecy. You didn’t use the names of real things, you used code-names (“oralloy,” “copper,” “the Gadget”). You didn’t centralize information, you compartmentalized it. You worried about what you needed now, not what you needed in the future. And the patent program was the opposite: you used the real names, with centralized information, because it was about protecting the bomb — legally — for the indefinite future. So from a certain standpoint, the Manhattan Project patent division housed more technical secrets in one place than any other part of the bomb program.

Invention by Oppenheimer, patent by Lavender.

Lavender didn’t do this alone, of course. He had a staff, and each Project site had dozens of lawyers attending technical meetings, looking for inventions, forcing the poor, harried scientists to fill out invention reports. It’s a really amusing idea if you think about it, juxtaposing that familiar narrative of the racing Los Alamos scientists with the dull banality of the legal aspects of patent applications. The local patent officer at Los Alamos, for example, recommended that they allow a “competent disinterested individual” attend the “Trinity” test so they could write a report that would testify to the “reduction to practice” of the first atomic bomb. Talk about the least interesting reason to be at “Trinity” on July 16, 1945.

The second in command at Lavender’s office was Captain Paul P. Stoutenburgh. Stoutenburgh was born in Norwalk, Ohio, on September 25, 1901. He received B.A. from Johns Hopkins in 1923, was married in 1926, and received a law degree from George Washington University in 1928. Stoutenburgh was had worked as an attorney for the Justice Department, in the claims division, and had joined the Army only in July 1945. He was discharged from the Army in February 1946 as a Lieutenant Colonel, and he thereafter resigned from the Justice Department and returned to work for the Office for Scientific Research and Development as a civilian.

When I was researching the atomic patent program, I came across Stoutenburgh’s name occasionally, but it didn’t stand out. His memos to Lavender or others weren’t anything unusual or special — just a guy doing his job. Sometimes he wrote things in Lavender’s name, the way that subordinates often do. I wasn’t drawn to him in any particular way.

But as part of my research into Lavender, I started running his name through various newspaper archives, looking for obituaries, articles, later jobs, and so on. And when I did, suddenly Stoutenburgh showed up, in a horrific way:

On the morning of Saturday April 1, 1946, a friend of Stoutenburgh’s daughter, became alarmed when she did not show up for a roller skating date and no one would answer the phone at the Stoutenburgh residence. They contacted Mrs. Stoutenberg’s brother, and another friend, and together they went to Stoutenberg’s Northwest Washington, DC, home. Finding the Stoutenberg car in the garage, they assumed the worst, and contacted the Sixth Precinct police. Three officers arrived and broke into the house through a back window.

Inside was a scene of horror. Paul Stoutenburgh was wearing his pajamas and a smoking jacket, and was sprawled across his daughter’s bed on his back, with his feet on the floor. Near his hand was a .25-caliber pistol. In his right temple, a bullet wound. He was 44.

His wife, Anna, was face-down, near the door in the same room. She wore a black housecoat. She had a bullet wound in the back of her head, exiting through the skull. She was also 44.

His daughter, Mary Alice, was found unconscious, breathing heavily on the other side of the bed, in her pajamas. She had a bullet wound in her right temple. She was taken to Walter Reed Hospital, without much of hope of survival. She died a week later, without reviving. She was 12.

What happened? According to Stoutenburgh’s former Justice Department colleagues, he had visited them the week before and told them that he’d be returning to the claims division soon. According to Stoutenburgh’s neighbors, he had developed a “‘phobia’ over atomic bomb secrets, which he believed were leaking out despite his repeated recommendations to the War and Navy Departments,” as the Washington Post put it at the time. “Atomic sescrets worried him,” they wrote under his photo — mangling the epitaph.

The War Department, for their part, told the press that “Stoutenburgh had nothing to do with the development of the atomic bomb itself,” and left it at that. Well, yes and no, as we’ve seen. He didn’t build the bomb, but he did help patent it — every part of it.

The newspaper stories implied that Stoutenburgh succumbed to paranoia: he imagined secrets were getting out, and couldn’t take it anymore. The coroner ruled it “homicide-suicide.” The phenomena of male familial murder-suicide is not a new one. These things happen with disturbing frequency. Apparently Stoutenburgh had tried to commit suicide a month previous, and failed.

He was a troubled man in a troubling time. The spring of 1946 was the period of the first real atomic spy scare — the Gouzenko affair. In terms of actual data given away, it was a minor thing; it involved a Canadian spy ring, and General Groves had compartmentalized the Canadians out of pretty much everything he cared about.¹ It was nothing like a Klaus Fuchs situation.

But in the spring of 1946 it was a big deal, both because it was the first such spy scare, and because Groves leaked the news about the espionage to the press that February. Why? Because he wanted Congress to be scared of the Russians, so they would add scarier secrecy provisions to the draft version of the Atomic Energy Act they were considering. And it worked — the changes to the law made in the spring of 1946 are responsible for the problematic “Restricted Data” clause and all of its issues.

Given the context, it’s not surprising that Stoutenburgh’s death briefly made the front pages of several national newspapers. Each played up the “secrets” angle, though the stories themselves make it clear that they are about a man driven mad by fear of secrets getting out, not actual cases of secrets getting out. Therein is the question: Did secrets kill the Stoutenburgh family, or did “secrets” kill them? Was it the thing itself, or just a fear about the thing itself? Or neither?

It doesn’t strike me implausible as that someone who was on the periphery of real policy, but with an acquaintance with secrets, might, in the spring of 1946, get concerned with the loss of secrets, especially if one implies some sort of latent mental illness. But I’m an historian, not a psychologist, so I am not really treading into those waters. Still, I’ve tried to follow this up a bit, and the trail wasn’t very rich for the most part. Stoutenburgh once had an FBI file, but it doesn’t exist anymore.

Specifically, the FBI told me that:

Records which may be responsive to your Freedom of Information-Privacy Acts (FOIPA) request were destroyed on October 1, 2001. Since this material could not be reviewed, it is not known if it actually pertains to your subject.

Now this sounds Kafkaesque, if not a wee bit conspiratorial, but I’ve been assured this is pretty standard boilerplate for a pretty common issue. Somewhere in the FBI’s record database it basically says, “we had a file with this guy’s name on it, but we destroyed it.” Ergo, they don’t really know what was in it anymore. Not so helpful.²

The Washington, DC, Police Department destroyed the records awhile back because of age. The DC Coroner’s Office, likewise. The case had been closed, ruled murder-suicide, so there was no need to keep the files. Army Intelligence had nothing on Stoutenburgh, a FOIA to the National Archives turned up nothing.

But I did find a few little other tidbits in the archives. Because it wasn’t just present-day people who worried about conspiracies — there were Stoutenburgh conspiracy theories back in the day, they just didn’t end up in the newspapers.

The first little nibble comes from the papers of James Burnham. Burnham’s work is pretty well-known — in a nutshell, he was a former Marxist who became an anti-Communist neo-conservative political pundit during the Cold War. You know the type. He wrote a lot, and wrote for the National Review, among other publications. Apparently he also collected rumors about dead patent clerks.

On a memo from December 1951, now in his papers at the Hoover Institution Archives, Burnham wrote that he had been called by someone he listed only as “BL.” I’ve no clue who it is meant to correspond to, but presumably it is someone who worked with Burnham regularly. Here’s what Burnham wrote:

L stated that a fantastic and sensational story had been brought to him. He felt it essential to try to check any point we could, in order to see whether it has a presumption of truth. Involved is a man named L.t Col. STOUTENBURGH. It is stated that on 31 March 1946 STOUTENBURGH was found shot dead by a bullet in his home in Washington, D.C. His wife and daughter were also shot, presumably also dead. Apparently they were murdered, although the facts were never established. STOUTENBURGH is said to have had a secret job in connection with the atomic bomb, perhaps in something involving British-Canadian-United States liaison.

Apparently a certain E.M. Lee, living in Silver Spring, Maryland, worked with Stoutenburgh at some point. Burnham was told by “BL” that he should call Lee and tell him he was a friend of Bill Offenhauser, of Telenews in New York, and get more information. A few weeks later, Burnham called Edward M. Lee, whose number he got from a telephone directory. He spoke to Lee, who confirmed he was a friend of Offenhauser. Burnham wrote of it:

I then brought up the STOUTENBURGH case. For a minute or two, LEE shied away from the matter, and said nothing to indicate that he knew what I was talking about. Then, he stated that he had not been personally acquainted with STOUTENBURGH but had had certain relations with him. He said that STOUTENBURGH was working in the Patent Office of the ATOMIC ENERGY COMMISSION (he then corrected himself and said that at that time it was called the Manhattan Project). He (LEE) had been transferred to the Navy, and had certain “business” with STOUTENBURGH, which was transacted by telephone. He said that half a dozen or more times he had telephoned STOUTENBURGH at the latter’s office. He stated that he knew nothing further about him, and nothing about the deaths except of what he had read in the papers. (It was my impression that LEE probably knows a good deal more about STOUTENBURGH that he indicated in his telephone conversation, and that he has thought a good deal about the case.)

Burnham’s other research involved pulling up the various newspaper articles about the Stoutenburgh case. But there the trail ends. It doesn’t add up to a whole lot — even the initial lead was just a suspicion, not anything hard.

The other piece was a memo I found in the archives of the Congressional Joint Committee on Atomic Energy. In late August 1953, a certain Calvin Bertolotte of New York City got in touch with a Congressman, desiring to talk with someone about “a theory had had which might explain the operations of the Soviet espionage in connection with the atomic program.” He was put in touch with the staff of the Joint Committee, who liked to investigate this sort of thing. Bertolotte was “an employee of the Telefact Foundation engaged in research in information control and world strategy.” He told the Committee staff that he had been a friend or colleague of Sidney Young White, a physicist in New York City.

According to Bertolotte, White had related to him “on several occasions” the story of Stoutenburgh’s death. As the staff noted in their later write-up of their interview, “Bertolotte implied that both he and White imputed espionage significance to the story.”

Basically, Bertolotte and White’s objections to the official story were as follows, with my thoughts in parentheses:

Stoutenburgh actually did important secret work at the patent office and “had access to vital information.” (True)
White claimed to have determined that Stoutenburgh only had a .45-calibre weapon, not the .25-calibre one that he was reported to have used. (How would White have known what guns Stoutenburgh could have owned?)
White knew Stoutenburgh was a poor shot, so how had he hit his wife and child when at least the former was fleeing? (I don’t think you have to be that good a shot at that close a range.)
White “determined” (doesn’t say how) that Stoutenburgh had mentioned “either to his brother or his brother-in-law” that papers had gone missing from his desk for short periods of time, and would then be returned. (Vaguely sourced.)

Bertolotte thought the FBI ought to get involved, but didn’t want to betray White’s trust, so he gave it to the Joint Committee staff instead. (Um.) The Joint Committee staff asked whether they could relay the information to the FBI for him; Bertolotte asked to check with White first, then later got in touch and said he preferred they not give it to the FBI. The Committee staff member writing this up said that “unless advised to the contrary,” he was going to send all of this to the FBI anyway “despite Bertolotte’s objection.” I have no record as to whether he did this or not.

Where does that leave us? At a minimum, I think, we can agree with the general notion that secrecy engenders this kind of speculation. Monsters manifest within a vacuum of information, and at its peripheries. If this didn’t have any connection to “secrets,” would it stand out above the many other similar tragedies that happen each year? Obviously I wouldn’t be sending out Freedom of Information Act requests left and right if he didn’t have an atomic connection, either.

On the other hand, the fact that someone who had been so close to various secrets died under mysterious circumstances, and seems to have left no trace of any kind of official investigation, is suspicious. If you even sneezed near Los Alamos during World War II, the Manhattan Project security people would have opened a file on you. Why wasn’t there more poking around? (As for me, I poke around in these things compulsively — it’s sort of my job. I am always happy to check into unusual or unlikely stories, though I always try to do so with a skeptical mindset.)

Maybe there was, and it turned up nothing interesting, hence the destruction of the records. But I’ve got to say, the FBI sure kept around records of a lot of less-interesting cases than this one. And we do know that secrets were leaking out of the Manhattan Project during this time, after all. Stoutenburgh might not have known anything “solid” about that, but the fact that there was quite a lot of Soviet spying going on does perhaps raise our estimations of his suspicions.

On the other hand, the idea that, say, the KGB would have killed Stoutenburgh and his family just seems unlikely. Really not their style. In general, killing someone and their whole family is not the quietest way to make accusations of spying go away. Of course, it might still be murder, but if it was, I wouldn’t really suspect the Soviets. If this were a James Ellroy novel, there’d be a murderer, but it wouldn’t really be about the atomic secrets — that would just be the hook that brings the ambitious young detective onto the case in the first place, an opening into a far seedier story. But this isn’t a James Ellroy novel. It’s real life, where banal answers are usually the correct ones.

My eventual conclusion, is that this just another sad story in a world of sad stories. It’s a story, at most, that is about the conspiracy fears that cluster around “secrets” — and the conspiracy fears that follow those conspiracy fears around, decades into the future. In this case, one almost hopes there was something more sinister to it, because it would keep it from seeming so pointlessly tragic. But pointlessly tragic is probably just what it was.

Groves let a number of French and Canadian scientists work on a reactor and plutonium separation in Montreal, but it was a strictly one-way information flow. They did good work there, but they didn’t benefit from the support of the rest of the Allied effort. [↩]
Of course, the mere mention of the year 2001 is going to set off further conspiracy blinkers, but it’s hard to see any connection there. [↩]

Tags: 1940s, 1950s, Espionage, FBI, FOIA, Joint Committee on Atomic Energy, Leslie Groves, Manhattan Project, Speculation
Posted in Meditations, Redactions | This post has footnotes | 7 Comments »

Restricted Data

The Problem of Redaction

The 36-Hour War: Life Magazine, 1945

Narratives of Manhattan Project secrecy

Hiroshima and Nagasaki in color

Death of a patent clerk

Search

Pages

Projects

Recent posts

Post categories ►

Post tags ►

E-mail subscription

Recent posts from DOOMSDAY MACHINES