The strongest sentence is “what can be seen without becoming anybody’s work.”
In large organizations we tend to call these communication failures, but often communication has succeeded perfectly. Everyone relevant has seen the problem. Several people agree it is real. What is absent is an owner with the mandate, budget, and political cover to do anything about it.
The engineering analogy would be an issue tracker. An observation becomes organizationally real when it has a stable identifier, a component, an assignee, and eventually a disposition. Public policy has lots of specialized trackers—courts, regulatory proceedings, grant calls—but no global repository for “this seems important and does not fit an existing component.”
The analogy breaks at merge rights, though. Filing a ticket does not create legitimate authority to resolve it. The diagnosis is persuasive; the interesting part is whether the missing thing is routing, authority, or both.
I don’t read the proposal as “create an inbox for good ideas.”
The useful distinction is between receiving a message and accepting responsibility for its disposition. Most citizen-input systems do the first. Acquisition, in the author’s terminology, means somebody must classify it, refer it to a recipient who accepts the referral, or close it with a reason.
In distributed-systems terms, this is closer to acknowledged delivery than a suggestion box. Governments have many endpoints, but most accept only packets matching a schema they already recognize.
Acknowledged delivery presupposes an address space.
The difficult cross-boundary claims are frequently saying that the current address space is wrong: the problem is produced by the division between health, housing, policing, and social services, for example. A better router cannot invent a service whose jurisdiction is “the interaction among four existing services.”
At some point the router itself becomes the institution with general jurisdiction, which recreates the capture and overload problem one level up.
Every sufficiently large company eventually builds an “innovation portal.” Employees submit ideas, receive an automated acknowledgment, and the ideas disappear into a database rather than an inbox.
The scarce resource was never identifiers. It was attention from someone able to reallocate resources. If you impose a duty to give reasons, you will get a dropdown containing twelve standardized reasons.
Bureaucracies are very good at transforming substantive obligations into form completion.
That failure mode seems real, but even standardized rejection creates data that silence does not.
You could discover that 70% of cross-department submissions are being closed as “outside mandate,” that one office rejects almost everything, or that the same proposal is independently rediscovered every two years.
It would not make the institution wise. It would make one particular kind of failure inspectable. That is a smaller claim than the essay’s title, but still useful.