← The canon · AItopiaOrAImageddon?

The Turing–Welchman Bombe, and industrial cryptanalysis at Bletchley Park

idea · Alan Turing, who saw that the machine had to be driven by guessed plaintext rather than by the enemy's indicator system, and specified it; Gordon Welchman, whose diagonal board turned a design that mostly produced false stops into one that worked; Harold "Doc" Keen and the British Tabulating Machine Company at Letchworth, who engineered it into something manufacturable and then manufactured it; Marian Rejewski, Jerzy Różycki and Henryk Zygalski of the Polish Cipher Bureau, whose bomba came first and whose handover in July 1939 is the reason there was anything to start from; and the 1,676 Wrens and 263 RAF men who were running 211 of them by the end · 1940

A framing later work is built out of rather than argued about. Cited when the thing being watched descends from it and the descent explains its shape.

Descends from The Hollerith electric tabulating system, and the 1890 census.

Filed under idea in canon/proposals.md, and idea is right — but not on the reasoning the canon usually uses for the kind, and the entry has to say so immediately, because the difference is the whole subject of the file.

The house test for idea, set by shannon-chess-1950 and restated in hollerith-census-1890, is that there is a mechanism here you could build. That test passes trivially. The Bombe is a mechanism to the point that sixty volunteers built one between 1995 and 2007 from drawings GCHQ released fifty-five years after the fact, and it runs, and you can watch it run.

The second clause of build.py's gloss is where it gets interesting: "Cited when the thing being watched descends from it and the descent explains its shape." Nothing a reading watches in 2026 descends from the Bombe as a machine. Nobody builds crib-driven contradiction engines. Enigma died with the war, the machines were dismantled, the drawings went into a GCHQ archive, and the technique has no issue. On a strict reading of the second clause this entry fails.

It is saved by eliza-1966, which is the controlling precedent and is exactly on point. That entry filed a program as idea while conceding that its technique was a dead line — "thirty years of chatbots were built on them and nothing inside a transformer is" — because what descended was not the mechanism but a durable claim about people. The same move applies here, and section 3 does the work of naming what actually descends. It is two things, one institutional and traceable and one analogical and clearly labelled as such, and neither of them is the machine.

Why not moment, which is the strong rival and which fails in the most interesting way available in this canon. The house definition — set by eliza-1966 when it argued its own way out of the kind, and used since by clippy-1996, siri-2011, expert-systems-collapse-1987, lighthill-1973 and bletchley-declaration-2023 — is a date on which something visibly happened in public. There is no shortage of dates here. Victory began work at Bletchley Park in half of Hut 1 in March 1940; Agnus Dei started in Hut 11 on 8 August 1940 with Welchman's diagonal board fitted. Both are dates on which something happened, and what happened was decisive within about a year.

None of it happened in public. That is not an accident of the record; it is the subject of the entry. Nothing about the Bombe was publicly visible on any date between 1940 and 1974. This is the one file in canon/ where the failure of the moment test is itself the content, and it is worth stating plainly what that exposes: the house definition of moment contains a clause — in public — that five entries have been carrying without ever having to defend, because every event they filed happened to be public. This entry is where the clause becomes load- bearing, and rather than quietly amend a settled standard in the file that first strains it, I am accepting the standard and filing elsewhere. If a later session wants to argue that the canon needs a kind for something that happened, mattered enormously, and was invisible, this is the entry that motivates it, and it should be argued in its own proposal rather than smuggled in here.

Why not limit. Tempting for the wrong reason and worth naming so it is not retried. There is a real bound in this story — the Bombe could not find a key without a crib, and a crib is a guess about plaintext supplied by a human from outside the machine — and the temptation is to file that where Gödel and Turing sit, so it can be cited with a theorem's authority. It is an engineering dependency, not a result about what cannot be done. eliza-1966 refused the same move for the same reason, and godel-incompleteness-1931 exists to catch exactly this dressing-up of an observation as a proof.

Why not interpretation or prediction. interpretation would be a different entry: the legend of Bletchley — the lone genius, the machine that won the war — is a reading of events, it is doing real work in 2026, and it deserves an id if anyone wants to propose one. This file is about the machine and the factory and grades the legend in section 7 rather than becoming it. prediction is wrong on subject: there is no dated forecast here. But the secrecy regime was a bet, made on a date, with a due date and an outcome, and section 6 grades it under full prediction discipline — claim, date made, date due, what happened, the insiders' grade and an independent one — because that is the honest way to handle an entry whose central artefact is a decision rather than a document.

The proposal's claim, graded

The proposal line reads:

> bombe-bletchley-1940 — the Bombe and industrial machine cryptanalysis at > Bletchley Park. Cite when: a capability is developed in secret and the secrecy > itself becomes a fact about the field — this work stayed classified for roughly > thirty years, so the discipline rediscovered much of it from scratch, which is > the strongest historical argument that closed capability slows everyone > including its owner. Ancestor of turing-1950.

The instinct is right and the entry belongs. Three of the four factual clauses do not survive contact with the record, and the one that survives does so in a form that strengthens the proposal's own case, which is an unusual failure mode and worth being precise about.

"Stayed classified for roughly thirty years" is right for Ultra and wrong for the Bombe, and the error runs against the proposal. Ultra's existence was secret for twenty-nine years after the war and was broken by F. W. Winterbotham's The Ultra Secret in 1974. That is the thirty-year figure and it is the one everybody quotes. The Bombe itself stayed dark much longer:

| What | Released | Years held | |---|---|---| | That Enigma had been broken at all | 1974 (Winterbotham) | 34 | | The first technical account of the Bombe and Hut 6 | 1982 (Welchman, The Hut Six Story) | 42 | | ~2,000 BTM engineering documents and drawings | 1995, to the Bletchley Park Trust | 55 | | Turing's Treatise on the Enigma ("the Prof's Book") | April 1996, by NSA; later a better copy at TNA HW 25/3 | ~56 | | Turing's "The Applications of Probability to Cryptography" and "Paper on Statistics of Repetitions" | April 2012, by GCHQ to the National Archives | ~70 |

Seventy years, for two mathematical papers with no operational content left in them. If the proposal's argument is that long secrecy has costs, understating the secrecy by a factor of two is conceding ground it did not need to concede.

"The discipline rediscovered much of it from scratch" is the clause that most needs correcting, and the best available scholarship on precisely this question argues close to the opposite. Daniel Shiu's The legacy of Bletchley Park on UK mathematics (arXiv:2403.01331, 2 March 2024) sets out to ask what the cryptologic effort did to British mathematics, and finds transmission rather than loss. Its three findings run directly against the proposal:

So: the clause is not simply false. Attribution was destroyed, publication was delayed by decades, and there are real instances of duplicated effort. But "rediscovered from scratch" is the wrong shape. The knowledge moved through people rather than papers; what was lost was the record, the credit, and the ability of the people who had it to prove they had it. That is a different claim, it is better supported, and it is more useful in 2026, because it is exactly the claim at issue in an argument about whether a capability described only in a system card is a capability the field can be said to hold.

"The strongest historical argument that closed capability slows everyone including its owner" is backwards on the first order and right on the second, and citing it without that distinction gets the case wrong. Bletchley Park is, before it is anything else, the strongest historical argument in existence that closed capability works. Roughly nine thousand people were on the site at the January 1945 peak, nearly ten thousand including the outstations, about three-quarters of them women; more than twelve thousand passed through over the war. Hundreds more built the machines at Letchworth. Six hundred WAVES ran the American programme in Dayton. The secret held — through the war, and then for twenty-nine years of peace, through demobilisation and marriages and deathbeds, with most families never told more than that someone had done "some kind of secret war work." The Germans did not change the machine. On its own terms the closure was a total success, and an entry that leads with its costs is not being sceptical, it is being sentimental in the other direction.

The costs are real, and they are second-order, and — this is the part worth citing — they were paid by different people than the ones who chose the secrecy. Section 6 itemises them. The honest formulation is not "closed capability slows its owner." It is: closure buys a decisive, measurable operating advantage now, and is paid for later, in a currency the decision-makers do not themselves hold — other people's credit, the public record, and the institution's own memory of how the thing was built. That is a sharper claim, it is supported by everything below, and it is the one a 2026 reading actually needs.

"Ancestor of turing-1950" — the canon's own file says no, and I think the canon's file is right but for an incomplete reason. turing-1950 carries descends_from: [lovelace-1843, godel-incompleteness-1931, turing-halting-1936] and says those three are "unusually well-evidenced, because all three ancestors are named in the paper itself." Bletchley is named in the paper nowhere; it could not be, in 1950, by a man still bound. The biographical line is nonetheless real and traceable through documents that are not the 1950 paper: Turing's first recorded use of "intelligence" about a machine is in the ACE report of 1945–46, in connection with chess; the chess work itself began at Bletchley, where Turing and Champernowne developed Turochamp and Michie and Wylie developed Machiavelli, and none of it was published at the time. Whether that makes this file an ancestor of turing-1950 is a judgment for a session editing turing-1950, which this file must not touch. What I will say is that the arrow the proposal draws is at best weakly supported and at worst the wrong way round: the Bombe is better understood as a descendant of Turing's theoretical work than as an ancestor of his philosophical work, and even that descent is thin, as section 3 argues.

The descent, and the ancestors the canon does not hold

hollerith-census-1890, and a name that appears in both files

descends_from: [hollerith-census-1890], and this is the least decorative descent link in the canon so far, because it runs through a person the Hollerith entry already names.

The Bombes were designed and built by the British Tabulating Machine Company at Letchworth in Hertfordshire, thirty-three miles from Bletchley Park. BTM was formed in 1902 as The Tabulator Limited, holding the exclusive right to market Hollerith equipment in Britain and the Empire (Canada excepted) in return for paying twenty-five per cent of its revenues in royalties to the American Tabulating Machine Company — the company that became IBM. It was renamed the British Tabulating Machine Company by 1909, moved to Letchworth in 1920, and at that point began manufacturing rather than merely reselling. The royalty agreement, an increasing burden that BTM repeatedly tried to renegotiate, was finally terminated in 1948 — which is to say it was in force for the whole of the war in which BTM built the Bombes. Whether the Bombe contracts themselves were royalty-bearing is not something this entry could establish and it is not asserted; the agreement's existence through the period is well documented and is enough of an oddity to record.

The man who obtained those British rights in 1902, and who was a founder and director of the company, was Robert Percival Porter — the same Robert P. Porter whom hollerith-census-1890 names in its creator field as the Superintendent of the United States Census Office who set the 1888 competition, wrote the contract and put Hollerith's machines to work on the 1890 count. Porter ran the census that made the punched card, then took the punched card to Britain, then founded the company that thirty-eight years later built the machines that broke Enigma. That is not an analogy. It is one man's career, and it is the reason the capability existed in 1940 at all: Britain could build two hundred Bombes because Britain already had a punched-card industry with a machine shop, a drawing office and a workforce, and it had one because the 1890 census had created the market for it.

This gives hollerith-census-1890 two children in the canon now, on opposite sides of the Atlantic and on opposite sides of the secrecy line: univac-election-1952, which descends through Powers and Remington Rand and put its machine on television, and this file, which descends through Porter and BTM and put its machines behind a fence. Read together they are the canon's cleanest statement that the same industrial lineage produces both the most public and the most secret computing of the mid-century, and that the difference is ownership and not technology — which is the claim LENSES.md makes under Concentration in its own words.

What actually descends, since it is not the machine

Two things, and they are of very different evidential quality. Saying which is which is most of this entry's value.

One, traceable and institutional: the industrialisation of a hard intellectual problem. The design work was months. Turing had the crib-driven approach by late 1939; Welchman had the diagonal board in early 1940; the first machine ran in March. Everything after that was manufacturing and shift-work. BTM's first Bombes took six months each to build; later, produced in batches of six, one came off the line a week. By the end there were 211 machines (the figure given by both the rebuild team and The National Museum of Computing; Wikipedia's type-by-type table sums to about 224, and the discrepancy is noted rather than resolved here), spread across Bletchley and outstations at Adstock, Wavendon, Gayhurst, Stanmore and Eastcote, run around the clock by 1,676 Wrens and 263 RAF men. The Bombe section logged 36,002 jobs at a claimed 97.6 per cent efficiency. The Americans, rather than share a single programme, built 121 more at National Cash Register in Dayton, Ohio, under Joseph Desch, at a cost of about $6 million, staffed by six hundred WAVES.

The framing that descends from this is: a hard intellectual problem can be converted into a manufacturing and staffing problem, and once it has been, the ceiling on the capability is set by how many units you can build and how many people you can put on shifts rather than by how clever anyone is. That framing is built out of rather than argued about, which is what the kind requires. Its institutional descent is direct and unbroken — GC&CS became GCHQ, the Dayton programme's successor institutions are still running, and BTM merged with Powers-Samas in 1959 to become ICT and then ICL, so the British computing industry of the 1960s is the Bombe factory's corporate descendant.

Two, analogical and labelled as such: the 2026 shape of the same thing. A reading that meets a frontier lab whose news is a datacentre rather than an idea, whose binding constraint is fabs and power and floor space, whose output scales with how many identical units it can run simultaneously and how continuously it can run them, is looking at the same shape. This is a rhyme, not a descent. Nobody at a 2026 lab is doing anything because of what happened at Letchworth, and an entry that let the two blur would be doing the thing LENSES.md forbids under record the magnitude, never the consequence. Cited as an analogy, clearly marked, it is useful; cited as lineage, it is false.

The ancestors this canon does not hold, named rather than invented

Following the practice univac-election-1952 set, these are named in prose because inventing ids for them would be worse than admitting the gap.

turing-halting-1936 considered as an ancestor, and declined

The obvious reach, and I am not taking it. Nothing in the Bombe uses anything from On Computable Numbers. The Bombe performs a finite exhaustive search over 1,054,560 configurations, rejecting those that produce a contradiction; the 1936 paper is about undecidability and the universal machine, and neither idea appears in the design. What the two share is an author, and an author is not a descent — the canon would be much poorer if it started drawing lines between entries because the same person turns up in both.

There is a real link and it runs the other way. The Bombe is the first machine Turing specified and got built, and the experience of watching a mechanism execute a chain of deduction and reject contradictions at a thousand configurations a minute is plausibly upstream of everything he wrote about machine intelligence after 1945. That would make this file an ancestor of the ACE report, which the canon does not hold, and possibly of turing-1950, which it does. Adding it to turing-1950's header is that file's decision and not this one's.

A connection the canon already had and did not know

good-intelligence-explosion-1965 is Irving John Good's Speculations Concerning the First Ultraintelligent Machine — the ultraintelligence paper, the source of "the first ultraintelligent machine is the last invention that man need ever make." Good spent the war in Hut 8 under Turing, working on Banburismus, and then in the Newmanry on Tunny. The canon has therefore been holding a Bletchley Park alumnus since that entry was written, without either file knowing it. It is worth recording explicitly, because it means the sequential-Bayesian machinery Good worked out with Turing on naval Enigma in 1941 and the argument he made about recursive self-improvement in 1965 are the same man's work, twenty-four years apart, and the first half was classified when he wrote the second.

What it is

The problem

The German armed forces enciphered their radio traffic on the Enigma, an electromechanical machine with a keyboard, a lampboard, a set of rotating wired rotors, a reflector and — the military addition that made it hard — a plugboard, or Stecker, which swapped pairs of letters before and after the rotor stack. Three rotors chosen from five and set in order; a starting position for each; ten plugboard pairs. The number of configurations is usually given as 158,962,555, 217,826,360,000, about 1.59 × 10²⁰, and the number is quoted in every account because it looks unbreakable and is meant to.

Two properties of the machine mattered more than the number. First, the reflector made the machine reciprocal: if A enciphered to R at a given setting, R enciphered to A, and — the corollary the codebreakers lived on — no letter could ever encipher to itself. Second, the plugboard transformation is self-inverse in the same way: if A is steckered to R then R is steckered to A. Neither property is a weakness in the arithmetic. Both are handles.

Turing's idea

Turing's decision, made before there was a machine, was the one that mattered. The Polish bomba worked by attacking the indicator system — the procedure by which the operator transmitted his chosen message key, doubly enciphered, at the head of the message. It was extremely effective and it was hostage to a procedure the Germans could change at any time. Turing's view, as The National Museum of Computing states it, was that "changes in the German indicating system … would render any equipment based on indicators obsolete overnight."

He was right, and the timing is worth putting on the record because it is the sharpest vindication in the story: on 1 May 1940 the Germans stopped repeating the message key. Every method that depended on the repetition — including the Zygalski sheets Poland had handed over ten months earlier — died that day. Victory had been running for about six weeks. Had Britain built the Polish design it would have been holding scrap by the summer of 1940.

What Turing built instead ran on cribs: guessed plaintext. German signals were stereotyped — weather reports, Wetter Vorhersage; routine acknowledgements; a station that opened every message the same way; and later, when cribs were short, the RAF would mine a specific patch of sea ("gardening") so that the resulting report would contain a known place name. A cryptanalyst laid the guessed plaintext against the ciphertext, slid it until no letter matched itself — the reciprocity rule doing its first job — and drew the resulting letter-pair relationships as a graph, the menu. Where the graph contained closed loops, a hypothesis about one plugboard connection could be propagated round the loop and checked against itself.

The Bombe then tested that hypothesis at every rotor position, mechanically, and stopped whenever it failed to find a contradiction. It is not a brute-force search of the keyspace and it is important not to describe it as one: it is a constraint-propagation engine that uses the crib to collapse the plugboard — the expensive part of the keyspace — out of the problem, leaving 60 wheel orders × 26 × 26 × 26 = 1,054,560 positions to walk through. That is the number the Bombe's designers cared about, against the 1.59 × 10²⁰ that gets quoted.

Welchman's contribution, which is the reason it worked

Turing's original design, the one built into Victory, needed menus containing at least three loops, and even then it stopped too often to be useful. Turing's own estimating table survives and is brutally clear: on a twelve-letter menu with three loops, expect 0.04 stops; with no loops at all, expect 820. Cribs that rich were rare.

Gordon Welchman's diagonal board removed the requirement. He realised that the self-inverse property of the plugboard — if G is steckered to R then R is steckered to G — could be wired into the machine as an additional set of connections, so that a hypothesis propagated not only around the loops in the menu but across the symmetry of the stecker itself. Deductions could then be drawn from menus with few or no loops. In Welchman's own account Turing was sceptical when first shown the diagram and then "became as excited about it as I was." It is the single change that turned a machine which mostly produced false stops into a machine that produced keys, and it is why this entry's title, and the museum's, names both men.

The first Bombe, Victory, without a diagonal board, went to work at Bletchley Park in half of Hut 1. The date is not agreed. The rebuild team and The National Museum of Computing both give 14 March 1940; Wikipedia and a range of secondary accounts give 18 March 1940, some describing it as the date of delivery or installation rather than of first operation. No source read for this entry resolves it and both are recorded here. Victory was out of action for only forty-two hours in its first fourteen months. The second machine, Agnus Dei — shortened to Agnes, then Aggie — was the first with the diagonal board and started in Hut 11 on 8 August 1940. Victory went back to Letchworth afterwards to have one fitted.

The machine as an object

Six and a half feet tall, seven feet long, two feet wide, weighing over a ton. Thirty-six vertical sets of three drums on the front face, each set the electrical equivalent of one Enigma scrambler, with 108 drums in total; the colour-coded drums correspond to the German rotors and are changed by hand for each wheel order. The back is a wall of hand-formed cable — the 2007 rebuild used approximately twelve miles of wire to reproduce it. A three-wheel run took about twenty minutes on the early machines, sixteen by early 1943, and as little as a minute and a half on the later high-speed Keen designs.

When it found a position at which no contradiction arose, it stopped. An operator read the drum positions, wrote them down, restarted it, and passed the candidate to a checking machine, which either produced German or did not. The whole of the first fourteen months of Britain's Enigma capability came out of one machine sitting in half a hut, and Hut 1 was fifteen feet by twelve.

The factory

The Bombes were designated 6/6502, or CANTAB machines, at Letchworth. Final assembly was in the main BTM factory on Icknield Way; sub-assemblies were spread across the town, with drum production in the Spirella corset factory building and more work in the basement of the Ascot Government Training Centre. The project was managed until 1942 by Dora Metcalf, a computing pioneer whose name appears in almost none of the popular accounts. Harold "Doc" Keen was the chief engineer and did the actual engineering design; Turing specified what it had to do, Keen made it a thing that could be built two hundred times.

The security arrangement at Letchworth is the detail worth taking away, and The National Museum of Computing states it plainly: "although literally hundreds of people were involved in the Bombe production, the secret was kept. In fact, security was deliberately kept very low key" — completed machines were driven to Bletchley accompanied by a single soldier, without escort, because a convoy would have been a signal. Hundreds of factory workers building a machine none of them could be told the purpose of, and it held for the duration and for thirty years after.

The operation

Volume gives the best sense of what "industrial" means. Fifty messages decoded a week in 1940; roughly three thousand a day by 1943, against three to five thousand intercepts arriving daily. Hut 6, doing Army and Air Force Enigma, was handling up to a thousand a day with over 450 staff by late 1943. The Wrens worked the Bombes in shifts around the clock, and — a fact the histories tend to bury — most of them were told nothing about what the machines did. Ruth Bourne, a Bombe operator, said she had never heard of Enigma until long after the war.

The dependency: the machine could not do it alone

The most important operational fact about the Bombe, and the one section 7 has to defend against the legend, is that it was never self-sufficient. It needed a crib. Cribs came from German procedure, German laziness, and, when those failed, from physical capture.

The clearest case is Shark. On 1 February 1942 the U-boats of the Atlantic and Mediterranean moved to a four-rotor M4 Enigma on the Triton key, which Bletchley called Shark. The existing three-rotor Bombes could not touch it. Hut 8 was blind for more than ten months — through the worst of the Battle of the Atlantic. It ended not with a machine but with three men. On 30 October 1942, off Port Said, Lieutenant Tony Fasson, Able Seaman Colin Grazier and sixteen-year-old NAAFI canteen assistant Tommy Brown boarded the sinking U-559 and took out the second edition of the Wetterkurzschlüssel, the short weather cipher book. Fasson and Grazier went down with the submarine and were awarded the George Cross posthumously; Brown got the George Medal and died in a house fire in 1945. The captured book supplied cribs, and on the afternoon of 13 December 1942 the naval section telephoned the Admiralty's Operational Intelligence Centre to say Shark was back. Ralph Erskine's estimate is that the resulting intelligence saved somewhere between 500,000 and 750,000 tons of shipping in December 1942 and January 1943 alone.

A capability that depends on the adversary's mistakes and on men swimming into a sinking submarine is not the same kind of thing as a capability that works from first principles, and the difference is the most transferable technical point in this file.

The ending, and the fifty-five-year gap

After the war roughly fifty Bombes were kept at RAF Eastcote — official documents indicate some continued to run, presumably against Eastern-bloc traffic — and the rest were destroyed. Wrens dismantled the machines they had operated. Colossus, the other machine, was broken up on Churchill's order into pieces "no bigger than a man's hand," and Flowers burned the drawings in a furnace at Dollis Hill.

The consequence surfaced fifty years later in a form nobody had planned. In 1995, GCHQ released about two thousand BTM documents and drawings to the Bletchley Park Trust for the rebuild project John Harper had started in 1994. They were component drawings. There were no assembly drawings. Harper's account: "we had individual component drawings returned to Bletchley Park by GCHQ but no assembly drawings." A team that grew to more than sixty volunteers redrew them in AutoCAD, produced about 900 new drawings and 100 new assembly drawings, and — in Harper's phrase — built the machine on paper before building it in steel. The frame went into Hut 11 in September 1997; commissioning ran through 2006 and 2007; the Duke of Kent opened it in July 2007; it won an Engineering Heritage Award in March 2009 and moved to The National Museum of Computing in May 2018, the gallery reopening on 23 June 2018.

A state that had built more than two hundred of a machine could not, fifty-five years later, hand anyone a description of how to put one together. That is not a metaphor for institutional memory loss. It is a documented instance of it, with a date on the release and a count of the drawings that had to be redrawn.

Why a reading would cite it

The proposal's cite case needs the correction in section 2 before it is usable. With that correction made, there are four occasions, and they are not interchangeable.

1. The base rate for how long a decisive capability can stay invisible, and how many people can hold it there

This is the strongest reason to keep the entry, and it cuts against the intuition most 2026 arguments start from. When a reading meets the claim that a frontier capability cannot be kept secret — that someone always talks, that scale makes leaks inevitable, that a lab with ten thousand employees cannot hold a line — this is the counter-example with a headcount attached. Around ten thousand people at Bletchley and its outstations, hundreds more at Letchworth, six hundred WAVES in Dayton, and the existence of the capability held for five years of war and twenty-nine years of peace.

The conditions have to be stated with it or the citation is dishonest. Wartime; conscription; criminal sanction under the Official Secrets Act; a shared and immediate existential threat; no financial upside to defecting; no press willing to print it; and no mechanism by which one person's disclosure could reach a million people in an hour. Every one of those is absent in 2026. What the entry establishes is that large-scale secrecy is possible, which is a weaker and more useful claim than that it is easy, and it establishes the price list of conditions under which it held.

2. The costs of closure are itemisable, and they are charged to people who did not make the decision

This is the citation the proposal wanted and the one section 6 grades. Each of these is a specific, dated cost, and in each the person paying is not the person who chose:

A reading meeting an argument about open weights, published evaluations, or whether a classified capability assessment is worth anything to anyone outside the room should cite this list, and should cite it as a list of second-order costs that were worth paying in 1940, because that is the only form in which it is honest.

3. The precedent for capability whose ceiling is manufacturing rather than insight

Turing and Welchman's contribution was months of work. The next five years were a factory, five outstations, two thousand people and 211 machines. When a reading meets a lab whose announcement is a datacentre, a power contract or a fab allocation rather than a result, this is the historical case where that transition is cleanly observable — where you can see the exact point at which the binding constraint stopped being how clever anyone was. scaling-laws-2020 and bitter-lesson-2019 are the modern statements of the same claim from inside the field; this is the same claim with eighty years of distance and no stake in the outcome. Cited as a rhyme, and labelled as one.

4. The test for what a system was fed, and by whom

The Bombe found keys. It did not find them from nothing: it found them from a guess about the plaintext that a human supplied, and that guess came from stereotyped German procedure, operator error, deliberately provoked signals, and in the Shark case a captured codebook that cost two lives. When a reading meets a claim that a system "solved" a problem, this entry is the precedent for asking the prior question — what was it given, who gave it, and would it work against an adversary who stopped making the mistake? The Germans nearly answered that question themselves on 1 May 1940 and again on 1 February 1942, and both times the capability went dark until a human supplied a new way in.

What it got right, and what it got wrong

Not required for idea, and imported anyway, because the central artefact of this entry is a decision rather than a document and the prediction discipline is the right instrument. The claim being graded is the secrecy regime itself, treated as a bet: made on a date, due on a date, with an outcome, a self-grade from the people who made it and an independent grade that differs.

The bet

The claim, in its own terms: that the existence of the Enigma break must be concealed absolutely — from the enemy, from most of the people doing the work, from allies where possible, from the public indefinitely — because the value of the capability is entirely contingent on the adversary not knowing it exists, and that concealment is worth its costs.

Made: from 1939 onward, hardened into the Ultra distribution regime through 1940–41. Due: twice. Operationally, by May 1945. Historically, by 1974, when the secret broke.

Operationally: right, and by a very large margin

The Germans never concluded that Enigma had been broken. The machine was strengthened repeatedly — rotors IV and V, the plugboard increase, the abandonment of the doubled indicator on 1 May 1940, the four-rotor M4 on 1 February 1942 — but every change was made for its own reasons, and none was a response to a suspicion of compromise. Bletchley went from fifty decodes a week to three thousand a day. The secret held through ten thousand people and five years. On the terms it set for itself, the bet was won outright, and no honest reading of this entry can skip that sentence on the way to the costs.

The magnitude of the win: contested, and this is where a reading must be careful

The insiders' grade. Sir Harry Hinsley, the official historian of British intelligence and himself a Bletchley veteran, in a lecture to the Security Group Seminar at Cambridge on 19 October 1993: without Ultra "the war would have been something like two years longer, perhaps three years longer, possibly four years longer than it was." This is the figure that has entered general circulation, usually stripped of its hedges and its speaker's affiliation, as "Bletchley shortened the war by two years and saved millions of lives."

Independent grades, which differ sharply and in the same direction.

| Assessor | Estimate | |---|---| | Hinsley, 1993 — official historian, Bletchley veteran | two years, perhaps three, possibly four | | John Keegan | possibly as little as three months — the time it took the United States to deploy the atomic bomb | | Jeffrey T. Richelson | about three months on the same reasoning; two years if the atomic programme had failed | | Guy Hartcup | declines to quantify: "It is impossible to calculate in terms of months or years how much Ultra shortened the war" | | John Ferris, Behind the Enigma (2020), authorised GCHQ history | Ultra was effective not in itself but because it meshed with economic and military resources and leadership at every level |

The spread is a factor of eight to sixteen, and the highest number comes from the person with the deepest institutional stake. That is precisely the structure the prediction kind exists to expose, and it is the reason LENSES.md insists on recording the magnitude and never the consequence. A reading that cites "two to four years" without saying who said it, and that serious historians put it as low as three months, is repeating an official history as though it were a measurement. Ferris's formulation is the most citable of the five because it is the only one that describes a mechanism rather than a counterfactual: intelligence was an input, it was not a cause on its own, and it worked because everything around it worked.

Historically: the bet came due in 1974, and this is where it lost

Every cost in section 5.2 is a post-1945 cost. None of them was foreseen in 1940, all of them were foreseeable by about 1950, and the regime was maintained for another quarter-century anyway — through the deaths of participants, through the writing of the histories that got it wrong, and long past any point at which Enigma had operational value. The specific verdicts:

And the proposal's own claims, graded in one place

"Stayed classified for roughly thirty years": right for Ultra, understated by between eight and forty years for the Bombe itself. "The discipline rediscovered much of it from scratch": not supported, and the best study of the question argues the opposite — the knowledge moved through people; the attribution and the public record did not. "The strongest historical argument that closed capability slows everyone including its owner": backwards as stated. It is the strongest historical argument that closed capability works, and a real but second-order argument that the bill arrives later and is paid by others. "Ancestor of turing-1950": weakly supported at best, and possibly the wrong direction. "A capability is developed in secret and the secrecy itself becomes a fact about the field": entirely right, and the reason the entry belongs.

Commonly misused as

Not required for idea. Included because the popular account of this subject is more distorted than that of anything else in the canon, largely by one book and one film, and because a reading that cites the legend instead of the record will get a 2026 argument wrong in a predictable direction.

What the record says. Between 1939 and 1945, a British government organisation, drawing on a Polish break it had been handed five weeks before the war, built and industrially manufactured 211 special-purpose electromechanical machines that tested cryptanalytic hypotheses against guessed plaintext and stopped on contradictions; the machines were designed by two mathematicians in a few months and engineered and produced by a punched-card company; they were operated around the clock by nearly two thousand service personnel, most of whom were not told what they were doing; they depended continuously on enemy procedural error and twice on physical capture; the resulting intelligence was one input among several into an Allied victory whose timing historians estimate Ultra advanced by somewhere between three months and four years; and the whole of it was concealed successfully for twenty-nine years after the war, at costs that fell on people who had not chosen the concealment.

What it is repeatedly made to say, in roughly descending order of frequency:

One thing that is not a misuse, and is worth defending. It is entirely fair to cite this as the founding case of a capability that is decisive, industrial, and invisible at the same time — three properties that in 2026 are usually assumed to be in tension. They were not in tension in 1940, they were held together for five years by an organisation of ten thousand people, and knowing that is worth more to a reading than any of the myths this section clears away.

Sources

Provenance is marked. Where something was read directly it says so; where it comes from a search summary rather than the page, it says that too.