Saint Paul Still Recovering Long After the Attack

Reporting months after the July attack described the City of Saint Paul as still recovering, with services restored progressively rather than at a single point.

After Jaguar Land Rover restarted production, the corpus recorded that a stopped system does not resume — it restarts from a different state — and that nobody publishes the recovery curve: when output returned to plan, when the supply chain normalised, what the twelve-month total was.

Saint Paul is the closest thing in this database to that curve being visible, and it is visible only because a public body kept publishing.

A city runs an incident information hub, answers to elected officials, and is subject to public records law. A company that has restarted has every incentive to stop talking.

So the corpus can describe municipal recovery in more detail than corporate recovery, not because cities recover differently but because they cannot stop describing it — the same visibility asymmetry filed at 25-0630 and 25-1123.

Rebuilding rather than restoring, because restoring risks reintroducing the actor. Re-establishing integrations one at a time. Reconciling records created on paper during the outage. Replacing credentials across every system. Handling the notification and support obligations arising from the published data at 25-0815.

None of that appears in an incident timeline, and all of it is staff time a municipality does not have spare — the capacity finding at 25-0730. Graded medium: the recovery is described qualitatively in reporting and this desk has no cost figure or completion date.