Chapter 125 - THE FLOOD MAP

The engineer unfolded the flood map on a table too small for it. Three corners slipped over the edge, and Gabriel had to place paperweights beside the streets to keep the drawing flat. I stood near the window with Marisol, watching a thin blue line curve through the neighborhood and disappear beneath a patch of green marked MUNICIPAL LAND.
"That's the garden," I said.
"Part of it," the engineer, Dr. Priya Shah, answered. "The drainage network doesn't respect the property boundary."
Priya worked for an independent firm retained jointly by the city and a neighborhood coalition. She had reviewed earlier North Row findings, inspected accessible maintenance points, and compared historical storms with newer projections. She warned us that the model could estimate risks, not predict the exact shape of a future flood.
"The question is not whether the gate is good or bad," she said. "The question is whether the proposed equipment allows drainage crews to reach critical points when water rises, and whether runoff from the project makes conditions worse elsewhere."
Owen Price leaned forward. "Can we improve maintenance without installing an electronic barrier?"
"Almost certainly. But we need to compare alternatives on cost, reliability, and access. The present proposal doesn't contain enough analysis to do that."
The room shifted. Some people looked relieved that the problem might have a practical solution. Others looked frustrated that another study was necessary. I was both.
After the meeting Priya took a small group outside. She pointed to the inspection hatch near the proposed control cabinet and explained how a blocked approach could delay a crew carrying pumps and safety equipment. She was precise about what she had actually observed. The existing hatch was accessible on an ordinary dry day. The proposed cabinet might change that. A heavy storm could introduce risks no dry-day inspection could settle.
"This is where North Row lost time," Renee said quietly.
Priya looked at her. "Were you here during the flood?"
"I was across the street. My neighbor kept knocking on the maintenance office door. Nobody answered."
Priya did not respond with a comforting generalization. She asked whether Renee would be willing to describe what she remembered to the independent review team. Renee agreed on the condition that she see the transcript before it was used publicly.
By afternoon dark clouds had gathered over Chicago. I walked with Daniel and Charlotte toward the north boundary where they'd planted the peonies. They had survived the early heat but needed careful watering. Daniel crouched to pull a weed from the soil and paused to read the plaque again.
"If they build something useful, I don't want our story used to stop it," he said. "But I don't want it used to sell another bad idea, either."
Charlotte nodded. "A memorial shouldn't be a weapon."
"I wish more people understood that," I said.
The following week Priya visited a neighborhood middle school to explain flood risk. She had agreed to teach a science class before anyone knew she might become the most quoted engineer in our dispute. The teacher invited me to observe because the students were preparing a display about public spaces and climate.
Priya brought a transparent tray filled with sand, model buildings, and a shallow channel. She poured water slowly upstream and asked the students to predict what would happen if a narrow outlet became blocked. Some thought the water would stop. Others expected it to rise. They watched it spread across the lowest cardboard street.
"Models simplify the world," Priya told them. "That makes them useful and dangerous. We have to remember what we've left out."
A student asked whether their neighborhood was going to flood again. Priya did not make a promise. She explained the warning systems, the drainage repairs under consideration, and the importance of following official emergency instructions. Then she asked what information would help families make decisions. The students suggested clear maps, notices in multiple languages, and a phone number that worked during storms.
When the class ended, I stood beside a wall of student drawings. One showed the garden with a bridge over a river. Another showed a house on stilts beside a tree bearing enormous purple fruit. The futures were imaginative, sometimes impossible, and unashamedly hopeful. I wanted the adults designing the real corridor to remember that they were protecting the conditions in which children could imagine those futures.
On the walk back, Priya told me she'd spent years working on infrastructure projects whose public meetings were dominated by consultants arguing over decimals. "Numbers matter," she said. "But they only matter because of the people affected by them."
At the center we added a student question to the public board, with the class's consent: IF THE WATER CHANGES, CAN OUR PLAN CHANGE TOO? It stood beside Sophie's question about the next generation. I found myself wishing the procurement documents contained as much practical wisdom.
That evening a city representative announced a revised schedule. The decision on the private contract would be delayed by forty-five days so the engineering alternatives could be reviewed. Some residents cheered. Others worried that another postponement meant the drains would go another winter without improvements.
Celeste turned to me. "Both sides have a point. I hate when that happens."
"You hate it because it means more meetings."
"I hate it because it means more coffee. I'm going to run out of mugs."
Luca came home carrying a stack of documents from his auditors. We had agreed not to use dinner as an informal boardroom, so he left them in his office and joined Sophie in the kitchen. They were arguing about whether she could teach him the difficult section of her new composition. He maintained that talent could be inherited. She maintained that practice could not.
When Sophie went upstairs, Luca told me Elaine had found an old maintenance agreement linking a former Moretti subsidiary to a small part of the drainage network. The agreement had expired years earlier, but it might explain why certain drawings were incomplete.
"Was the company responsible for the old flood?" I asked.
"We have no basis to say that. They supplied inspection software. Some archived data may exist, and the auditors are looking for it."
I appreciated his restraint. We had both seen what happened when people treated proximity to a tragedy as proof of responsibility.
On Sunday a heavy storm passed north of the city. The rain at our house was modest, but Priya asked Gabriel to photograph water levels at designated monitoring points after the weather cleared. Only trained crews went near flooded infrastructure. Volunteers handled public observation from safe locations.
One photograph showed the water rising near the garden's lower wall. Another showed a drainage grille partially blocked by leaves and litter. The city maintenance crew cleared the obstruction the same morning after receiving a report.
"Look," Gabriel said, showing us the before-and-after images. "A problem found, reported, and fixed. No conspiracy required."
"We should celebrate those too," I said.
We posted an account of the maintenance response with the dates and agency contact details, after confirming the information. Some people complained that it wasn't dramatic enough. Mrs. Alvarez told them if they wanted drama, they should try growing tomatoes in unpredictable weather.
At the week's end Priya sent a preliminary memo. It identified three options worth considering: public maintenance without a barrier, a revised contractor plan preserving continuous pedestrian access, and a hybrid service agreement with independent oversight. None had yet been fully costed. None guaranteed protection from every future storm.
I read the memo beside our crooked shelf while Sophie practiced upstairs. She was working on a quiet passage that began again every time I thought it had resolved. I thought about the city and the garden, our family and its unfinished agreements. Sometimes a good design was one that allowed a person to change course without having to destroy everything built before.
We brought the memo to the next board meeting, where Marisol asked the simplest question of the night.
I had one more conversation with Owen after the engineering workshop. He was looking at the maintenance budget and shaking his head. "You know what scares me?" he said. "A good plan that nobody can afford to follow."
We sat beneath the library awning while rain dripped from the edge. He explained how a drain inspection could be postponed when crews were diverted to a broken water main, and how an electronic record could still show the scheduled task as active long after the date passed. It was not an excuse for poor work. It was a reminder that staffing and money determined whether procedures became real.
I asked him to write down which resources he believed were necessary for the proposed alternatives. He agreed, on the condition that we include the constraints openly rather than presenting them as proof that one vendor had to win. The next budget summary listed staffing needs alongside equipment costs. It was harder to advertise. It was easier to trust.
May you like
"Which option can people challenge when something goes wrong?"
The engineer smiled. "That needs to be part of the evaluation, too."