Skip to content
Make AI Good

Graph · Message

Google Should Not Be in the Business of War

01 · In focus

One message, in the field.

The structured facts the source records about Google Should Not Be in the Business of War, the count of declared adjacencies in the corpus, and the federation map zoomed on this node and its neighbours.

message

4 declared connections

Kind
Message
Status
active
Confidence
high
Entity ID
msg-google-not-in-the-business-of-war
Network
View in network

Tags us, international, mountain-view, framing, slogan, open-letter, anonymous-worker-letter, internal-dissent, tech-worker-organising, tech-worker-conscience, big-tech-accountability, military-ai, ai-and-warfare, drone-surveillance, computer-vision, automated-targeting, project-maven, google, alphabet, sundar-pichai, meredith-whittaker, tech-workers-coalition, icrac, lucy-suchman, federal-contracting, dod, pentagon, founding-artefact, ai-principles, resignations, no-tech-for-ice-precursor, no-tech-for-apartheid-precursor, business-of-war

Google Should Not Be in the Business of War · 2 direct neighbours visible

02 · Connections

4 adjacencies, by relation.

Split by direction. Direct links are the ones Google Should Not Be in the Business of War’s source record names; inferred backlinks are records elsewhere in the corpus that point at this entity.

Direct from this record

2 links

Links named in this entity's structured fields.

Inferred backlinks

2 links

Other records that name this entity.

03 · Background

From the source record.

Body prose as it appears in movement-graph’s published markdown for this entity. Links to other corpus entities resolve to their graph page; links to deeper repo paths are kept as text so the page does not invent a route.

"Google Should Not Be in the Business of War" is the framing of the spring-2018 open letter from more than 3,100 Google employees addressed to CEO Sundar Pichai, opening with the line "We believe that Google should not be in the business of war" and demanding that Google cancel its participation in Project Maven — the US Department of Defense's Algorithmic Warfare Cross-Functional Team — and "draft, publicize, and enforce a clear policy stating that neither Google nor its contractors will ever build warfare technology". The letter is the founding public artefact of the contemporary tech-worker-conscience organising lineage this corpus tracks: its anonymous-internal-letter form, its multi-team cross-functional organising shape, and its "no [tech] for [state-violence system]" rhetorical posture were the documented template the #NoTechForICE campaign drew on six months later (October 2018), and the No Tech For Apartheid campaign drew on three years later (October 2021). It also produced, inside three months, the most consequential single corporate-policy outcome the tech-worker conscience movement has yet documented: Google's 1 June 2018 announcement that it would not renew the Maven contract, and its 7 June 2018 publication of "AI at Google: our principles" naming weapons and norms-violating surveillance among the four "applications we will not pursue".

Origin

The letter was first reported by the New York Times on 4 April 2018 — by then it had been circulating internally on Google's communications servers for several weeks and had collected 3,100 signatures. Its proximate trigger was the late-2017 internal disclosure that Google had signed a US Department of Defense contract — publicly framed as worth around $9 million — to supply machine-learning systems for Project Maven, the Algorithmic Warfare Cross-Functional Team that then-Deputy Secretary of Defense Robert Work had stood up on 26 April 2017 to apply machine vision and deep learning to drone-camera footage from US military intelligence, surveillance, and reconnaissance platforms.

The letter was organised by then-Google AI researcher Meredith Whittaker — a co-founder of the AI Now Institute earlier that year — and an autonomous cross-team Google employee group that Collective Action in Tech's retrospective records as spanning Cloud, AI, Communications, the Google Brain team, and DeepMind by January 2018. The text was anonymous — no signatory names were public — and its two-part operational demand was the load-bearing structure on which the rest of the campaign hung: first, that Google cancel the Maven contract; second, that the company commit to a clear, publicly enforced policy that "neither Google nor its contractors will ever build warfare technology". The first part of the demand was concrete and time-bounded, anchored on a specific contract the company could withdraw from; the second part lifted the framing from a single-contract objection to a structural one about what Google as an institution would and would not build, and it is the second part of the demand that supplies the framing's afterlife.

The supply-chain framing

The letter's substantive ground was the same supply-chain frame that the later #NoTechForICE and No Tech For Apartheid letters would inherit. Maven's military product — the automated identification of objects in drone-camera footage for US intelligence, surveillance, and reconnaissance operations — was not itself a weapons system; it was an information-system component that fed into the targeting and operational tempo of weapons systems. The letter's argument was that distinction-making at that level was unsafe: that the supply of machine-vision infrastructure to a state-violence platform constituted "build[ing] warfare technology" regardless of whether the contracting tech company built the kinetic end-product. That argument located the corporate-complicity objection at the scale of the contract and the supply relationship, not at the scale of any individual targeting decision or operational mission — the same scale-of-objection move the No Tech For Apartheid campaign would later make about Project Nimbus's cloud and AI services, and the #NoTechForICE campaign about ICE's Investigative Case Management infrastructure.

Travel into the tech-worker dissent movement

The framing's first external propagation was the Tech Workers Coalition's Coworker.org petition "Tech should not be in the business of war" — published on 19 April 2018, fifteen days after the NYT's first report — which translated the Google-internal demand into a cross-company tech-industry one addressed to Google, Amazon, Microsoft, and IBM, with the opening "We are tech industry employees concerned about the lack of accountability, accuracy, and safety in the use of artificial intelligence (AI) technology in offensive capabilities of the U.S. Military". The Coworker petition collected 332 signatures across the four companies before being marked "successful" on 1 June 2018, the day Google announced non-renewal. The petition was the framing's first hop out of the originating company and into the cross-company tech-industry worker base that the Tech Workers Coalition was assembling at the time.

The academic-side amplification came one month later. On 15 May 2018 the International Committee for Robot Arms Control (ICRAC) — a 2009-founded coalition of researchers, scientists, and ethicists working on autonomous-weapons accountability — published an open letter "in support of Google employees and tech workers" co-authored by Lucy Suchman of Lancaster University and signed by hundreds of academics in AI, ethics, and computer science. The ICRAC letter took the Google workers' two-part demand and extended it into a three-part academic-side companion: terminate the Maven contract, commit not to develop military technologies or allow personal data collected by Google to be used for military operations, and pledge to neither participate in nor support the development, manufacture, trade, or use of autonomous weapons. The pairing — the worker-letter and the academic-letter running on different fronts of the same demand — is the template the Stop Killer Robots autonomous-weapons advocacy movement and the broader humanitarian-disarmament coalition had already developed for the LAWS file, and that the tech-worker conscience framing imported into the corporate-supply register.

Inside Google itself, The Intercept's 1 June 2018 reporting records "nearly a dozen" employees who resigned in protest before the non-renewal announcement; Collective Action in Tech's retrospective notes the eventual internal signatory count grew toward 5,000 across the campaign's full arc, the company's senior leadership made repeated "ethics is complicated, ethics is hard" responses in internal forums, and the cross-team organising shape included petition-gathering, all-hands question coordination, internal media tracking, meme distribution, and personal-statement collection — a self-organised employee campaign apparatus rather than a single-letter signing exercise.

Corporate-policy outcome

The outcome ran on two tracks in the first week of June 2018. On 1 June 2018, Google Cloud chief Diane Greene announced at a Friday-morning briefing that Google would not renew the Maven contract when it expired in March 2019 — the most consequential single piece of tech-worker-driven corporate-policy revision the contemporary movement has yet produced on the public record. Six days later, on 7 June 2018, Sundar Pichai published "AI at Google: our principles" — a corporate-policy document setting out seven affirmative principles (be socially beneficial; avoid creating or reinforcing unfair bias; be built and tested for safety; be accountable to people; incorporate privacy design principles; uphold high standards of scientific excellence; be made available for uses that accord with these principles) and four "applications we will not pursue" categories, two of which directly mirrored the worker letter's structural objection: "weapons or other technologies whose principal purpose or implementation is to cause or directly facilitate injury to people" and "technologies that gather or use information for surveillance violating internationally accepted norms".

The Maven contract itself did not end with Google's withdrawal. Per the Project Maven public record, the contract was transferred to Palantir Technologies, which became the project's principal subsequent contractor — an outcome the campaign's organisers have read both as a concrete win (Google's specific corporate-policy revision and its withdrawal from a contract it had signed) and as a limit on the supply-chain framing's reach (the underlying state-violence platform did not lose its commercial supplier; the supply relationship moved to a different contractor whose worker base had no comparable internal organising capacity at the time). The framing's own analytic premise — that the corporate-supply objection holds at the level of the contract and the supply relationship rather than the level of any single company — anticipates that limit: the move from Google to Palantir is the move the framing predicts and the move the subsequent #NoTechForICE and No Tech For Apartheid campaigns were structured to address by addressing the supply chain as a chain rather than as a single named contractor.

Carriage into the corpus

Two corpus-side propagation paths anchor the framing in this graph. The direct downstream lineage is into #NoTechForICE, the October 2018 Mijente-led campaign that translated the Google workers' "no [tech] for [state-violence system]" rhetorical form into the immigration-enforcement supply-chain register, six months after Google's withdrawal from Maven and inside the same Trump-administration political-cycle window. The campaign's working architecture — tech-worker dissent inside the contracting companies, student-side pressure on the tech-talent recruitment pipeline, faith and civil-liberties coalition pressure, direct-action confrontations — is the documented organisational template the Google Maven campaign developed, generalised by Mijente to a cross-company coalition addressing a single state-violence supply chain. The further downstream lineage is into No Tech For Apartheid, whose 12 October 2021 anonymous Guardian open letter by more than 500 Google and Amazon workers explicitly traces the lineage in its own text — "we have watched Google and Amazon aggressively pursue contracts with institutions like the US Department of Defense, Immigration and Customs Enforcement (ICE), and state and local police departments" — naming the Maven, ICE, and police-contracting cases as the prior worker-dissent record on which the Nimbus letter is built.

The framing also surfaces inside the corpus through the Stop Killer Robots campaign chronology, which records Google's June 2018 withdrawal from Maven and its adoption of weapons-excluding AI principles as a milestone in the autonomous-weapons advocacy coalition's own public-record timeline — the documented intersection between the humanitarian-disarmament register and the tech-worker conscience register on the same corporate-supply question.

The framing's authoring body — an autonomous cross-team employee group inside Google — is not formally an organisation, has no institutional name beyond the company that employed its members, and is not represented as an Org or Local Group entry in this corpus. Structurally parallel to msg-pause-giant-ai-experiments — whose authoring body (the Future of Life Institute) is also outside the corpus's grassroots-organising remit, and where the in-corpus anchor is the downstream grassroots-organising vehicle (PauseAI) the framing seeded — this message's in-corpus carriage runs through the downstream messages and campaigns the framing's organising template seeded rather than through a propagating organisation already in corpus.

Why it has carried

Three features have made the framing durable.

First, it pairs a single concrete contract-withdrawal demand with a structural policy commitment. The contract demand — cancel Maven — gave the campaign a specific operational object to point to, with a specific counterparty (the DoD), a specific renewal date (March 2019), and a specific corporate-policy decision (renew or not) that could be won or lost. The structural commitment — "neither Google nor its contractors will ever build warfare technology" — lifted the demand off the single contract and onto the corporate-policy register, supplying the long-run organising target the AI Principles publication translated into a written corporate-policy document. Most subsequent tech-worker conscience campaigns have inherited this two-level architecture; the single-contract demand provides legibility and the policy-commitment demand provides durability.

Second, it built the corporate-policy outcome on an internal worker-organising apparatus rather than on external coalition pressure alone. The cross-team employee group that organised the letter — spanning Cloud, AI, Communications, Brain, and DeepMind — was the campaign's load-bearing structure; the external coalition pressure (the Tech Workers Coalition petition, the ICRAC academic letter) reinforced the internal pressure rather than substituting for it. The corporate-policy revision Google made — non-renewal plus AI Principles — was a response to an internal employee constituency, not to external coalition demands alone. That internal-worker-base architecture is the feature the subsequent worker letters at Amazon (the same period's Rekognition campaign), at Microsoft (the HoloLens campaign at the US Army), at Salesforce (the CBP contract campaign), and at Google again on Nimbus (the 2021 letter) all adopted as their primary organising form rather than reverting to the external-coalition-only template that the autonomous-weapons advocacy field had been working with.

Third, the framing supplies a portable rhetorical template. "We believe that Google should not be in the business of war" is a single-sentence employer-naming opening that compresses the worker-side conscientious-objection move ("we, who work here, do not want to build this") into a sentence that travels. The form is the building block of the no-tech-for-X grammar that the subsequent #NoTechForICE and No Tech For Apartheid campaigns ran on, and the documented public-record artefact in which the worker-side corporate-complicity objection was first staged in the AI / machine-learning context at scale.

04 · Sources

Where this came from.

12 sources listed from the pinned corpus. Links are shown only when the source URL is a valid HTTP(S) address.

  1. cnbc.com

    Checked 2026-05-22

    CNBC's 5 April 2018 coverage of the Google employee letter — primary source for the 3,100-signatory count, the addressee (CEO Sundar Pichai), the letter's opening line "We believe that Google should not be in the business of war", and the letter's two-part demand (cancel Project Maven; draft and publicize a clear policy that neither Google nor its contractors will ever build warfare technology); reports the NYT's same-week first-publication of the letter's existence

  2. vice.com

    Checked 2026-05-22

    Vice / Motherboard reporting on the open letter — corroborates the over-3,000-signatory count, the addressee, and the verbatim opening line; primary source for the campaign's contextualisation alongside contemporaneous research-ethics worries about autonomous-weapons applications of machine vision

  3. en.wikipedia.org

    Checked 2026-05-22

    Wikipedia overview of Project Maven — primary corpus-side anchor for the Algorithmic Warfare Cross-Functional Team's 26 April 2017 launch under Deputy Secretary of Defense Robert Work, the project's drone-footage object-detection and -tracking purpose, the publicly-reported $9 million Google contract value, Google's 2018 non-renewal decision, the transfer of the contract to Palantir, and Meredith Whittaker's named role among the worker protesters

  4. collectiveaction.tech

    Checked 2026-05-22

    Collective Action in Tech's long-form retrospective on the Project Maven campaign — primary source for the timeline (internal dissent from September 2017, at least a dozen teams aware by January 2018, NYT first report 4 April 2018, June 1 2018 non-renewal announcement), the eventual ~5,000-signatory aggregate (internal letter plus subsequent organising), the multi-team cross-functional organising shape spanning Cloud, AI, Communications, the Google Brain team, and DeepMind, and the "ethics is complicated; ethics is hard" leadership response that the campaign treats as documenting management's working posture

  5. en.wikipedia.org

    Checked 2026-05-22

    Wikipedia profile of Meredith Whittaker — primary source for her role at Google's Open Research group at the time, her authorship and organising of the Project Maven employee letter, her co-founding of the AI Now Institute (2017) and her standing in the AI-accountability research field, and her subsequent organising including the November 2018 Google Walkout; secondary cross-reference for Tech Workers Coalition involvement in the wider campaign

  6. coworker.org

    Checked 2026-05-22

    Tech Workers Coalition's 19 April 2018 Coworker.org petition "Tech should not be in the business of war" — primary source for the framing's external propagation one day after the Google internal letter was first reported, the petition's addressee companies (Google, Amazon, Microsoft, IBM), its opening line ("We are tech industry employees concerned about the lack of accountability, accuracy, and safety in the use of artificial intelligence (AI) technology in offensive capabilities of the U.S. Military"), the 332 signatures by petition close, and the campaign's "Google will not renew its AI contract with the Department of Defense" June 2018 victory note

  7. futureoflife.org

    Checked 2026-05-22

    Future of Life Institute write-up of the International Committee for Robot Arms Control (ICRAC) open letter in support of the Google workers — primary source for the May 2018 academic-side letter co-authored by Lucy Suchman, signed by hundreds of academics in AI, ethics, and computer science, calling on Google to terminate the Project Maven contract, commit not to develop military technologies or allow personal data collected to be used for military operations, and pledge to neither participate in nor support the development of autonomous weapons

  8. theintercept.com

    Checked 2026-05-22

    The Intercept's 1 June 2018 report by Lee Fang on Google's non-renewal decision — primary source for the date Google Cloud chief Diane Greene announced internally that the company would not renew the Maven contract when it expired in March 2019, the "nearly a dozen" employees who resigned in protest, and the reference to the several-thousand-strong open letter that preceded the decision

  9. blog.google

    Checked 2026-05-22

    Sundar Pichai's 7 June 2018 Google blog post "AI at Google: our principles" — primary source for the AI Principles publication date six days after the Maven-non-renewal announcement, the seven principles (socially beneficial; avoid creating or reinforcing unfair bias; built and tested for safety; accountable to people; incorporate privacy design; uphold scientific excellence; made available for uses that accord with these principles), and the four "applications we will not pursue" — overall-harm-causing technologies; "weapons or other technologies whose principal purpose or implementation is to cause or directly facilitate injury to people"; "technologies that gather or use information for surveillance violating internationally accepted norms"; technologies whose purpose contravenes widely accepted principles of international law and human rights

  10. thedefensepost.com

    Checked 2026-05-22

    The Defense Post's 7 June 2018 coverage of the AI Principles announcement — secondary source corroborating the publication date, Pichai's authorship of the post, and the substantive scope of the four "applications we will not pursue" commitments

  11. laborforpalestine.net

    Checked 2026-05-22

    Republication of the 12 October 2021 Guardian anonymous open letter "We are Google and Amazon workers. We condemn Project Nimbus" — secondary corpus-side anchor showing the framing's downstream propagation: the No Tech For Apartheid letter explicitly traces the lineage ("we have watched Google and Amazon aggressively pursue contracts with institutions like the US Department of Defense, Immigration and Customs Enforcement (ICE), and state and local police departments") and adopts the same anonymous-internal-letter form

  12. notechforice.com

    Checked 2026-05-22

    Mijente's #NoTechForICE campaign About page — secondary corpus-side anchor showing the framing's October 2018 downstream propagation into the campaign's own working architecture (tech-worker dissent inside contracting companies, student-side pressure, faith and civil-liberties coalition pressure, direct-action confrontations); the campaign's "no tech for" rhetorical form is the direct lineage descendant of the Google workers' 2018 framing

Source: entities/messages/msg-google-not-in-the-business-of-war.md in movement-graph at pin 3cc1a36.