The lede above is true, and it is one of the stranger facts about the Apollo programme. The software that ran on the Apollo Guidance Computer, the small machine on board both the command module and the lunar module, was not written to a disc, a tape, or any other storage medium that could be edited. It was woven. By hand. Into wire.
The storage technology was called core rope memory. The principle was simple. A magnetic ring was either threaded by a sense wire or not. Through the ring meant one. Around the ring meant zero. To store a program, you ran the wire through the rings in the pattern that represented the bits, in the right sequence, across thousands of cores. Once the wires were in place, the memory module was potted in epoxy and bolted into the spacecraft.
The code was now hardware.
How the rope was made
The looms were not looms. They were specialised wiring rigs at the Raytheon plant in Waltham, Massachusetts. Wiring a single rope module took roughly eight weeks and cost about fifteen thousand dollars in 1960s terms. The Block II Apollo Guidance Computer, the version that flew on the crewed Moon missions, contained multiple rope modules. The arithmetic is straightforward. Each new build of the flight software meant another two-month manufacturing cycle, multiplied across rope sets, with the cost to match.
The work was done by women. Many were recruited from the surrounding textile industry and from the nearby Waltham Watch Company, which had a long tradition of producing the kind of skilled precision labour the rope work demanded. The needle was hollow, with a length of fine wire fed through it. Two workers sat opposite one another, passing the needle through the matrix of cores while an automated jig positioned each ring under an aperture at the right moment. The wire either passed through the core or around it, and that was your bit. The position could not drift.
Apollo engineers sometimes referred to this as the “LOL method,” for “Little Old Ladies.” Whether the term was widely used during the programme itself, or whether it became attached to the work afterwards, has been contested by historians of the AGC such as Ken Shirriff. What is not contested is that the women doing the work were skilled technical employees, inspected and re-inspected by both Raytheon and federal inspectors. Mary Lou Rogers, one of the weavers, has recalled in the Science News account that each component had to be looked at by three or four people before being signed off.
What “no patches” meant
Once a rope was woven, the program was finished. There was no way to fix it on the spacecraft. There was no way to fix it on the ground. A bug discovered late in testing did not produce a code change. It produced a new manufacturing order: another eight-week wiring cycle, another module, another set of inspections.
This is the part of the story that quietly does most of the work. The phrase that gets repeated about the AGC, that it was “the computer that landed Apollo on the Moon,” is true but slightly off-centre. The more accurate phrase is that Apollo landed with the code that had been frozen months earlier, manufactured into copper and ferrite, and signed off by federal inspectors. The famous 1202 alarm during Armstrong and Aldrin’s descent was a response by frozen software to a real-time situation. The software did what the people on the ground hoped it would do, partly because Margaret Hamilton’s team at MIT had insisted on robust handling for exactly this class of overload. By the time the Eagle was on its way to the surface, the part of Hamilton’s argument that mattered most was already physically present in the wire.
The framing worth being careful with
The story of the rope weavers has been told a great deal, and most of the recent retellings carry one of two framings.
The first is sentimental. It dwells on the image of skilled craftswomen knitting men to the Moon, on the contrast between domestic textile work and a high-prestige engineering programme. The contrast is real. It is also a contrast that does some flattening of its own. The women at Raytheon were not knitting in the front room. They were precision technical workers at a defence contractor, working to tolerances checked by government inspectors.
The second framing is the corrective version, which insists that the work was skilled technical labour, that the affectionate “LOL” nickname undersold it, and that the standard sentimental account has functioned as a kind of soft erasure. This corrective is also right.
What we find more interesting than either framing is the underlying fact of the period. For a stretch of years in the 1960s, the software that flew the most visible engineering project of the century was a physical artefact. It had to be designed, debugged, frozen, manufactured, inspected, and bolted in. The line between software and hardware, which has since become a foundational distinction of computing, did not yet exist in the form we now take for granted. A program was a thing you could weigh.
What carries forward
The technical lineage of rope memory is short. Apollo used it because it was light, dense, and effectively unerasable, which suited a flight environment where you did not want a stray particle event to flip a bit in your descent code. Once semiconductor memory became reliable enough for spaceflight, the rope went away.
The organisational lineage is longer and less often noticed. The pattern of carefully verified, manufactured, signed-off code, frozen in advance of a mission, with no last-minute changes possible, has not entirely disappeared from spaceflight. Modern flight software is patchable in ways the Apollo software was not, but the verification regime around it still carries the shape of the older world: long lead times, multiple inspections, change-control discipline, and a strong cultural reluctance to ship code that has not been certified to within an inch of its life.
The looms at Waltham are gone. Some of the discipline that surrounded them is not.
