Jerusalem Program
ideological platform of the Zionist Movement
The Jerusalem Program (Hebrew: תוכנית ירושלים) is the ideological platform of the Zionist Movement, and was initially adopted in 1951 at the twenty-third Zionist Congress to replace the Basel Program. The Jerusalem Program differed from the original Basel Program in that it shifted the goals of the Zionist Movement once the State of Israel was already established.
The 1951 Jerusalem Program
The 1951 Jerusalem Program stated that:
The task of Zionism is the consolidation of the State of Israel, the in gathering of exiles in Eretz Israel, and the fostering of the unity of the Jewish people. The program of work of the World Zionist Organization is:
Encouragement of immigration, absorption and integration of immigrants; support of Youth Aliyah; stimulation of agricultural settlement and economic development; acquisition of land as the property of the people.
Intensive work for halutziut (pioneering) and hachsharah (training for halutziut).
Concerted effort to harness funds in order to carry out the tasks of Zionism.
Encouragement of private capital investment.
Fostering of Jewish consciousness by propagating the Zionist idea and strengthening the Zionist Movement; imparting the values of Judaism; Hebrew education and spreading the Hebrew language.
Mobilization of world public opinion for Israel and Zionism.
Participation in efforts to organize and intensify Jewish life on democratic foundations, maintenance and defense of Jewish rights.
This brief starts where responsible research should: with the source description of “Jerusalem Program” as ideological platform of the Zionist Movement. Everything that follows is an evidence route, not borrowed authority.
Why this record matters
The subject matters to the history & society register because the source frames it as ideological platform of the Zionist Movement. Its deeper value depends on whether names, dates, institutions and citations support that framing.
Chronology, provenance and viewpoint should be read together before a broad social or political interpretation is accepted. The source revision retrieved here is dated Aug 11, 2026. The linked authority identifier is Q6185183. None of the 0 selected statements returned an explicit reference. The first chronological checks are 1951.
Later summaries often reconcile disputed chronology or motive more neatly than the contemporary record permits. 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
Compare institutional narratives with records created by participants and affected communities. Dates and formal titles are useful anchors, but not substitutes for context.
- Event chronology
- Institutional context
- Locating named record creators
Contemporary correspondence, government or organizational records, oral histories and cited historical scholarship.
Three-step research path
- Establish the record: confirm the title “Jerusalem Program”, its source revision and the description used here.
- Expand the search: follow Jerusalem Program primary sources, Jerusalem Program archive and Jerusalem 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 “Jerusalem Program”?
- Who created the surviving record, and for what administrative purpose?
- Which voices are present, absent or mediated by the institution?
Search terms from this dossier
This entry incorporates text from “Jerusalem Program” 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.