Being told, and being heard

This one is not a new problem. It is an existing sentence that got filed four times as evidence for something else, and never once as a claim in its own right.

The account makes the same structural complaint in four places:

• Nothing tells you what is closed. No signage, no central mechanism of notification, main thoroughfares that simply end. Construction disruption.
• When information is published, it is unusable. A diversion route presented over a Zoom planning committee that “literally looked like a plate of spaghetti”, passed as public information about road diversions. The pedestrian testimony.
• Asking directly gets you nothing. A direct approach to the company running a site next to the household’s home produced no response at all, on a question — how long will this noise continue — that the resident had no other way to answer. One hundred and ten decibels.
• There is no route for objecting to the damage after the fact. Businesses shuttering under prolonged works, with nothing offered and nowhere to say so. Small businesses.

Those four are the same failure at four points on one process: before (notification), during (usable information), on request (a question answered), after (an objection heard). Read as one thing rather than four, it is the closest thing the material has to a single finding.

Why it might matter more than the areas it sits inside

Every substantive grievance in this project runs into a jurisdiction problem. The works are probably not the municipality’s to run; the fare is not its to set; landlord–tenant law is national; the horns are the police’s. Those are real constraints and the powers doctrine exists because of them.

Publishing what you already know is the one act that does not have that problem. A municipality does not need the Interior Ministry’s confirmation to put a map on a website, to answer a question, or to say when a thing will end. If the jurisdiction gate confirms that — and it has not yet been run, so nothing here is established — then the consultation failure would be the rare case of a grievance that is both severe and squarely class A.

It is also the point at which the resident’s own account turns from complaint into diagnosis: the closing note of the third dictation is not about noise or buses but about being asked to look away towards a future that has not arrived, by an administration that is not engaging with the people it is disrupting.

What is not established

Everything, and specifically:

#	Question	Status
1	What Jerusalem is actually obliged to publish about works in the public way, and under which instrument	[UNVERIFIED]
2	Whether a central works/closures register exists at all — in Hebrew, and whether the account’s author would have found it	[UNVERIFIED]
3	The statutory objection routes that do exist (planning objections, the local committee, the community administrations) and why they were not experienced as available	[UNVERIFIED]
4	Whether the municipality can compel a contractor or a delivering body to answer a resident, or only ask	[UNVERIFIED]
5	What comparable Israeli municipalities publish — the precedent test, which under the doctrine settles feasibility faster than statutory reading	[UNVERIFIED]

What would open it

Testimony from someone who tried to use a formal route — objected to a plan, went to a committee, called the hotline, wrote to a community administration — and can say what happened. The account on file describes the absence of a route; it does not describe using one. Those are different claims and only the second supports a proposal.

Related and separately recorded: what happens when you complain.