Golem (computer)
Open-knowledge reference entry

Golem (גולם) was the name given to three computers built at the Weizmann Institute of Science and used for research at the institute and at other Israeli research centers. The project was led by Smil Ruhman, an American-Israeli computer scientist and electrical engineer who had earlier worked in the early American computer industry before joining the Weizmann Institute.
Background
The first computer built in Israel was WEIZAC, designed and built at Weizmann Institute of Science in 1955 under Chaim Leib Pekeris. It was based on the John von Neumann's computer built at Princeton.
Golem A
At the beginning of 1960, the Department of applied mathematics, headed by Pekeris, began planning a new computer to replace the WEIZAC, which had begun operating in 1955. The new computer was planned to be a hundred times faster than WEIZAC. The computer was first called WEIZAC2, but by advice of the Kabbalah scholar Gershom Scholem was renamed "Golem".
Pekeris invited Smil Ruhman to lead the construction of the new computer. Ruhman had studied electrical engineering at the Worcester Polytechnic Institute and the University of Pennsylvania, and had worked at the Moore School's digital computer laboratory, where he was among the developers of the MSAC and EDVAC computers. He later worked at Raytheon on magnetic circuits and became a co-founder and director of development at Packard Bell's computer division. His earlier work included military and aerospace computer projects and a small computer with about 250 transistors and 4,000 words of memory.
The public source identifies “Golem (computer)” as open-knowledge reference entry. This brief keeps that definition visible, then builds a research path around Golem, computer and Open-knowledge.
Why this record matters
A short description can identify a subject without explaining its stakes. For “Golem (computer)”, the useful work is to connect “open-knowledge reference entry” to the records capable of establishing context and consequence.
The citation trail is more important than the brevity of the summary: it shows where individual claims can be examined in context. The source revision retrieved here is dated Sep 4, 2026. The linked authority identifier is Q7003612. None of the 0 selected statements returned an explicit reference. The first chronological checks are 1955 and 1960.
Overview language is designed for orientation and should not be treated as a substitute for the evidence cited beneath it. The lead is largely declarative, so disagreement and counter-evidence require a deliberate search beyond the opening account. Authority statements aid reconciliation but still require their own references, qualifiers and ranks to be checked.
How to read it
Use the entry as an orientation point, then follow its citations and revision history. Names, dates and institutional relationships should be checked against the original record.
- Subject orientation
- Search vocabulary
- Locating named sources
The closest primary source, responsible institution and strongest cited specialist reference.
Three-step research path
- Establish the record: confirm the title “Golem (computer)”, its source revision and the description used here.
- Expand the search: follow Golem (computer) primary sources, Golem (computer) archive and Golem research across catalogues and specialist indexes.
- Test the account: compare the strongest cited source with the responsible institution’s current record and note any disagreement.
Questions for further research
- Which source most directly establishes the central claim about “Golem (computer)”?
- What terminology or title could unlock a more precise catalogue search?
- Which institution is responsible for the underlying evidence?
Search terms from this dossier
This entry incorporates text from “Golem (computer)” on English Wikipedia. Contributors are listed in the page history. Text is available under the Creative Commons Attribution-ShareAlike 4.0 License. Selected authority identifiers and statements are retrieved from Wikidata under CC0; their references and qualifiers remain part of the verification path.