Public Beta
Home About

Toronto 2.0

Your city runs on code. Zoning bylaws, transit policy, parking minimums — thousands of rules shaping every moment of your day. Most of them, you've never seen.

Tell us a story. We'll show you the code behind it.

Somewhere in Toronto's thousands of bylaws, zoning codes, and policies, there's a line that explains why your commute doesn't work. Why that corner has been empty for years. Why you can't afford to live near where you grew up.

We say "Toronto is broken" but we can never point to what, exactly, is broken. The rules that shape this city are buried in documents nobody reads, written in language nobody speaks, passed in meetings nobody attends.

Toronto 2.0 is a project to explore that. You tell us a story, something that frustrated you, confused you, or cost you time or money and we trace it back to the specific rules that made it happen. We show you the fine print behind your lived experience.

And then we ask: what if we deleted that line? What might be possible?

Story by story, a pattern emerges. And when enough people trace their frustrations back to the same rules, those rules get a lot harder to ignore.

QSo what do you actually do with this?
Right now, it's a public experiment. We publish the traces. People share them. And if enough people start seeing the same lines of code showing up across totally different stories — a parent late to pickup, a restaurant that couldn't open, a cyclist who had no safe route — that becomes a pattern. Patterns become conversations. And conversations that point to specific, named provisions are a lot harder to ignore than vague complaints about "the city."
QIs this a political project?
It's a legibility project. We're not advocating for a party, a candidate, or a policy platform. We're making visible the invisible architecture that shapes your daily life. What you do with that visibility is up to you.
QAre the traces accurate?
They're illustrative, not forensic. City systems are deeply interconnected — we're showing you threads worth pulling, not delivering legal analysis. The point isn't precision. It's that your frustrations aren't random. They're authored. Someone wrote the code. And code can be rewritten.