All articles

Nobody's Job · Part 2 of 8 · September 2, 2026

Nobody's Job: The Function No City Ever Funded

By Ricardo Vega

Nobody's Job: The Function No City Ever Funded

By Ricardo Vega


Start with a man I'll call Dale, because that isn't his name.

Dale worked eleven years at a distribution warehouse outside a mid-sized city. He hurt his back. He kept working. The pain got worse, the hours got shorter, and eventually the job went away — not dramatically, just the slow way jobs go away. He had a little savings. He had a truck. He had an ex-wife two states over and a brother he hadn't called in six years, because the last conversation had gone badly and neither of them was the type to call first.

Here is the important part. At no point in the next fourteen months did Dale meet a single person whose job it was to notice.

He met people. He met a leasing agent who processed his non-renewal. He met an emergency room nurse who treated his back and discharged him. He met a caseworker at a county office who determined he did not qualify for the programme he had applied for, and who was correct. He met a police officer who told him he couldn't park overnight where he was parked, and who was polite about it. Every one of those people did their job properly. Not one of their jobs was Dale.

That's the whole thesis. Let me say it plainly, because everything else in this series depends on it.

A city is a set of funded flows. Water comes in. Waste goes out. Power runs along the wires, cars along the roads, data along the fibre. We are astonishingly good at this. There is a person whose job is the pressure in your tap. There is a department that knows when your street is next for resurfacing, and a budget line with a number attached, and a meeting where that number gets defended. We plan these things thirty years out.

Now name the department responsible for noticing that Dale is falling.

There isn't one. There has never been one. Not because anyone decided against it, but because for most of human history that function was free. In a town of four thousand people, Dale doesn't fall fourteen months. He falls about nine days. His brother hears from someone at church. His old boss runs into him at the hardware store. The web is dense enough that he can't drop far without hitting a strand. Nobody budgets for it because nobody has to. The catching is a by-product of everyone knowing everyone.

Then we built cities.

And here's the thing that I don't think gets said enough: the web didn't scale. Cities scale population beautifully. They scale water and power and transit — that's what infrastructure is for. But social connection doesn't work that way. You do not know ten thousand people because you live among a million. You know roughly the same number of people you'd know in a small town. What changes is the ratio. In the town, your handful of connections overlaps with everyone else's, and the mesh is closed. In the city, the same handful floats in a vastly larger space, and the mesh is full of holes.

So the catching rate goes down at exactly the moment the falling volume goes up. Two curves crossing. That's not a policy failure or a moral failure. It's a structural consequence of scale that we never compensated for, because the function was invisible when it was free, and things that are invisible when they're free don't get line items when they stop being free.

Everything we currently do about homelessness happens downstream of that crossing point. Shelters, outreach teams, emergency housing, encampment sweeps — all of it is triage on people who have already fallen all the way. Some of it is good work done by serious people. None of it is the catching function. Catching is what happens at month two, not month fourteen. And month two is nobody's job.

I want to be careful here, because there's an obvious objection and it's a fair one: we can't hire our way to a million watchful neighbours. Correct. That's not the proposal. You don't rebuild a social web by funding it directly — that's been tried, and it produces caseloads, not relationships.

What you can do is build the thing the web used to do. The web did two jobs. It noticed, and it routed. Someone saw you were in trouble, and someone knew where the spare room was, where the odd job was, who had too much of something you didn't have enough of. Noticing and routing. Those are information problems, and information problems are the one category of problem we've gotten dramatically better at solving in the last twenty years — just not, so far, pointed at this.

That's what the rest of this series is about. The next piece starts somewhere unglamorous: behind a strip mall at eleven at night, at a dumpster with about four hundred dollars of edible food in it, and a manager who would genuinely rather have given it away.

Because the resources are already here. The will is probably already here. What's missing is the routing — and the reason it's missing is that catching people was never anybody's job.

Somebody should make it theirs.

We discover what people love — then we use technology to help them do more of it, and teach them to bring others along.

Join the Coalition