MétaCan
Menu
Back to cohort
Record W2191268435 · doi:10.5204/mcj.1029

What If? Re-imagined Scenarios and the Re-Virtualisation of History

2016· article· en· W2191268435 on OpenAlex
Meg Stalcup

Why this work is in the frame

A frame that forgets how it found something cannot be audited. These are the routes that admitted this work.

affAt least one author lists a Canadian institution in the pinned OpenAlex snapshot.

Bibliographic record

VenueM/C Journal · 2016
Typearticle
Languageen
FieldPsychology
TopicMemory, Trauma, and Commemoration
Canadian institutionsUniversity of Ottawa
Fundersnot available
KeywordsVirtualizationComputer scienceHistoryCloud computingOperating system

Abstract

fetched live from OpenAlex

Image 1: “Oklahoma State Highway Re-imagined.” CC BY-SA 4.0 2015 by author, using Wikimedia image by Ks0stm (CC BY-SA 3 2013). Introduction This article is divided in three major parts. First a scenario, second its context, and third, an analysis. The text draws on ethnographic research on security practices in the United States among police and parts of the intelligence community from 2006 through to the beginning of 2014. Real names are used when the material is drawn from archival sources, while individuals who were interviewed during fieldwork are referred to by their position rank or title. For matters of fact not otherwise referenced, see the sources compiled on “The Complete 911 Timeline” at History Commons. First, a scenario. Oklahoma, 2001 It is 1 April 2001, in far western Oklahoma, warm beneath the late afternoon sun. Highway Patrol Trooper C.L. Parkins is about 80 kilometres from the border of Texas, watching trucks and cars speed along Interstate 40. The speed limit is around 110 kilometres per hour, and just then, his radar clocks a blue Toyota Corolla going 135 kph. The driver is not wearing a seatbelt. Trooper Parkins swung in behind the vehicle, and after a while signalled that the car should pull over. The driver was dark-haired and short; in Parkins’s memory, he spoke English without any problem. He asked the man to come sit in the patrol car while he did a series of routine checks—to see if the vehicle was stolen, if there were warrants out for his arrest, if his license was valid. Parkins said, “I visited with him a little bit but I just barely remember even having him in my car. You stop so many people that if […] you don't arrest them or anything […] you don't remember too much after a couple months” (Clay and Ellis). Nawaf Al Hazmi had a valid California driver’s license, with an address in San Diego, and the car’s registration had been legally transferred to him by his former roommate. Parkins’s inquiries to the National Crime Information Center returned no warnings, nor did anything seem odd in their interaction. So the officer wrote Al Hazmi two tickets totalling $138, one for speeding and one for failure to use a seat belt, and told him to be on his way. Al Hazmi, for his part, was crossing the country to a new apartment in a Virginia suburb of Washington, DC, and upon arrival he mailed the payment for his tickets to the county court clerk in Oklahoma. Over the next five months, he lived several places on the East Coast: going to the gym, making routine purchases, and taking a few trips that included Las Vegas and Florida. He had a couple more encounters with local law enforcement and these too were unremarkable. On 1 May 2001 he was mugged, and promptly notified the police, who documented the incident with his name and local address (Federal Bureau of Investigation, 139). At the end of June, having moved to New Jersey, he was involved in a minor traffic accident on the George Washington Bridge, and officers again recorded his real name and details of the incident. In July, Khalid Al Mihdhar, the previous owner of the car, returned from abroad, and joined Al Hazmi in New Jersey. The two were boyhood friends, and they went together to a library several times to look up travel information, and then, with Al Hazmi’s younger brother Selem, to book their final flight. On 11 September, the three boarded American Airlines flight 77 as part of the Al Qaeda team that flew the mid-sized jet into the west façade of the Pentagon. They died along with the piloting hijacker, all the passengers, and 125 people on the ground. Theirs was one of four airplanes hijacked that day, one of which was crashed by passengers, the others into significant sites of American power, by men who had been living for varying lengths of time all but unnoticed in the United States. No one thought that Trooper Parkins, or the other officers with whom the 9/11 hijackers crossed paths, should have acted differently. The Commissioner of the Oklahoma Department of Public Safety himself commented that the trooper “did the right thing” at that April traffic stop. And yet, interviewed by a local newspaper in January of 2002, Parkins mused to the reporter “it's difficult sometimes to think back and go: 'What if you had known something else?'" (Clay and Ellis). Missed Opportunities Image 2: “Hijackers Timeline (Redacted).” CC BY-SA 4.0 2015 by author, using the Federal Bureau of Investigation (FBI)’s “Working Draft Chronology of Events for Hijackers and Associates”. In fact, several of the men who would become the 9/11 hijackers were stopped for minor traffic violations. Mohamed Atta, usually pointed to as the ringleader, was given a citation in Florida that spring of 2001 for driving without a license. When he missed his court date, a bench warrant was issued (Wall Street Journal). Perhaps the warrant was not flagged properly, however, since nothing happened when he was pulled over again, for speeding. In the government inquiries that followed attack, and in the press, these brushes with the law were “missed opportunities” to thwart the 9/11 plot (Kean and Hamilton, Report 353). Among a certain set of career law enforcement personnel, particularly those active in management and police associations, these missed opportunities were fraught with a sense of personal failure. Yet, in short order, they were to become a source of professional revelation. The scenarios—Trooper Parkins and Al Hazmi, other encounters in other states, the general fact that there had been chance meetings between police officers and the hijackers—were re-imagined in the aftermath of 9/11. Those moments were returned to and reversed, so that multiple potentialities could be seen, beyond or in addition to what had taken place. The deputy director of an intelligence fusion centre told me in an interview, “it is always a local cop who saw something” and he replayed how the incidents of contact had unfolded with the men. These scenarios offered a way to recapture the past. In the uncertainty of every encounter, whether a traffic stop or questioning someone taking photos of a landmark (and potential terrorist target), was also potential. Through a process of re-imagining, police encounters with the public became part of the government’s “national intelligence” strategy. Previously a division had been marked between foreign and domestic intelligence. While the phrase “national intelligence” had long been used, notably in National Intelligence Estimates, after 9/11 it became more significant. The overall director of the US intelligence community became the Director National Intelligence, for instance, and the cohesive term marked the way that increasingly diverse institutional components, types of data and forms of action were evolving to address the collection of data and intelligence production (McConnell). In a series of working groups mobilised by members of major police professional organisations, and funded by the US Department of Justice, career officers and representatives from federal agencies produced detailed recommendations and plans for involving police in the new Information Sharing Environment. Among the plans drawn up during this period was what would eventually come to be the Nationwide Suspicious Activity Reporting Initiative, built principally around the idea of encounters such as the one between Parkins and Al Hazmi. Map 1: Map of pilot sites in the Nationwide Suspicious Activity Reporting Evaluation Environment in 2010 (courtesy of the author; no longer available online). Map 2: Map of participating sites in the Nationwide Suspicious Activity Reporting Initiative, as of 2014. In an interview, a fusion centre director who participated in this planning as well as its implementation, told me that his thought had been, “if we train state and local cops to understand pre-terrorism indicators, if we train them to be more curious, and to question more what they see,” this could feed into “a system where they could actually get that information to somebody where it matters.” In devising the reporting initiative, the working groups counter-actualised the scenarios of those encounters, and the kinds of larger plots to which they were understood to belong, in order to extract a set of concepts: categories of suspicious “activities” or “patterns of behaviour” corresponding to the phases of a terrorism event in the process of becoming (Deleuze, Negotiations). This conceptualisation of terrorism was standardised, so that it could be taught, and applied, in discerning and documenting the incidents comprising an event’s phases. In police officer training, the various suspicious behaviours were called “terrorism precursor activities” and were divided between criminal and non-criminal. “Functional Standards,” developed by the Los Angeles Police Department and then tested by the Department of Homeland Security (DHS), served to code the observed behaviours for sharing (via compatible communication protocols) up the federal hierarchy and also horizontally between states and regions. In the popular parlance of videos made for the public by local police departments and DHS, which would come to populate the internet within a few years, these categories were “signs of terrorism,” more specifically: surveillance, eliciting information, testing security, and so on. Image 3: “The Seven Signs of Terrorism (sometimes eight).” CC BY-SA 4.0 2015 by author, using materials in the public domain. If the problem of 9/11 had been that the men who would become hijackers had gone unnoticed, the basic idea of the Suspicious Activity Reporting Initiative was to create a mechanism through which the eyes and ears of everyone could contribute to their detection. In this vein, “If You See Something, Say Something™” was a campaign that originated with the New York City Metropolitan Transportation Authority, and was then licensed for use to DHS. The tips and leads

Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.

Full frame distilled prediction

Teacher imitation

Not calibrated prevalence, not ground truth. Human validation pending. Learned from the 10,348 direct Codex labels and 10,348 direct Gemma labels. Candidate is the union of thresholded teacher heads; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels or direct frontier model labels.

metaresearch head score (Codex)0.001
metaresearch head score (Gemma)0.000
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesInsufficient payload (model declined to judge)
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Not applicable · Consensus signal: none
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.486
Threshold uncertainty score0.999

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0010.000
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0000.000
Science and technology studies0.0000.000
Scholarly communication0.0000.000
Open science0.0000.000
Research integrity0.0000.000
Insufficient payload (model declined to judge)0.0020.000

Machine scores (provisional)

The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.

Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.

Opus teacher head0.045
GPT teacher head0.294
Teacher spread0.249 · how far apart the two teachers sit on this one work
Validation statusscore_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from it