Editing Code name

{{Short description|Clandestine term}}
{{Redirect2|Codename|Codenames|the television series|Codename (TV series)|the board game|Codenames (board game)}}
{{More citations needed|date=November 2009}}

{{Intelligence}}A '''code name''', '''codename''', '''call sign''', or '''cryptonym''' is a [[Code word (figure of speech)|code word]] or name used, sometimes clandestinely, to refer to another name, word, project, or person. Code names are often used for military purposes, or in espionage. They may also be used in [[industrial espionage|industrial counter-espionage]] to protect secret projects and the like from business rivals, or to give names to projects whose marketing name has not yet been determined. Another reason for the use of names and phrases in the military is that they transmit with a lower level of cumulative errors over a [[walkie-talkie]] or radio link than actual names.

== Origins ==

=== Achaemenid Empire ===
The [[Achaemenid Empire]] under [[Darius the Great|Darius I]] employed a network of spies called the King’s Eye or the King’s Ear.<ref>{{Cite web |title=Herodotus, The Histories, Book 1, chapter 1, section 0 |url=https://www.perseus.tufts.edu/hopper/text?doc=Perseus:text:1999.01.0126 |access-date=2025-03-06 |website=www.perseus.tufts.edu}}</ref><ref name=":0">{{Cite web |date=2010-01-09 |title=The Eyes and Ears of the King |url=https://garycorby.com/blog//2010/01/eyes-and-ears-of-king.html |access-date=2025-03-06 |website=A dead man fell from the sky... |language=en-US}}</ref> These agents operated under anonymity, and “King’s Eye” was not a specific person but rather a code name for the intelligence network that reported directly to the king.<ref name=":0" />

=== Punic Wars ===
The [[Ancient Carthage|Carthaginian]] general [[Hannibal|Hannibal Barca]] reportedly used coded references for his agents and informants in Rome and among allied territories.<ref name=":1">{{Cite web |title=Titus Livius (Livy), The History of Rome, Book 21, chapter 30 |url=https://www.perseus.tufts.edu/hopper/text?doc=Perseus:text:1999.02.0144:book=21:chapter=30 |access-date=2025-03-06 |website=www.perseus.tufts.edu}}</ref> Some sources suggest that key figures in his intelligence operations were identified using nicknames instead of real names to avoid detection by Roman counterintelligence.<ref name=":1" />

=== Rome ===
[[Julius Caesar]] used [[Cipher|ciphers]] to encode messages and likely employed code names for key operatives.<ref name=":2">{{Cite book |last=Suetonius |url=https://books.google.com/books?id=MeVVDwAAQBAJ&q=Suetonius,+The+Twelve+Caesars+(Life+of+Julius+Caesar) |title=The Twelve Caesars |date=2018-04-18 |publisher=Courier Dover Publications |isbn=978-0-486-83023-0 |language=en}}</ref> His famous [[Caesar cipher]] (simple letter-shifting [[encryption]]) was used to disguise military commands.<ref name=":2" /> He also referred to [[Mark Antony|Marc Antony]] and other generals with shortened or altered names in correspondence to prevent interception from revealing strategic plans.<ref name=":2" />

=== Jewish code names in the Bible ===
During the [[Jewish revolts against Rome]], leaders and messengers used symbolic or misleading names in communications.<ref name=":3">{{Cite web |title=Wicked Priest {{!}} Encyclopedia.com |url=https://www.encyclopedia.com/religion/encyclopedias-almanacs-transcripts-and-maps/wicked-priest |access-date=2025-03-06 |website=www.encyclopedia.com}}</ref><ref name=":4">{{Cite web |last=Wacholder |first=Ben Zion |title=Who Is the Teacher of Righteousness? |url=https://library.biblicalarchaeology.org/article/who-is-the-teacher-of-righteousness/ |access-date=2025-03-06 |website=The BAS Library |language=en-US}}</ref> The Dead Sea Scrolls reference figures such as the “[[Teacher of Righteousness]]” and the “[[Wicked Priest]],” which may have functioned as code names to obscure real identities.<ref name=":3" /><ref name=":4" />

=== Byzantine Empire ===
The [[Byzantine Empire|Byzantine Empire’s]] intelligence agents, particularly under [[Justinian II|Emperor Justinian I]], operated under codenames or titles rather than real identities.<ref name=":5">{{Cite book |last=Procopius |url=https://books.google.com/books?id=w8oX0AEACAAJ |title=Anecdota Or Secret History |date=2023-07-18 |publisher=LEGARE STREET Press |isbn=978-1-01-943447-5 |language=en}}</ref> [[Procopius]] suggests that spies within the Persian and Gothic courts were assigned allegorical names to protect them from discovery.<ref name=":5" />

== Military origins ==
<!-- this section begins with WWI, but switches to WWII at an unclear point with no transition; can someone knowledgeable about the subject make it clearer? -->
During [[First World War|World War I]], names common to the [[Allies of World War I|Allies]] referring to nations, cities, geographical features, military units, military operations, diplomatic meetings, places, and individual persons were agreed upon, adapting pre-war naming procedures in use by the governments concerned. In the British case names were administered and controlled by the Inter Services Security Board (ISSB) staffed by the [[War Office]].<ref>{{Cite journal |last=Webster |first=Graham |year=2013 |title=History of the British Inter-Services Security Board and the Allocation of Code-Names in the Second World War |journal=Intelligence and National Security |volume=29 |issue=5 |pages=1–31 |doi=10.1080/02684527.2013.846731|s2cid=153643351 }}</ref> This procedure was coordinated with the United States when it [[American entry into World War I|entered the war]]. Random lists of names were issued to users in alphabetical blocks of ten words and were selected as required. Words became available for re-use after six months and unused allocations could be reassigned at discretion and according to need. Judicious selection from the available allocation could result in clever meanings and result in an [[aptronym]] or [[backronym]], although policy was to select words that had no obviously deducible connection with what they were supposed to be concealing. Those for the major [[List of World War II conferences|conference meetings]] had a partial naming sequence referring to devices or instruments which had a number as part of their meaning, e.g., the third meeting was "TRIDENT". [[Joseph Stalin]], whose last name means "man of steel", was given the name "GLYPTIC", meaning "an image carved out of stone".

* Reference: Glossary of Names<ref>{{cite web|url=http://www.army.mil/CMH/books/wwii/WCP/glosscn.htm|title=Glossary of Code Names|website=www.army.mil|access-date=27 March 2018|archive-date=16 October 2007|archive-url=https://web.archive.org/web/20071016131213/http://www.army.mil/cmh/books/wwii/WCP/glosscn.htm|url-status=dead}}</ref> from [[U.S. Army]] in [[World War II]] – Washington Command Post: The Operations Division
** World War II Allied Operations<ref>{{Cite web |url=http://homepage.ntlworld.com/frank.kilburn/ |title=WORLD WAR II ALLIED CODE NAMES|access-date=2005-05-02 |archive-url=https://web.archive.org/web/20160304091003/http://homepage.ntlworld.com/frank.kilburn/ |archive-date=2016-03-04 |url-status=dead }}</ref>
** Abbreviations, Acronyms, Codewords, Terms Appearing in WW II Histories and Documents<ref>{{cite web|url=http://www.ibiblio.org/hyperwar/Glossary/index.html|title=HyperWar: Glossary of Abbreviations, Acronyms, Codewords, Terms of WWII|website=www.ibiblio.org|access-date=27 March 2018|archive-date=1 May 2018|archive-url=https://web.archive.org/web/20180501125816/http://www.ibiblio.org/hyperwar/Glossary/index.html|url-status=live}}</ref>
** Information from original files held at [[National Archives (UK)|The National Archives]] (formerly [[Public Record Office|The Public Record Office]]) which hold the publicly available records of central government for the UK

=== German code names ===<!-- This section is linked from [[Manhartsberg]] -->
[[Ewen Montagu]], a British Naval intelligence officer, discloses in ''Beyond Top Secret Ultra'' that during [[World War II]], [[Nazi Germany]] habitually used ''ad hoc'' code names as nicknames which often openly revealed or strongly hinted at their content or function.

Some German code names:

* Golfplatz (German for "golf course") – Britain, employed by the [[Abwehr]]
* Samland – The United States (from [[Uncle Sam]]), employed by the [[Abwehr]]
* [[Heimdall]] (a god whose power was "to see for a hundred miles") – long-range radar
* [[Wotan (deity)|Wotan]] – an [[Y-Gerät|aerial bombing navigation system]]. Knowing that the god Wotan had only one eye, [[R. V. Jones]], a British scientist working for [[RAF Intelligence|Air Intelligence]] of the British [[Air Ministry]] and [[Secret Intelligence Service|SIS]] inferred that the device used a single beam and from that determined, correctly, how it must work. A counter-system was quickly created which made Wotan useless.
* [[Operation Seelöwe]] ([[Sea-lion]]) – plans to invade Britain (lions being prominent in the [[coat of arms of the United Kingdom]])
* [[Operation Barbarossa]] ([[Frederick Barbarossa]]) – plans to go east and invade the Soviet Union

Conversely, [[Operation Wacht am Rhein]] (Watch on the [[Rhine]]) was deliberately named to suggest the opposite of its purpose{{snd}} a defensive "watch" as opposed to a massive [[blitzkrieg]] operation, just as was [[Operation Weserübung]] ([[Weser]]-exercise), which signified the plans to invade [[Norway]] and [[Denmark]] in April 1940.

=== Code names of other powers ===
Britain and the United States developed the security policy of assigning code names intended to give no such clues to the uninitiated. For example, the British counter measures against the [[V-2 rocket|V-2]] was called ''[[Operation Crossbow]]''. The [[Nuclear weapon|atomic bomb]] project centered in [[New Mexico]] was called the [[Manhattan Project]], derived from the [[Manhattan Engineer District]] which managed the program. The code name for the American [[Lockheed A-12|A-12]] / [[Lockheed SR-71 Blackbird|SR-71]] spy plane project, producing the fastest, highest-flying aircraft in the world, was ''Oxcart''. The American group that planned that country's first [[Intercontinental ballistic missile|ICBM]] was called the [[Teapot Committee]].

Although the word could stand for a menace to shipping (in this case, that of Japan), the American code name for the attack on the subtropical island of [[Okinawa Island|Okinawa]] in World War II was ''[[Battle of Okinawa|Operation Iceberg]]''. The Soviet Union's project to base missiles in Cuba was named ''[[Operation Anadyr]]'' after their closest bomber base to the US (just across the Bering Strait from Nome, Alaska). The names of colors are generally avoided in American practice to avoid confusion with meteorological reporting practices. Britain, in contrast, made deliberately non-meaningful use of them, through the system of [[rainbow codes]].

=== Aircraft recognition reporting names ===
{{See also|World War II Allied names for Japanese aircraft}}
Although German and Italian aircraft were not given code names by their Allied opponents, in 1942, Captain Frank T. McCoy, an intelligence officer of the [[USAAF]], invented a system for the identification of Japanese military aircraft. Initially using short, "[[hillbilly]]" boys' names such as "[[Mitsubishi F1M|Pete]]", "[[Aichi E13A|Jake]]", and "[[Nakajima A6M2-N|Rufe]]", the system was later extended to include girls' names and names of trees and birds, and became widely used by the Allies throughout the [[Pacific Ocean theater of World War II|Pacific theater]] of war. This type of naming scheme differs from the other use of code names in that it does not have to be kept secret, but is a means of identification where the official nomenclature is unknown or uncertain.

The policy of recognition reporting names was continued into the [[Cold War]] for Soviet, other [[Warsaw Pact]], and Communist Chinese aircraft. Although this was started by the Air Standards Co-ordinating Committee (ASCC) formed by the United States, United Kingdom, Canada, Australia, and New Zealand, it was extended throughout [[NATO]] as the [[NATO reporting name]] for aircraft, rockets and missiles. These names were considered by the Soviets as being like a nickname given to one's unit by the opponents in a battle. The Soviets did not like the [[Sukhoi Su-25]] getting the code name "[[Sukhoi Su-25|Frogfoot]]". {{Citation needed|date=April 2008}} However, some names were appropriate, such as "Condor" for the [[Antonov An-124]], or, most famously, "Fulcrum" for the [[Mikoyan MiG-29]], which had a "pivotal" role in Soviet air-strategy.

Code names were adopted by the following process. Aerial or space reconnaissance would note a new aircraft at a [[Warsaw Pact]] airbase. The intelligence units would then assign it a code name consisting of the official abbreviation of the base, then a letter, for example, "Ram-A", signifying an aircraft sighted at [[Ramenskoye Airport]]. Missiles were given designations like "TT-5", for the fifth rocket seen at [[Baikonur|Tyura-Tam]]. When more information resulted in knowing a bit about what a missile was used for, it would be given a designation like "SS-6", for the sixth surface-to-surface missile design reported. Finally, when either an aircraft or a missile was able to be photographed with a hand-held camera, instead of a reconnaissance aircraft, it was given a name like "[[Sukhoi Su-27|Flanker]]" or "[[Scud]]"{{snd}} always an English word, as international pilots worldwide are required to learn English. The Soviet manufacturer or designation – which may be mistakenly inferred by NATO – has nothing to do with it.

Jet-powered aircraft received two-syllable names like [[Mikoyan-Gurevich MiG-25|Foxbat]], while propeller aircraft were designated with short names like [[Tupolev Tu-4|Bull]]. Fighter names began with an "F", bombers with a "B", cargo aircraft with a "C". Training aircraft and reconnaissance aircraft were grouped under the word "miscellaneous", and received "M". The same convention applies to missiles, with air-launched ground attack missiles beginning with the letter "K" and surface-to-surface missiles (ranging from [[ICBM|intercontinental ballistic missiles]] to [[antitank]] rockets) with the letter "S", air-to-air missiles "A", and surface-to-air missiles "G".

=== Military operations since Churchill ===
Throughout the Second World War, the British allocation practice favored one-word code names ([[Operation Jubilee|Jubilee]], [[Operation Frankton|Frankton]]). That of the Americans favored longer compound words, although the name [[Operation Overlord|Overlord]] was personally chosen by [[Winston Churchill]] himself. Many examples of both types can be cited, as can exceptions.

Winston Churchill was particular about the quality of code names. He insisted that code words, especially for dangerous operations, would be not overly grand nor petty nor common. One emotional goal he mentions is to never have to report to anyone that their son "was killed in an operation called 'Bunnyhug' or 'Ballyhoo'."<ref>{{cite book |last=Jablonsky |first=David |date=2013-09-13 |title=Churchill, the Great Game and Total War |url=https://books.google.com/books?id=ApvcAAAAQBAJ |publisher=Routledge |page=95 |isbn=9781135199296 }}</ref>

Presently, British forces tend to use one-word names, presumably in keeping with their post-World War II policy of reserving single words for operations and two-word names for exercises. British operation code names are usually randomly generated by a computer and rarely reveal its components or any political implications unlike the American names (e.g., the [[2003 invasion of Iraq]] was called "Operation Telic" compared to Americans' "Operation Iraqi Freedom", obviously chosen for propaganda rather than secrecy). Americans prefer two-word names, whereas the Canadians and Australians use either. The French military currently prefer names drawn from nature (such as colors or the names of animals), for instance ''[[Opération Daguet]]'' ("brocket deer") or ''[[Opération Baliste]]'' ("Triggerfish"). The CIA uses alphabetical prefixes to designate the part of the agency supporting an operation.

In many cases with the United States, the first word of the name has to do with the intent of the program. Programs with "have" as the first word, such as [[Lockheed Have Blue|Have Blue]] for the stealth fighter development, are developmental programs, not meant to produce a production aircraft. Programs that start with Senior, such as Senior Trend for the F-117, are for aircraft in testing meant to enter production.{{citation needed|date=September 2016}}

In the United States code names are commonly set entirely in upper case.<ref name="maryferrell/cryptdb">{{cite web |title=CIA Cryptonyms |url=https://www.maryferrell.org/php/cryptdb.php |website=[[Mary Ferrell Foundation]] |access-date=2023-02-07 |archive-date=2023-02-07 |archive-url=https://web.archive.org/web/20230207020033/https://www.maryferrell.org/php/cryptdb.php |url-status=live }}</ref> This is not done in other countries, though for the UK in British documents the code name is in upper case while operation is shortened to OP e.g., "Op. TELIC".

This presents an opportunity for a bit of public-relations ([[Operation Just Cause]]), or for controversy over the naming choice (Operation Infinite Justice, renamed [[Operation Enduring Freedom]]). Computers are now used to aid in the selection. And further, there is a distinction between the ''secret'' names during former wars and the ''published'' names of recent ones.

== Project code name ==
A '''project code name''' is a code name (usually a single word, short phrase or acronym) which is given to a [[project]] being developed by [[Private industry|industry]], [[academia]], government, and other concerns.

Project code names are typically used for several reasons:

* To uniquely identify the project within the organization. Code names are frequently chosen to be outside the normal business/domain jargon that the organization uses, in order to not conflict with established terminology.
* To assist with maintaining [[secrecy]] of the project against rival concerns. Some corporations routinely change project names in order to further confuse competitors.
* When the goal of the project is to develop one or more commercial ''products'', use of a code name allows the eventual choice of product nomenclature (the name the product(s) are marketed and sold under) to be decoupled from the development effort. This is especially important when one project generates multiple products, or multiple projects are needed to produce a single product. This allows for ''subprojects'' to be given a separate identity from the main project.
* To decouple an early phase of a development effort (which may have failed) from a subsequent phase (which may be given a "fresh start") as a political tool.
* To prevent casual observers from concluding that a pre-release version is a new release of the product, thus helping reduce confusion.

Different organizations have different policies regarding the use and publication of project code names. Some companies take great pains to ''never'' discuss or disclose project code names outside of the company (other than with outside entities who have a need to know, and typically are bound with a [[non-disclosure agreement]]). Other companies never use them in official or formal communications, but widely disseminate project code names through informal channels (often in an attempt to create a [[marketing buzz]] for the project). Still others (such as [[Microsoft]]) discuss code names publicly, and routinely use project code names on beta releases and such, but remove them from final product(s). In the case of Windows 95, the code name "CHICAGO" was left embedded in the [[INF file#Structure|INF File structure]] and remained required through Windows Me. At the other end of the spectrum, [[Apple Inc.|Apple]] includes the project code names for [[Mac OS X]] as part of the official name of the final product, a practice that was started in 2002 with [[Mac OS X v10.2]] "Jaguar". Google and the [[Android Open Source Project|AOSP]] also used this for their [[Android (operating system)|Android]] operating system until 2013, where the code name was different from the release name.

== Notable code names ==
<!-- PLEASE RESPECT ALPHABETICAL ORDER -->{{Excessive examples|date=October 2023|section}}

=== Military ===
* [[Operation Anthropoid]] – assassination of top Nazi [[Reinhard Heydrich]] in Prague
* [[Operation Arc Light]] – [[United States Air Force]] [[B-52]] bombing campaign during the [[Vietnam War]]
* [[Operation Barbarossa]] – German invasion of the [[Soviet Union]]
* Operation [[Black Tornado]] – began on 26 November 2008 and lasted until 29 November when India's [[National Security Guards]] (NSG) conducted Operation Black Tornado to flush out the attackers from the [[Taj Mahal Palace & Tower|Hotel Taj Mahal]], Mumbai
* [[Operation Blue Star]] – was an [[Indian military]] operation which took place 3–8 June 1984, in order to remove [[Jarnail Singh Bhindranwale]] and his armed followers from the [[Harmandir Sahib]] in [[Amritsar]], [[Punjab, India]].
* [[Operation Market Garden]] – failed invasion of Germany (1944)
* [[South African military assistance to the Central African Republic|Operation Morero]] – [[South African Special Forces]] sent to the [[Central African Republic]] to protect president [[François Bozizé]].
* [[Operation Neptune Spear]] – The operation, was carried out in a Central Intelligence Agency-led operation in which [[Osama bin Laden]], the founder and head of the Islamist militant group [[al-Qaeda]], was killed in Pakistan on May 2, 2011, by Navy SEALs of the [[U.S. Naval Special Warfare Development Group]].
** "Geronimo", the code name for Osama bin Laden during [[Operation Neptune's Spear]]
* [[Operation Desert Storm]] – The US code name of the airland conflict from 17 January 1991, through 11 April 1991 in [[Kuwait]] during the [[Gulf War|First Gulf War]].
* [[Operation Overlord]] – [[Allies of World War II|Allied]] invasion of [[Normandy]]
* [[Operation Rolling Thunder]] – the sustained bombing campaign conducted against [[North Vietnam]] by the United States and [[South Vietnam]]
* [[Operation Sea Lion]] – the planned invasion of Britain by [[Nazi Germany]] which was never carried out
* [[Operation Shakti]] – ([[Pokhran-II]]) refers to the series of five nuclear bomb test explosions conducted by [[India]] at the [[Indian Army]]'s [[Pokhran]] Test Range in May 1998. It was initiated with the detonation of one fusion and three fission bombs.
* [[Operation Torch]] – British-American invasion of North Africa in 1942
* [[Manhattan Project]] (with [[Trinity site|Trinity]], [[Little Boy]], and [[Fat Man]]) – U.S. [[nuclear weapons]] program during [[World War II]]
* [[MKULTRA]] – CIA project (an attempt at mind control technology & technique)
* [[Smiling Buddha]] – ([[Pokhran-I]]), was an assigned code name of India's first nuclear weapon explosion, which took place on 18 May 1974. The device was detonated by the Indian Army in the long-constructed army base, [[Pokhran]] Test Range. It was also the first confirmed nuclear test by a nation outside the five permanent members of the United Nations Security Council.
* [[Project-706]] (with [[Chagai-I]] and [[Chagai-II]]) – an early Pakistani secret code name for its nuclear weapons programme during the Cold War
* [[Tank]] – originally a code name adopted in 1915 by the British government for the first tracked armoured vehicles, which were then under development
* [[Tube Alloys]] – British nuclear program
* [[Operation Unthinkable]] - Winston Churchill's plan to invade the Soviet Union [[USSR]]

* [[Special military operation|SVO]], euphemism for 2022 [[Russian invasion of Ukraine]]

=== Commercial ===
{{Further|List of computer technology code names|Working title}}

* [[Advanced Micro Devices|AMD]] have also been naming their CPUs since [[90 nm]] generations under the [[AMD K8|K8]] micro-architecture after the name of cities around the world. For the CPUs under the [[AMD Phenom|Phenom]] brand, the names of stars were used as code names. For [[Opteron]] server CPUs and platforms, cities related to the [[Scuderia Ferrari|Ferrari Formula One team]] were used. Mobile platforms are named after birds (except for Puma). For example:
** Single-core [[Athlon 64]] and [[Athlon 64 FX]] : Newcastle, Venice, San Diego and Lima
** Dual-core [[Athlon 64 X2]] and [[Athlon 64 FX]]: Manchester, Toledo, Windsor and Brisbane
** Phenom CPUs: Agena ([[Beta Centauri]]), Toliman ([[Alpha Centauri]]), Kuma ([[Nu Draconis]]), [[Deneb]] (Alpha Cygni), Propus ([[Eta Geminorum]]), Heka ([[Lambda Orionis]]), Rana ([[Delta Eridani]]), Regor ([[Gamma Velorum]])
** Opteron CPUs: Barcelona, Shanghai, São Paulo, Istanbul
** Server platforms: Catalunya, Fiorano, Maranello
** Mobile CPUs: Griffin, Lion, Swift
** Mobile platforms: Kite, Puma, Shrike, Eagle
* [[Apple Inc.|Apple]] currently names the major releases of [[macOS]] (previously known as Mac OS X) after major California landmarks, such as Mavericks ([[OS X 10.9|10.9]]), Yosemite ([[OS X 10.10|10.10]]), El Capitan ([[OS X 10.11|10.11]]), Sierra ([[macOS 10.12|10.12]] ), High Sierra ([[MacOS High Sierra|10.13]]) Mojave ([[macOS Mojave|10.14]]), Catalina ([[MacOS Catalina|10.15]]), Big Sur ([[MacOS Big Sur|11.0]]), Monterey ([[MacOS Monterey|12.0]]), Ventura ([[MacOS Ventura|13.0]]), and Sonoma ([[MacOS Sonoma|14.0]]). Previous releases were named after [[big cats]]: Cheetah ([[Mac OS X 10.0|10.0]]), Puma ([[Mac OS X 10.1|10.1]]), Jaguar ([[Mac OS X 10.2|10.2]]), Panther ([[Mac OS X 10.3|10.3]]), Tiger ([[Mac OS X 10.4|10.4]]), Leopard ([[Mac OS X 10.5|10.5]]), Snow Leopard ([[Mac OS X 10.6|10.6]]), Lion ([[Mac OS X 10.7|10.7]]), and Mountain Lion ([[OS X 10.8|10.8]]).<ref>{{cite web |url=https://www.apple.com/macosx/ |title=OS X Mountain Lion – Move your Mac even further ahead |publisher=Apple |access-date=2012-11-10 |archive-date=2002-08-29 |archive-url=https://web.archive.org/web/20020829042532/https://www.apple.com/macosx/ |url-status=live }}</ref> Other former code names include:
** Composers, such as [[Copland (operating system)|Copland]], after composer [[Aaron Copland]]; and [[Gershwin operating system|Gershwin]], after [[George Gershwin]]. 
** Women's names, e.g. [[Jennifer (given name)|Jennifer]] (rumored for the [[Macintosh IIx]]), and [[Lisa (given name)|Lisa]]. 
** Varieties of apples, including [[Cortland (apple)|Cortland]] for the [[Apple IIGS]], and [[Mac (computer)|Macintosh]] (from [[McIntosh (apple)|McIntosh]]). 
** Carl Sagan, which was used for the [[Power Macintosh 7100]] while it was under development. In 1994 astronomer [[Carl Sagan]] filed [[Notable litigation of Apple Computer#Libel dispute with Carl Sagan|two lawsuits against Apple]] related to that usage, and lost both, reaching an out-of-court settlement with the company.
* [[Intel]] often names CPU projects after rivers in the American West, particularly in the state of [[Oregon]] (where most of Intel's CPU projects are designed). Examples include Willamette, Deschutes, Yamhill, Tualatin, and Clackamas. See [[List of Intel codenames]].
* [[Microsoft]] often names projects (in particular, versions of the [[Microsoft Windows]] operating systems) after place names. Examples include Chicago ([[Windows 95]]), Daytona ([[Windows NT 3.5]]), Memphis ([[Windows 98]]), Whistler ([[Windows XP]]) and Longhorn ([[Windows Vista]]).
* For a period of time, [[Mozilla]] used code names which are mostly named after [[national park]]s to reference different versions of the [[Mozilla Firefox]] browser:
** Firefox 2.0: [[Bon Echo Provincial Park|Bon Echo]]
** Firefox 3.0: [[Gran Paradiso]]
** Firefox 3.5: [[Shiretoko National Park|Shiretoko]]
** Firefox 3.6: [[Tsingy de Namoroka Strict Nature Reserve|Namoroka]]
** Firefox 4.0: [[Tumucumaque National Park|Tumucumaque]]
** Firefox pre-beta: Aurora
** Firefox trunk builds: Nightly
* [[Nintendo]] often uses code names for new consoles. The best-known is that of [[Wii]], which was code-named Revolution for over a year. Others include the [[GameCube]]'s code name of Dolphin, the [[Game Boy Advance]]'s code name of [[Atlantis]], the [[Nintendo 64]] as Project Reality, the [[Nintendo DS|DS]] code name Project Nitro, the [[Game Boy Micro]] code name Oxygen, the [[Wii U]] code name Project Cafe, and the [[Nintendo Switch|Switch]] as NX.
* ''[[Return of the Jedi]]'' was code-named "Blue Harvest" while in production and principal photography. This was reportedly to prevent disruption by fans and the media as well as to avoid [[price gouging]] by local merchants and vendors.
* ''[[Harry Potter and the Chamber of Secrets (film)|The Chamber of Secrets]]'' sequel of the [[Harry Potter (film series)|''Harry Potter'' film series]] was code-named "Incident of 57th Street" to disguise the production from its increasingly rabid fanbase, who would seek out filming locations and disrupt production.

== See also ==
* [[List of computer technology code names]]
* [[CIA cryptonym]]s
* [[Code word (figure of speech)]]
* [[List of U.S. Department of Defense and partner code names]]
* [[List of Microsoft codenames]]
* [[List of military operations|Military Operations listed by code name]]
* [[List of Rainbow Codes|Rainbow Codes]]
* [[NATO reporting name]]
* [[Pseudonym]], the term for a code name when applied to a single person
* [[Secret Service codename]]
* [[Sensitive Compartmented Information]]
* [[Working title]]

== References ==
{{Reflist}}

== External links ==
* {{Cite book|last=Arkin|first=William M.|author-link=William Arkin|url=https://archive.org/details/codenamesdeciphe00arki|url-access=registration|title=Code Names: Deciphering US Military Plans, Programs, and Operations in the 9/11 World|date=2005|publisher=Steerforth Press|isbn=978-1-58642-083-3|language=en|location=[[South Royalton, Vermont]]}}
* {{Cite web|url=http://www.designation-systems.net/usmilav/codenames.html|title=Code Names for U.S. Military Projects and Operations|website=www.designation-systems.net|access-date=25 April 2020|first1=Andreas|last1=Gehrs-Pahl|first2=Andreas|last2=Parsch|date=4 October 2006}}
* [https://web.archive.org/web/20050203084650/http://www.democracynow.org/article.pl?sid=05%2F01%2F27%2F1359252 Code Names: A Look Behind Secret U.S. Military Plans in the Middle East, Africa and at Home] – Broadcast on ''[[Democracy Now!]]'' January 27, 2005.
* {{Cite journal|title=The Art of Naming Operations|first=Gregory C.|last=Sieminski|url-status=live|url=https://apps.dtic.mil/sti/pdfs/ADA298013.pdf#page=83|archive-url=https://web.archive.org/web/20100607221705/http://www.carlisle.army.mil/USAWC/Parameters/Articles/1995/sieminsk.htm|archive-date=7 June 2010|journal=PARAMETERS, US Army War College Quarterly|publisher=[[United States Army War College]]|volume=XXV|issue=3|pages=[https://apps.dtic.mil/sti/pdfs/ADA298013.pdf#page=83 81]-98|date=Autumn 1995|access-date=25 April 2020|issn=0031-1723|location=[[Carlisle Barracks]], Carlisle, Pennsylvania}} 	

{{Authority control}}
{{Personal names}}

{{DEFAULTSORT:Code Name}}
[[Category:Project management]]
[[Category:Names]]
[[Category:Code names| ]]