The escalation log for Block 14D starts at 6:04 AM on a Tuesday. Yaribel pulls it up on the mesh terminal in the community office, coffee untouched at the edge of the table. Three weeks since Rosa Domínguez went back to Mount Sinai full-time. Three weeks of escalation logs that look exactly like they did when Rosa was here.
She timestamps the entries. 6:04, 6:07, 6:11. The first one is a heat sensor on the fourth floor, a refrigerator cycling hot. Triage tier two, which means someone should know, not that someone has to act immediately. The flag went up. Someone checked it. The flag went down. Yaribel scrolls through twenty-one days of this and counts: forty-seven triage-tier events, forty-four resolved within the hour, three passed up to the mesh office, none of them the kind that needed her.
The cluster ran itself.
She sits with this for a moment. Then she opens the secondary log — not the event log but the interaction log, who touched what. She is looking for the names.
Gladys Moreno. Ages 63, retired from the transit authority, lives on the third floor with her mother Carmen who is eighty-four and sleeps badly. Gladys's interaction log shows she accessed the mesh notification tray at 6:02 AM on the day after Rosa left, and at roughly the same time every weekday since. Not on weekends. On weekends the log shows her neighbor Dmitri Petrov, age 41, a building super for two properties on 186th Street who checks the mesh on his morning route. And on days Dmitri is off — three out of the last twenty-one — the log shows Marisol Antigua, age 28, who works from home and starts her workday early enough that she sees the overnight queue before anyone else does.
None of them know each other particularly well. Gladys nods at Dmitri in the elevator. Marisol and Gladys have talked once, about Carmen's hip surgery. Dmitri and Marisol may have never spoken.
None of them are in the loss accountant registry. None of them applied for the function. The function just redistributed itself to whoever was paying attention and willing to spend thirty seconds looking at a notification tray.
Yaribel calls Gladys at 9 AM.
"Am I in trouble?" Gladys asks immediately. Her voice is the kind of careful that means she's already running through what she might have done wrong.
"No," Yaribel says. "I'm trying to understand what you've been doing. Can you walk me through your morning routine?"
Gladys explains it like it's nothing. She wakes at 5:30 because Carmen often needs water or the bathroom, and once she's awake she's awake. By 6 she has coffee going. She checks her phone — news, messages, the building app. The mesh notification tray is in the building app, same screen as the elevator status and the laundry room availability. She started looking at it because one time there was a laundry machine stuck in a cycle, spinning wet clothes for four hours, and someone had to go down and push the button. Since then she just checks. If something is red she calls the building contact. Rosa taught her that, two years ago. It takes thirty seconds.
"Did you know Rosa wasn't doing this anymore?" Yaribel asks.
Gladys pauses. "I figured she was busy. I wasn't going to stop looking at the screen just because Rosa was busy. Someone has to look."
"Did you know Dmitri was also doing it on weekends?"
Another pause. "Dmitri checks the mesh? I didn't know that."
"And Marisol Antigua, on days Dmitri is off."
"Oh," Gladys says. Then: "So we're doing Rosa's job?"
"You're doing what Rosa did," Yaribel says, which she knows is not quite the same thing. "Rosa got paid to do it."
The silence on the line has the texture of something being reorganized. Yaribel can hear Carmen saying something in the background, asking who's on the phone.
"Are you going to pay us?" Gladys asks finally. Not combative. Genuinely asking.
"I don't know," Yaribel says. "That's what I'm trying to figure out."
She hangs up and sits with the call for a while. Outside the mesh office window, the Washington Heights morning is fully underway — delivery trucks, school drop-offs, the bodega on the corner already open with the gate halfway up. The mesh is reading all of it through the sensors in the building facades: foot traffic by block, air quality by corridor, noise level by zone. The data flows into the cluster. Someone needs to watch when the data starts flashing red.
The mesh was not designed to need Rosa. The mesh was designed to surface problems to whoever could address them. Rosa was the person the mesh office paid to be the whoever. But the mesh doesn't know about Rosa. It doesn't have a field for loss accountant. It has a field for triage-tier events and a field for resolution status. The gap between those two fields is where Rosa lived, and where Gladys now lives without knowing it.
Yaribel opens a new document. She's been calling this "informal triage inheritance" in her notes, which is not a term that exists anywhere in the mesh documentation. It is a term she invented to describe something the documentation assumes cannot happen because the documentation assumes a named, paid person is always watching. The documentation is wrong. People watch without being named. They watch because they are already looking at the screen, already awake, already invested in their building in the way that people who live somewhere are invested, which is not the same as the way an employee is invested but is not nothing.
The question Yaribel has been not-quite-asking for three weeks is: what does it mean that the cluster ran anyway?
It could mean the system is resilient. That care work redistributes naturally to whoever is present and paying attention, and the named-and-paid structure is just a formalization of something that happens anyway.
It could mean the system exploits. That the mesh office extracted the triage function from Rosa for a salary, and now extracts it from Gladys for nothing, and the difference between those two situations is that Rosa knew what she was doing and Gladys thought she was just being a neighbor.
Both of these things can be true at the same time. Yaribel has been a mesh researcher for eleven years and she has learned that most things that look like resilience also look like exploitation if you change whose perspective you're standing in.
She writes: The triage function survived Rosa's absence. This is not evidence that the function doesn't require labor. It is evidence that the labor found a new host.
She thinks about the difference between a cluster that runs and a cluster that runs fairly. The Block 14D cluster is running. The sensors are monitored. The escalations are handled. By the metrics the mesh office tracks — response time, resolution rate, escalation accuracy — Block 14D is performing normally. The only thing the metrics don't track is whether the people doing the work are doing it knowingly.
Before she calls Dmitri she pulls the cluster history back six months, looking for the pattern before Rosa. The logs show a previous gap — August of last year, two weeks while Rosa was visiting family in the Dominican Republic. The cluster ran then too. Yaribel finds a different set of names in the interaction log: a building super named Felippe who has since moved, a woman named Grace who Yaribel does not recognize, a man listed in the building directory only as T. Mendes. None of them are in the registry. All of them were just looking.
The Block 14D cluster has never, in the eighteen months Yaribel has been tracking it, actually depended on its named loss accountant for continuous coverage. It has depended on whoever was paying attention. Rosa was paying attention and got paid. The others paid attention for free.
This is not specific to Block 14D.
Yaribel opens the cluster records for eight other buildings in the Heights network and starts a quiet audit. She is looking for how often the formal monitoring log diverges from the interaction log — how often the named person and the actual person are different. It takes her forty minutes. In six of the eight clusters, there are regular contributors to the triage queue who are not in the loss accountant registry. In three of those six, those informal contributors have been active for longer than the most recent registered accountant.
The Heights mesh has been running, for years, on a combination of formal and informal labor that the formal records describe as entirely formal.
In the afternoon she calls Dmitri. He is less surprised than Gladys was. "I figured someone should," he says. "Rosa was doing it. Then she wasn't. I was already going by the building on Saturday mornings anyway."
"Did you know Gladys was doing it on weekdays?"
"I assumed someone was," he says. "I didn't know who. It seemed to be working."
He says this without any apparent irony: it seemed to be working. The infrastructure seemed to be functioning. He checked on the weekends because he didn't know whether anyone was checking during the week, and the interval felt too long to leave unmonitored. He did not ask anyone. He did not tell anyone. He just started checking.
Yaribel asks him how long this would have continued without her call.
"Until it didn't work," he says. "Until something fell through."
She writes this down: until something fell through. Which is how most informal systems end — not by design but by the first failure that is large enough to surface. Dmitri would have kept checking Saturdays until the Saturday he didn't, until the emergency that happened between Saturdays and the Monday when someone found out, until the investigation that would have concluded the loss accountant function was unmaintained because it was unmaintained, which is technically true and misses everything.
By 4 PM she has a preliminary count. The forty-seven triage events over twenty-one days represent roughly twelve hours of total monitoring time, distributed across three people who together put in maybe four hours each. None of them know their contribution. None of them have been thanked. All of them would say they were just doing what you do when you live somewhere.
Yaribel writes the finding: informal triage inheritance is not a system failure. It is the system performing as designed at a layer the design pretended didn't exist.
She will bring this to the next research meeting. She does not yet know what the mesh office will do with it. She suspects they will discuss it for a meeting cycle and then nothing will change, because the informal layer is cheaper than the formal layer and cheaper tends to win.
She thinks about what it would mean to make this visible — not just to the mesh office but to Gladys, to Dmitri, to Marisol, to the six other people she found in her afternoon audit who have been contributing to cluster maintenance without a name in the system. The formal structure would call this volunteerism. The funding model would call it community participation. Yaribel's notes call it something the mesh never budgeted for and cannot stop using.
The system does not know it is doing this. That is the part she cannot reconcile. The mesh office genuinely believes the triage function is staffed by its registry. The registry looks accurate because the function is getting done. The function is getting done because Gladys wakes up at 5:30 and has a phone and lives in a building where something could go wrong. The gap between those two things — the registry and the reality — is not a bug that appeared when Rosa went back to nursing. It is the condition the system has always operated in. Rosa just made it visible by being paid.
Before she closes the document she adds one more line, the thing Gladys said that she has been returning to all day:
"Someone has to look."
Not: someone is paid to look. Not: someone agreed to look. Not: someone is responsible for looking. Someone has to look, the way the laundry room has to work and the elevator has to run and the neighborhood has to function — not because anyone decided it would but because the alternative is a building where the problems stack up until they break. Gladys learned this from Rosa and did not know she was learning a job. She thought she was learning how to be a neighbor.
The mesh doesn't know the difference. That's the problem. That's also, Yaribel writes on her way out the door, the entire argument.
She saves the document at 4:52 PM. The cluster log for Block 14D has already processed three more events since she started writing.