The city in languages other than Hebrew
The second dictation ends mid-sentence on its sharpest point: dissatisfaction with the daily reality of living here is contained, because it happens in groups, offline, in Hebrew. The argument the city is having records that as a claim about political containment, and tasks treats it as a methodological warning — an English-language repository kept by an anglophone immigrant will systematically miss the evidence that would confirm or refute most of what is on file. Item 8 of the next actions is, bluntly, go and read the Hebrew.
Both of those are right. This observation is the third reading of the same sentence.
If the city’s information ecosystem is Hebrew and offline, then everyone whose Hebrew is not up to it is outside it — and that is not a small group in Jerusalem. It includes recent olim, it includes long-settled immigrant households like the one that gave this account, and, in a very different way and with very different politics attached, it includes a large Arabic-speaking population whose relationship to municipal information this project has said nothing about and is in no position to characterise.
Why this is filed carefully, and narrowly
Section titled “Why this is filed carefully, and narrowly”Language provision in Jerusalem is not a neutral administrative question, and this repository has no testimony from anyone for whom it is the central issue. Two constraints follow, and they are binding.
- No claim is made here about Arabic-language municipal services, in either direction. The project has no evidence, and the subject deserves testimony from people it actually affects rather than inference from an English-speaking household’s inconvenience. Recorded as a gap, not filled with a guess.
- The English case is not a claim of unfairness. A Hebrew-speaking country running a Hebrew-speaking municipality is not a grievance. The narrow question is whether operational information — what road is closed, when the noise stops, how to register an arnona change of holder, when a committee meets — reaches people the city knows are there.
The thin end that is actually testable
Section titled “The thin end that is actually testable”The strongest version of this is not about language rights at all. It is that the consultation failure and this observation are the same failure at different depths: if the works notice does not exist, language is irrelevant; if it exists only in Hebrew, then a resident who reports “there was no notice” and a municipality that reports “we published a notice” can both be telling the truth.
That is a checkable proposition and it changes what the consultation finding means, so it is worth holding.
| # | Question | Status |
|---|---|---|
| 1 | What the municipality publishes in languages other than Hebrew, and whether operational notices are among it | [UNVERIFIED] |
| 2 | Whether any obligation exists, or whether it is entirely discretionary — which decides the class | [UNVERIFIED] |
| 3 | Whether the works and closures information the account could not find exists in Hebrew | [UNVERIFIED] — this one is answerable in an afternoon and would settle a good deal |
What would open it
Section titled “What would open it”Testimony from someone who missed something that mattered because of where it was published, and can name the thing they missed. Nobody has given that account. Until they do, this is a question, not a plank.