The Reconstruction

I am standing in a trench that is not a trench. It is a service corridor for a 600-millimeter water main that runs beneath Nauky Avenue, and I am the only person in the municipal water authority who volunteered to crawl down here in February. The pipe is cast iron, Soviet-era, installed in 1971.

The pipe is sweating. Condensation beads on its surface like fever on a forehead. I run my hand along the joint where two sections meet and feel the faint irregularity that means the gasket is degrading. I make a note. I take a photograph with my phone, holding it close so the flash catches the mineral deposits — white and green, calcium and copper, the signature of a system that has been losing pressure for years while the reports say everything is nominal.

I am twenty-six years old. I have a degree in municipal engineering. My salary is the equivalent of three hundred euros a month. My mother asks me every Sunday why I don't move to Kyiv. I don't move to Kyiv because these pipes are mine. Not legally. Emotionally. I know every joint, every valve, every bypass in the northern grid. I know that the pressure drops at 6:14 every morning when the Saltivka district wakes up and turns on its taps.

I am giving a lecture on public administration reform to forty-three students, of whom perhaps eleven are listening. This is an improvement over last Thursday, when the number was nine. I know because I count. An academic who does not count his audience is an academic who has already surrendered.

The lecture concerns the Contextual Interoperability Framework — a methodology I have spent seven years developing and which precisely zero municipal administrators have adopted. The framework analyzes six dimensions: legal, organizational, semantic, technical, political, cultural. Each dimension contains nested decision nodes. The whole thing, when properly applied, predicts with reasonable accuracy where a reform will stall. It stalls, invariably, at the cultural dimension. Technology is easy. People are hard. Institutions are people with filing cabinets.

I published this framework in 2013. It was cited four times. Three of those citations were by myself. The fourth was by a graduate student in Tallinn who misspelled my name.

After the lecture, a student — Serhii, a bright boy, sixteen, sitting in because his architecture program has a public policy elective — asks me if the framework has ever been used in practice. I tell him it was piloted in the Tsyrkuny community as a diagnostic tool. He asks what happened. I tell him the community administrators found it illuminating and then proceeded to do exactly what they would have done without it. He laughs. I appreciate the laugh. It means he understands.

I'm going to build things. That's the secret. Not study things, not write about things. Build.

Dunayev's lecture hall smells like radiator dust and cheap floor wax. I'm in the back row because the back row has the widest desk and I need it for sketching. Not buildings. My architecture profs want buildings. I draw what's underneath them — pipe cross-sections, electrical conduit runs, the heating mains that keep this city from freezing every November. The invisible city. The one that actually works.

Dunayev talks about interoperability frameworks. I get maybe sixty percent. The sixty percent says: everything's broken. The forty percent probably says the same thing with more syllables.

After class, Shevchenko Park. A Khrushchyovka panel block on the corner has a crack running from the third floor to the ground, patched with cement that's a different shade of gray. The building wears its repairs like scars. Every building in Kharkiv does. I photograph it. I don't know why yet.

I am debugging a shader in a game engine that renders a building that does not exist yet. The building is a school in Hammarby Sjostad, Stockholm's eco-district, and my job is to make it real before it is real — to create an interactive 3D environment where architects, administrators, parents, and city planners can walk through the building, open doors, look out windows, and argue about corridor widths in a space that currently exists only as thirty-two million polygons and a very large texture atlas.

I work for a GovTech company. We are seven people. Our office is in Sodermalm and our ambitions are Scandinavian, which means moderate in volume and immoderate in scope. We believe that 3D visualization will transform how public institutions make decisions.

The shader is misbehaving because of a normal map that one of our 3D artists generated with inverted green channels. This is the kind of problem that takes four hours to find and four seconds to fix. I find it. I fix it. I do not feel heroic. I feel like a person who spent four hours looking at the wrong shade of gray.

I have never been to Ukraine. I could not find Kharkiv on a map. If you told me that in fifteen years I would be standing in a bombed-out municipal building in that city, showing a woman named Olena how to create a digital twin of a destroyed water main, I would assume you were describing a movie I would not watch.

The northern grid upgrade is approved. Three years of reports, two changes of deputy director, one change of mayor, and finally — the authorization to replace 4.2 kilometers of cast iron with high-density polyethylene. I stand in the project office and look at the plans spread across the table and feel something I do not have a word for in Ukrainian. In English it might be “vindication.” In engineering it is simply: the data was correct and now someone acted on it.

My team is four people: two experienced technicians who know the physical grid better than they know their wives, and two recent graduates who know software better than they know pipe fittings. We are, in our way, a bridge between two centuries.

The European Union has funded a digitalization initiative for Ukrainian municipal governance. Excellent. The initiative requires participating municipalities to adopt standardized data formats for infrastructure reporting. Also excellent. The standardized formats were designed by a consulting firm in Brussels that has never visited Kharkiv, do not accommodate the legal distinctions in Ukrainian municipal law, and require data fields that no Ukrainian municipality actually collects.

I write a fourteen-page analysis of the incompatibilities. I present it to the regional administration. They thank me. They forward it to the Ministry. The Ministry acknowledges receipt. The consulting firm in Brussels revises the format. The revision adds three new fields and removes none of the incompatible ones.

I show Professor Dunayev my infrastructure model. He looks at it for a long time. He asks me how I built it. I tell him: open-source GIS data, a game engine for rendering, public records for pipe diameters and installation dates. He says, “This is what the EU consultants should be building instead of forms.” He means it.

I am twenty-one. I have two years left in the architecture program. I can feel it — not because it's technically impressive, but because it represents a way of seeing the city that nobody is offering. The architects see facades. The engineers see pipes. The administrators see spreadsheets. Nobody sees the whole thing.

We are experimenting with game-engine digital twins for an existing building — a school heating system in Uppsala. The building manager can enter the 3D environment, navigate to the mechanical room, and see real-time temperature data overlaid on the actual geometry of the pipes and radiators. When a valve fails, it turns red in the model before anyone in the building notices the temperature drop.

This is the methodology in action — we create a shared visual reality where all stakeholders work with the same model. No more spreadsheets interpreted differently by different people. One reality. Multiple perspectives.

I read a news article about the war in eastern Ukraine. I feel the appropriate Scandinavian empathy, which is sincere and also abstract. I think about those buildings being damaged and wonder, briefly, whether anyone is documenting what is lost. Then I close the article and return to my shader.

The air raid alert sounds at 4:17 AM. I know the exact time because I check my phone before I move, an absurd habit that persists because habits are the last things to die. I am in Uzhhorod — not my city, not my basement. I am a thousand kilometers from my pipes.

The northern grid I rebuilt — my grid, my four-point-two kilometers of polyethylene, my eighteen months of work — was severed in three places by missile strikes in March 2022. The Saltivka district no longer has running water in most buildings. The treatment plant on Shevchenko Street took a direct hit.

I have a folder on my phone of photographs from the northern grid project. I look at them sometimes, the way you look at photographs of a person who has died — not to remember what they looked like, but to confirm that they existed.

I am teaching a lecture on institutional resilience from the basement of the Faculty of Law building. The air raid alert has been active for forty minutes. Eleven students. Three are in uniform. Two attend via a laptop propped on a chair, transmitting from displacement locations in western Ukraine. The connection drops every few minutes. Nobody comments on this. It is simply how education works now.

I document everything. Not for the journal. For later. I have a notebook — actual paper, because the power goes out and laptops die and paper survives — in which I record every institutional adaptation I observe. How the university maintained accreditation while teaching from basements. How neighborhood committees emerged to manage generators and water distribution without any formal charter.

Because reconstruction is not building things again. It is building institutions that can build things again.

Half a degree. No future. Not self-pity — arithmetic.

The Academy suspended in-person in 2022. Online classes continued, technically, but try learning architecture through a laptop screen in a room where the power dies three times a day and the Wi-Fi drops whenever something hits the grid. I stopped attending. Didn't formally withdraw. Just stopped. The way you stop when the reasons evaporate — not a decision, an accumulation of non-decisions until the absence is the decision.

Back in Kharkiv. Ma's apartment. My childhood bedroom with the Zaha Hadid poster still on the wall. I sleep under it while my city's buildings get taken apart by Shaheds.

The alert goes off at 5:20 AM. My phone says “aerial threat.” I roll over and count. The thump comes fourteen seconds later — far, east side, probably Saltivka again. The all-clear at 5:47. Then another alert at 6:12. This is the rhythm. This is the clock the city runs on now. Not hours and minutes but intervals and impacts.

The hard drive is in my backpack. The infrastructure model. I carry it everywhere and never open it. The data describes a city that doesn't exist anymore — water network reconfigured by missiles, power grid held together with tape and prayers, heating on emergency generators. My beautiful model is a photograph of a corpse.

I see the gap. Not all at once. Understanding arrives in layers.

First layer: a conference in Copenhagen on post-disaster reconstruction. The keynote — World Bank infrastructure specialist, the kind of person who has seen everything and shows it in the flatness of her delivery — puts up a slide. One slide. A timeline: damage documentation to funding-ready project status for a water treatment plant in eastern Ukraine. Fourteen months. I stare at it. Fourteen months from “this is destroyed” to “here is the paperwork to fix it.” Not because the money isn't there — fifty billion euros committed through the EU facility alone. Because somebody has to physically go to the destroyed asset, assess it, classify it, cost it, format it for whichever donor institution will fund it. And there are not enough people to do that work.

Fourteen months. I write the number in my notebook and underline it twice.

Second layer: back in Stockholm, staring at our platform. We build 3D twins of buildings so people can make decisions. What if the building is destroyed? What if the decision is not “paint the corridor blue” but “rebuild the water supply for three hundred thousand people”?

Third layer: a paper. Dense, academic, exactly right. A professor at a Ukrainian university on why international reconstruction tools fail when they ignore local institutional context. The paper reads like a post-mortem written before the patient died. Legal dimensions, organizational dimensions, cultural dimensions. All the things our 3D models cannot render but that determine whether a project succeeds or dies in a filing cabinet.

I email him. He replies in two hours. Brief, formal, more insight per sentence than most white papers I've read. His name is Viktor. He is still in Kharkiv. Still teaching from basements.

The hub is a repurposed warehouse on Haharina Avenue. When I walk in, the first thing I notice is the sound: the hum of GPU workstations overlaid on the distant thud of generators. The second thing is the smell — concrete dust and fresh coffee. The third is a 3D model running on a wall-mounted monitor: a water treatment facility, destroyed, rendered in precise geometry, damage annotations floating around it like a surgeon's notes on an X-ray.

I understand within my first week. Not the technology — the methodology. The systematic approach to a problem I have only ever seen from inside the pipe.

My first assignment: the northern water grid. My grid.

Tuesday morning, Saltivka. The alert sounds at 8:03. I crouch against a building wall, tablet pressed to my chest, counting. The impact is east, maybe two kilometers. Car alarms. Then silence, then the all-clear at 8:31. I stand up, brush grit off my jacket, open the capture interface.

The junction of Heroiv Pratsi and Buchmy. The pipe has sheared at the bell joint — Category 3, structural failure. I photograph it with a steadiness that surprises me, because this is the exact point where I predicted stress concentration twelve years ago. I wrote it in a report. The report went into a cabinet.

The interval between alerts — twenty, thirty minutes — becomes the unit of work. Not hours. Intervals. You learn to think in them. How many captures fit between sirens.

I am, officially, the institutional methodology lead. This means I ensure that the technology platform — a Swedish game-engine digital twin system married to local engineering knowledge — does not crash against the same institutional barriers that have wrecked every previous reform I have observed in thirty years of observation.

My Contextual Interoperability Framework, the one that was cited four times, is now the diagnostic tool applied before any pilot deployment begins. Before the field teams go out with their tablets, I conduct a Rapid Institutional Assessment of the target community. The assessment takes two days and prevents three months of failures.

The Swedish woman, Anna, understands something that most technologists do not: technology is a tool, not a solution. The solution is the institutional fabric that allows the tool to function. She and I have arguments that are productive. She pushes for faster deployment. I push for deeper assessment. We meet in the middle, which is where progress lives.

Twenty-nine. Don't know how I got here. Standard condition for someone whose life was rearranged by forces they didn't pick, who found — against all arithmetic — that the rearrangement led somewhere.

Ma brought the flyer home from the station. Training program, eight weeks, digital infrastructure assessment. She put it on the kitchen table and said nothing. Next morning, still there. Third morning, I picked it up. Ma's silence is louder than most people's arguments.

Week one: field capture. Tablets, standardized angles, damage classification. Intuitive — I've been staring at broken buildings for three years. What changes is the lens. Not “this is broken” but “this is broken in this specific way, which means this cause, this severity, this recovery path.” The alert sounds during our first field exercise and the Swedish trainer freezes. The rest of us — all locals — just shift to cover and keep talking. He learns. The interval is the unit of work.

Week two: the 3D platform. This is where everything clicks. Game-engine visualization — walk through a damaged building from any angle, data layers mapped to geometry. It's my model. The one from the hard drive. Scaled up, made professional, populated with real data instead of my guesses. My hands already know this language.

Olena teaches me the physical layer. She stops at a junction and points down.

“This joint. I filed a report on it in 2015. Gasket was degrading. They filed the report. Joint failed 2018. Replaced. Destroyed 2022. Emergency repair used the wrong fitting.”

“How long will it hold?”

“Eighteen months. Maybe.”

She looks at me the way she looks at everything — flat, precise, patient. “The obvious damage is dramatic. The invisible damage is fatal.”

Week eight: a job. Not a certificate — a salary. Health insurance. Colleagues who build things instead of defending things. The diesel-and-solder smell of generator work replaced by concrete dust and coffee.

I arrive in Kharkiv on a Thursday. I expected devastation. There is devastation. But the city is not its wounds. The city is the people walking to work in the intervals between air raid alerts. The city is the metro, which has not stopped running since the full-scale invasion. The city is the coffee shop on Sumska Street where the barista knows my colleague Phil's order and makes it without asking.

Olena walks me through the northern water grid on a Saturday morning. She points to a junction and says, “This gasket was degrading in 2015. I filed a report. The report was filed. The gasket failed in 2018. It was replaced. The replacement was destroyed in 2022. The emergency repair used an incompatible fitting. It will fail within two years.” She says this with the flat precision of someone stating weather observations. There is no bitterness in her voice. There is something harder than bitterness: certainty.

The first documentation packages from the full 3D deployment go out within two weeks. An engineering firm in Kyiv reports that the packages reduce their preliminary assessment phase by seventy percent. They order forty more.

I am training a woman named Daryna who reminds me of myself at twenty-six: precise, impatient, unreasonably attached to infrastructure that will never thank her.

The hub has processed over two thousand documentation packages since 2030. These packages have fed into more than eight hundred reconstruction projects through the DREAM ecosystem. What began as a pilot in three communities now serves fifteen municipalities in four oblasts.

The northern water grid is rebuilt. Not as I designed it in 2015 — better. The new system incorporates lessons from the destruction: distributed supply with redundant pathways, smart valves with remote monitoring, materials that survive blast overpressure. The digital twin of the new grid lives in our platform, continuously updated, a living document of infrastructure that will serve Kharkiv for fifty years.

My methodology is taught in five countries. I find this alternately gratifying and alarming. Gratifying because the framework works. Alarming because academic adoption always involves simplification, and my framework resists simplification the way a river resists being put in a pipe.

My department has thirty-two students this year. Six of them are international — from Moldova, Georgia, Bangladesh, Colombia — who have come specifically to study post-conflict institutional reconstruction because this is now the only university in the world that teaches it from direct experience.

I am sixty-four years old. My knees have not improved. I am, despite everything, content. Not satisfied — satisfaction is for people who have stopped paying attention. But content, in the sense that the work I have done has mattered, and the work that remains will be done by people I have trained.

I am standing in a building that will, in four days, be the third hub in the network. This one is mine. I do not mean I own it. I mean I operate it.

My team is twelve people. Four are hub veterans from Kharkiv who transferred. Eight are local. Three of the eight are former architecture students whose education was interrupted by the war. I know what that interruption feels like. I know what it feels like when someone says “your skills matter” after years of being told, by circumstance, that they don't.

I think about the hard drive. The one with the old infrastructure model. I found it last year, in a box in my mother's apartment. I opened the files. The model was crude. The data was wrong. But the logic was right. The idea that a city is a system, and that understanding the system is the first step to rebuilding it — that idea was correct. I was twenty-one when I had it. It took a war and a hub and a British director and a Swedish technologist and a Ukrainian professor and a water engineer who never smiles to make it real.

Olena:

I arrive in Odesa the night before. At the hub, the field equipment is the new model — lighter, faster, with an improved capture interface that Serhii's team designed. I notice they have adopted my photo angle protocol for underground infrastructure. He doesn't mention this. I don't ask. Engineers communicate through standards, not words.

I think about the pipe under Nauky Avenue — the Soviet cast iron with the sweating gasket, the one I photographed in 2015 in a trench that was not a trench. That pipe is gone. The grid it served was destroyed and rebuilt and is now monitored by a digital twin that lives in a platform I helped create. My photograph from 2015 is irrelevant. The knowledge it represented is not.

I stand in the doorway and look at the sea. The salt air is doing things to the door hinges that I make a mental note to address. I feel something I have not felt since 2020, when the northern grid upgrade was approved. Not vindication. Not hope. The engineering certainty that a well-designed system, properly maintained, will function. It is a small feeling. It is enough.

Viktor:

Eighteen guests for the opening. Not many by conference standards. But these are not conference people. They are the Odesa regional administration's infrastructure director, representatives from four engineering firms, two delegates from the European Investment Bank's Kyiv office, three community heads from pilot municipalities, the vice-rector of the local polytechnic, and — this surprises me — two researchers from Nairobi who are studying the model for potential application in East Africa.

I look around the room and see the shape of what we have built. It is not a building. It is not a platform. It is not a methodology. It is the intersection of all three — a system that functions because each component respects the others. The technology does not override the institutional context. The institutional context does not block the technology. The training creates people who understand both.

When a framework works, it becomes invisible — the way grammar disappears into speech, the way plumbing disappears into water.

Serhii:

Phil said I should give a speech. Viktor said something about institutional ceremonies. Olena said nothing. Anna texted: “Short. Engineers don't listen.”

So I stand in front of this room — my room, my hub, five years traced back to eight weeks traced back to a flyer on a kitchen table — and I say:

“This hub exists because damage exists. We didn't choose the damage. We choose what we do with it. Seven days. That's the gap now — from field capture to a funding-ready package. It was fourteen months. Every day we cut from that gap, someone gets their water back sooner. That's the job.”

I stop. The silence stretches. Then the infrastructure director from the regional administration asks about the second-wave assessment timeline, and I know the speech worked because the room has moved past it and into the work.

Viktor nods. Olena checks her tablet. Anna makes a note.

Anna:

I think about the shader. 2015. An inverted green channel on a normal map for a school that did not yet exist. Four hours to find, four seconds to fix. I did not feel heroic.

I do not feel heroic now. I feel the satisfaction of having built something that works, and the knowledge that it works because of Olena's hands, Viktor's patience, and a twenty-nine-year-old who carried a hard drive through a war because he couldn't let go of the idea that a city is a system.

Serhii's mother arrives on the evening train. She is small, gray-haired, wearing a coat that is too heavy for April in Odesa. She looks at the room — the workstations, the monitors showing 3D models of damaged buildings, the field equipment, the people. She opens her purse and takes out a folded piece of paper. The training program announcement from five years ago, creased and soft from being carried. She says something in Ukrainian that Serhii does not translate immediately. His eyes are wet. He translates:

The air raid app buzzes. Odesa alert. The room pauses — not panic, the practiced calculation of people who assess threat the way others check the weather. The hub is rated as a shelter. Everyone stays.

Serhii's mother folds the flyer and puts it back in her purse. She does not look afraid. She looks like a woman who has carried more important things than paper through worse than this.