Chapter 5: Thirty Days

She wrote it at the top of a fresh page the morning after the notice arrived.

Not as a reminder — she did not need reminders, she carried numbers the way she carried floor plans and inspection routes and the precise dimensions of rooms she had walked through once. She wrote it because she wanted it outside her head, visible, fixed on a page where it could not shift or soften. Thirty days was thirty days. It did not become more days if you were careful with it or thought about it correctly. It was a measurement, like the distance across a room, and she treated it the way she treated all measurements: with respect and without sentiment.

She drew a line beneath the number and beneath the line she wrote two columns.

The left column she labeled WHAT I HAVE.

The right column she labeled WHAT I NEED.

What she had:

Seven departure markers with approximate dates, four buildings with confirmed ownership transfer to Meridian Development Group LLC, her own inspection notes from the building — the basement foundation crack, the ceiling damage in 2B, the fire door that would not latch — and Suárez’s official report when it arrived, which she was already treating as a document she possessed because she knew with certainty what it would say. She had the photographs on her school phone. She had Destiny, which was not a data point but was a resource. She had the mapping software and three weeks of practice using it.

What she needed:

Evidence that the fabrication was systematic and not an isolated error. Evidence connecting Meridian to the departures, not just to the property acquisitions. Evidence that the pattern extended beyond her building. And she needed all of this in a form that adults in a formal setting could look at and not dismiss, which meant it needed to be organized and sourced and layered and clear — it needed to be, she thought, undeniable in the specific way that a map is undeniable, because a map does not argue, it simply shows.

She looked at the two columns for a while.

Then she opened the laptop.

She had been meticulous before. Now she was meticulous and fast, which was a different thing — not sloppiness accelerating, but precision with urgency behind it, the way a surgeon works differently in an emergency than in a scheduled procedure but does not become less a surgeon. She had heard her father use this distinction once, talking about a landscaping job where weather had shortened the window. You work faster but you don’t work worse, he had said. Faster and worse is just panic with a shovel.

She thought about this while she worked.

The base layer was already built — the neighborhood to scale, every building plotted at its correct dimensions. She opened it now and looked at it with fresh eyes, the way she looked at a space she knew well when she needed to see it as a stranger would. A stranger looking at this map would see a residential neighborhood, eight blocks, the standard density of Miami’s older inner-ring development. They would not see what she saw. She needed to build the map until what she saw was what they saw.

She created a new layer and labeled it TIMELINE.

This was the layer she had not built yet — not just where things had happened but when, laid out so that the sequence was visible. She went through the notebook and entered each departure with its date and building, but she also entered the ownership transfers — she had the dates from the county records — and she entered them in a different color so that the sequence showed: Meridian acquires the building, then the inspections, then the families leave. She entered these for all four buildings. The sequence was identical across all four. Acquisition first. Then pressure. Then vacancy.

She looked at the timeline layer.

Even without the inspection data — Suárez’s official reports, which she did not yet have for most of the buildings — the sequence itself was a shape. A shape that repeated. A shape that did not happen by accident four times in fourteen months.