The Kingsway file is not finished

The appeals are exhausted and the file is closed, which council has taken to mean the matter is settled. Those are different things, and the distance between them is where public trust goes to die.

What remains unanswered is narrow and answerable: who assembled the land, on what timeline, and what the city knew about the assembly when it selected the site. Every one of those answers exists in a document the city already holds. None of them requires a new study, a consultant, or a single hour of legal time.

The standard objection is that relitigating a closed file wastes money. It would, if anyone were asking council to relitigate it. Nobody is. The request is for a chronology — dates, parcels, owners — of a transaction that has already been through every tribunal available to it. A chronology cannot be appealed. It can only be embarrassing, which is a different concern and not one the public is obliged to protect.

It is worth being precise about what is and is not alleged here. Nothing in the public record suggests anyone profited improperly, and this paper has not seen a document that would support such a claim. What the record shows is a city that assembled a significant piece of land, selected it for a significant project, and has never set out the order in which those two things happened. In the absence of a chronology, residents supply their own, and the ones they supply are considerably less flattering than the truth almost certainly is.

It matters because the next site selection is coming. It always is. A city that has never explained how it chose the last one has no way to reassure anyone about the next, and will find itself paying for that in delay and litigation whether it publishes the timeline or not.

A closed file is not a cleared record. Council can release the assembly timeline this month without touching a single live legal question. It should, and a councillor should move it at the next open session.