How AI could help Ottawa
1.physical realities - physics,
2.human incentives,
3.power dynamics, and
4.institutionalized systems
Rooted in energy, biology, evolution, and social organization, our modern way of life depends on solar energy and these four key materials:
Climate is where the gap between promises and money is easiest to see in Ottawa, but it isn't the only place. Housing, transit, affordability, garbage, and infrastructure follow the same pattern: stated goals, real needs, and budgets that don't line up. Here is where AI could help in each, and where it can't.
The problem isn't a shortage of plans
Ottawa has declared a climate emergency, approved the Climate Change Master Plan, and adopted Energy Evolution, a detailed strategy for cutting emissions. On paper, we have a mandate. In the budget, the picture is different.
Energy Evolution's own financial modelling put the cost of reaching the city's targets at roughly $621 million a year, a figure advocacy groups like Ecology Ottawa have highlighted for years. Meanwhile, the City Auditor General found that the plan's priorities were funded mainly through static operating budgets and Hydro Ottawa dividend surplus, in years when a surplus existed. It wasn't until Budget 2023 that council approved $5 million in annual dedicated funding. Against the modelled need, that's well under one percent.
A declaration shows intent. A budget shows commitment. Residents deserve to know the difference, and right now it's hard to see.
What AI can and can't do
I've been thinking about this through four forces that shape how any society works: human incentives, physical limits, institutional systems, and power dynamics. AI is strongest on the information side of that picture. It can process far more data than any planning office, forecast demand and failures, and test thousands of policy options before anyone is affected by them.
It is weakest where the real fights happen. AI can calculate the best route to a goal, but it cannot choose the goal. It cannot make councillors fund a plan, and it cannot manufacture legitimacy. If the objectives are set quietly by whoever builds or buys the system, AI becomes one more concentration of power rather than a check on it.
So the right role is advisor, not ruler: better analysis feeding decisions that humans make, in public, and remain accountable for.
Start small, start local
Big global optimization is a fantasy. Pilots are not. Ottawa is a good place to try one: about a million residents, and a city government that directly controls transit, roads, waste, water, building permits, planning, and a city-owned utility. Errors stay local, results can be compared against past years or similar cities, and residents can see what's happening.
The best starting domains have measurable outcomes and little value conflict:
- Winter operations. Smarter routing and forecasting for plowing, salting, and maintenance can cut cost and environmental harm together.
- Buildings and energy. Ranking which retrofits cut the most emissions per dollar, and managing peak demand as heating electrifies.
- Transit and traffic. Signal timing, scheduling, and reliability. This is the most visible domain and the most politically sensitive, which is exactly why it would be a meaningful test.
- Waste and water. Collection routing, stormwater and flood risk, and sewer overflows into our rivers.
Contested areas like taxation, policing, and welfare eligibility can wait. They embed the hardest value judgments and shouldn't be where we learn.
Housing
Ottawa's Official Plan aims for 20 per cent of new homes to be affordable, yet the city's 2023 progress report counted 12,447 households on the centralized wait list at year's end. The mayor has said close to 3,000 people experience homelessness on a given night, and that the 2026 budget added $23.25 million in affordable housing capital. In April, the city announced a partnership with Build Canada Homes aiming for 3,000 new homes, 800 of them affordable.
AI can help by tracking every application from submission to occupancy so delays show up where they happen, forecasting which neighbourhoods will need homes, schools, and transit as they grow, and matching waiting households to units faster. It can't change what drives cost: fees, financing, construction prices, and provincial and federal decisions. It also shouldn't decide who deserves housing. It can flag delays and gaps, and people decide.
Transit
In June, OC Transpo staff reported that weekday peak on-time performance on routes with corrected schedules rose from between 34 and 70 per cent last fall to between 73 and 86 per cent this spring. Nothing exotic was involved: schedules were rebuilt around how long trips actually take. Line 1 returned to double-car weekday service on June 8, while trial running of the East Extension still depends on more rail vehicles becoming available.
That's the model for AI in transit: use passenger counts and vehicle location data to set realistic schedules, forecast demand, and catch equipment problems before they become failures. The city has ordered bearing monitors for Line 1 for exactly that reason. AI can't conjure trains or buses, and weekend reliability is still weaker. Trust also depends on consistent reporting. Some observers have complained that the way performance is measured keeps changing, which makes comparison over time hard. Public metrics with fixed definitions matter more than any model.
Affordability
Council approved the 2026 budget 21 to 4: a 3.75 per cent property tax increase (about $166 on the average bill), a 2.5 per cent transit fare increase, and higher water, stormwater, garbage, and recreation charges. Each item is debated separately. Residents feel them together.
AI could model the combined effect on different households: a renter near the O-Train, a senior on a fixed income in an older suburb, a family in the rural wards. Councillors would see who is hit hardest before the vote and could test alternatives, such as income-based fee relief. It could also help identify residents who qualify for city programs they aren't using. The limit is that most of what makes Ottawa unaffordable, including rent, groceries, energy, and wages, sits outside city control, so the municipal share should be measured honestly rather than oversold. Household-level analysis should use aggregated or anonymized data, never profiles of individuals.
Landfill and waste
Trail Road, the city's only municipal landfill, is projected to fill sometime between about 2034 and 2038, depending on the report and its assumptions. Staff have weighed a private landfill, an incinerator, and a new landfill, and the city has estimated that a new landfill could cost about $591 million if needed in 2034. In January 2026 the city announced plans to buy a private landfill, the Capital Region Resource Recovery Centre, for $95 million plus taxes and closing costs. The waste plan aims to stretch Trail Road toward 2049 through diversion.
This is a problem built for modelling. AI can forecast tonnage by neighbourhood, test how much each diversion measure (the three-item garbage limit, weekly green bin pickup, the ban on commercial waste) really extends the landfill, and price the cost of delay against private disposal rates. It can optimize collection routes and flag contaminated green bins. It can't decide where a landfill or incinerator goes. That is a fight over who hosts the burden, and it needs open debate.
Infrastructure
City staff estimate that the tax-supported assets would cost more than $39 billion to replace, and that renewing and maintaining them takes about $479.7 million a year. That leaves a gap of roughly $229.1 million a year, even after infrastructure capital spending rose from $152.4 million in 2017 to $331 million in the 2026 budget. Staff have floated an infrastructure levy, and a one per cent levy would add about $46 a year to the average property tax bill.
AI's job here is prioritization. Models fed with pipe age, break history, traffic, soil conditions, and inspection images can rank which water mains, roads, and facilities to repair first, and show what waiting costs. They can't create the money, and they're only as good as the asset data behind them. But a public ranked list with the cost of each deferral attached would make it harder to push the bill onto the next term of council.
Make the gap visible
The most valuable thing a decision-support system could do for Ottawa may not be optimization at all. It could be reconciliation: a public, regularly updated accounting that connects each budget line to its expected effect on the outcomes residents care about, such as emissions, housing, reliability, and repair backlogs, and compares stated targets with what has actually been funded.
If a budget adds a few hundred thousand dollars for climate action and tens of millions for road expansion, residents and councillors should be able to see what each choice does to the city's targets, in plain terms, before the vote. Empty declarations are much harder to sustain when the arithmetic is public.
Guardrails that make it trustworthy
Technology projects have burned public trust before, in Ottawa and elsewhere. Any pilot should come with conditions set in advance:
- Published objectives and constraints. State the goals openly: better for people, better for the planet, sustainable over time. Set floors that no outcome can fall below, rather than hiding tradeoffs inside a single score.
- Independent evaluation. A university or outside body judges results, not the operators.
- Pre-registered metrics. Decide what success means before the pilot starts, and measure dollars committed and emissions reduced rather than plans adopted.
- Advisory first. The system recommends, staff and council decide, and authority expands only where trust is earned.
- A human override and an exit. The community can pause or reverse the pilot.
- Open data and open reporting. Residents can see what was recommended and what was done.
The limits
I don't want to oversell this. Ottawa's jurisdiction is divided: the province controls health, education, and much housing and transit funding, and the federal government and the NCC hold major land and facilities. Ottawa and Gatineau form a single commuter region split across two provinces, so a city-only view misses real flows. A city can also look greener by pushing costs outward, so metrics have to capture the wider region. And ward-based politics can override any system-wide recommendation.
The deepest limit is political will. Better analysis does nothing if its recommendations go unfunded, the same way Energy Evolution has been underfunded since it was approved.
What I'd ask for
- A dedicated, stable funding source for climate action, not one that depends on a surplus.
- A public budget-to-emissions reconciliation published alongside every budget.
- One well-scoped, independently evaluated AI-assisted pilot in a domain where money already flows, such as winter operations or building retrofits.
- Clear public rules on data, objectives, and oversight before any system is switched on.
Beyond climate, the same test applies to every area above: publish the objective, the baseline, and the funded action, then report back every year using the same measure.
AI will not fix Ottawa's problems by itself. Used honestly, it can do something just as useful: make it much harder to say one thing and fund another.
Sources
Figures below come from search results and should be checked against the original documents before publishing.
- Climate: Auditor General audit of the Climate Change Master Plan; Ecology Ottawa on Energy Evolution funding
- Housing: City of Ottawa 2023 Housing and Homelessness progress report; Affordable Housing CIP; Capital Current on 2026 housing investment; Build Canada Homes partnership release
- Transit: OC Transpo update to Transit Committee, June 11, 2026; OC Transpo committee recap; O-Transit blog on the June meeting
- Affordability: CTV on the approved 2026 budget
- Landfill: CTV on the waste plan and 2049 target; CBC on options to replace Trail Road; Landfill acquisition announcement
- Infrastructure: CTV on staff's infrastructure levy proposal
Comparing Project Cybersyn to AI Decision Support in Ottawa City Government
Structural lessons from Stafford Beer’s 1971–1973 Chilean experiment for municipal AI design
Yes — the comparison is productive, though the differences in scale, politics, and theoretical ambition matter as much as the similarities.
What Cybersyn Was
Project Cybersyn (Synco in Chile) was Stafford Beer’s 1971–1973 experiment, under Salvador Allende, to manage Chile’s expanding nationalized industrial sector with cybernetic principles rather than Soviet-style command planning. It rested on Beer’s Viable System Model (VSM): a recursive structure in which every level (factory, branch, sector, national) is itself a viable system containing the same five functional subsystems:
- System 1: primary operations
- System 2: coordination among them
- System 3: internal optimization and resource bargains (with occasional audit)
- System 4: outward/future intelligence and adaptation
- System 5: policy, identity, and resolution of tensions between “here and now” and “there and then”
Data flowed via a national telex network from factories (output, materials, absenteeism, etc.). Cyberstride software filtered for anomalies and short-term forecasts. An economic simulator and a purpose-designed Operations Room (with visual displays, shared controls, and no hierarchical seating) supported decision-making. The critical design principle was algedonic signaling: lower levels retained autonomy and were expected to solve their own problems; only if they failed within an agreed time window did an alert escalate upward. Beer’s explicit goal was to increase worker autonomy and self-regulation while managing the complexity of the whole, not to centralize command. The network showed practical value during the 1972 truckers’ strike by helping coordinate alternative logistics. The 1973 coup ended it before full-scale operation.
Overlaps with the Ottawa Hypothesis
Both treat governance as a problem of handling complexity through timely information and feedback rather than pure hierarchy or pure localism. Both emphasize decision support over automated rule. Both prioritize domains with measurable operational indicators (factory performance indices vs. plow routes, transit reliability, landfill tonnage, asset condition, emissions-per-dollar). Both value shared visualization so that decision-makers can see the state of the system (Ops Room vs. public budget-to-outcomes reconciliation, Digital Twin scenarios, fixed-metric dashboards). Both recognize that raw data volume must be filtered to the significant deviations, and that technology alone cannot set goals or manufacture legitimacy.
Karwacki’s four forces (physical realities, human incentives, power dynamics, institutionalized systems) map roughly onto VSM concerns: System 1 and the environment for physical and operational realities; Systems 2–3 for coordination and incentives inside the organization; Systems 4–5 for adaptation and the identity/policy choices that power dynamics ultimately decide.
Important Differences
- Scale and purpose: Cybersyn targeted real-time coordination of a nationalized economy during a deliberate transition to democratic socialism, with worker participation as a design objective. The Ottawa proposal is municipal service management and transparency inside existing liberal-democratic institutions.
- Theoretical depth: Cybersyn was built around explicit variety engineering, recursion, and exception-based escalation. Most current municipal AI is optimization, forecasting, or productivity tooling without a comparable theory of distributed autonomy.
- Technology and institutional context: Telex + mainframe + statistical filters versus contemporary ML, optimization solvers, digital twins, and sensors. Cybersyn was politically central to Allende’s project and vulnerable to its overthrow; Ottawa AI would sit inside ordinary procurement, staff workflows, and council politics.
- Power: Beer designed against bureaucratic centralization and Soviet models. The risk he and later observers noted — that the information system could still be used for coercive control — remains relevant. Modern AI systems can concentrate power in whoever sets objectives, chooses data, or owns the models even when labeled “advisory.”
Useful Extensions for the Ottawa Idea
The strongest lessons to import are structural rather than technological:
- Exception-based escalation over continuous central optimization. Design the system so that operational units (plow crews, depots, permit teams, district offices) receive timely local signals and retain decision rights. Higher levels (and the public dashboard) see primarily deviations from pre-registered targets or agreed response times — the algedonic principle. This preserves autonomy and reduces the “AI as ruler” problem Karwacki flags.
- Recursive viability. Treat city systems as nested viable systems (route crew → depot → division → department → council/public). Each level needs its own metrics, local adaptation capacity, and clear rules for when escalation is required. The Digital Twin and existing asset data can support this without inventing a new national architecture.
- Shared, non-hierarchical visualization. The Ops Room’s emphasis on common visual ground for decision-makers translates into collaborative dashboards, public reconciliation reports, and Digital Twin scenarios that councillors, staff, and residents can inspect together. Pre-registered metrics and open reporting of recommendations versus decisions serve a similar function to the visual filtering of significant signals.
- Amplify local variety, don’t only attenuate it centrally. Beer’s cybernetics stressed that lower levels must have sufficient variety (capacity) to handle their local environment. AI tools that help crews optimize salt application in real time, or that surface permit bottlenecks to the teams that can fix them, fit this better than pure central ranking models.
- System 5 remains human and political. AI can surface the arithmetic between stated targets (Energy Evolution, housing goals, reliability standards) and funded action, but it cannot choose the identity or resolve value conflicts. Cybersyn’s designers were clear that policy and purpose sat outside the technical system; the same limit applies in Ottawa. Public arithmetic raises the cost of sustained mismatch but does not eliminate political will as the binding constraint.
Cybersyn demonstrated both the power of near-real-time operational coordination and its fragility to political rupture. The Ottawa hypothesis already correctly treats AI as an advisor that makes gaps harder to hide. Borrowing the VSM’s recursive autonomy and exception logic would make that advisory role more robust against both under-use and over-centralization, without requiring the revolutionary political project that accompanied the Chilean experiment.
This document compares Stafford Beer’s Project Cybersyn (Chile, 1971–1973) with the hypothesis on AI decision support in Ottawa city government articulated by Peter Karwacki. Content is based on publicly available historical accounts of Cybersyn and the provided analysis of municipal AI applications.
** The hypothesis is solid on the core framing—AI as an information and analysis layer that strengthens the advisor role without pretending to resolve value conflicts, funding choices, or power dynamics—and on the practical starting points (measurable domains with existing money flows). It can be extended usefully by anchoring it in what Ottawa already has, specifying higher-leverage pilots with real analogs, and tightening the transparency and governance mechanisms so they actually constrain the “say one thing, fund another” problem.
### Anchor in Ottawa’s existing foundation Ottawa is not starting from zero. It has an operational Digital Twin (3D model with zoning, roads, subsurface utilities, development applications, and growing real-time/field data), which already supports scenario modeling, zoning analysis, asset cataloguing via machine learning on imagery, and planning tools. Staff are using Microsoft Copilot at scale, AI is being applied to resume screening and mapping footage analysis, and an Archistar AI PreCheck pilot is aimed at residential permitting completeness and compliance. The City is developing a responsible AI framework (governance, privacy, structures) targeted for 2026. These are the right substrates: the Digital Twin for spatial/asset context and simulation, operational systems for routing and maintenance data, and emerging governance for guardrails.[](
Layering decision-support AI on top of this is more realistic and lower-risk than greenfield systems. It also creates a natural audit trail: recommendations can be visualized against the twin and compared to actual decisions and outcomes.
### Sharpen the high-value pilots **Winter operations** remains one of the strongest first pilots. Cities are already combining GPS/location data, weather, traffic, and optimization for routing, salt/brine application, and signal priority for plows. Examples include Syracuse (GPS + video + AI reducing complaint calls ~30% while improving situational awareness and public maps), systems that optimize salt based on real-time conditions, and signal prioritization approaches that reduce stops and fuel use. Optimization solvers can treat constraints (priority streets, salt capacity/reloads, driver rules, legal turns) while minimizing total time or salt. Ottawa can start with one district or storm type, feed results into the Digital Twin for asset-condition context, and pre-register metrics: salt use per km or storm, clearance times for priority routes, complaint volume, fuel/cost, and emissions-relevant proxies. Benefits compound with environmental goals (less salt) and operational efficiency; failures stay local and reversible.[](
**Infrastructure prioritization and predictive maintenance** map directly onto the identified gap (tax-supported assets replacement value >$39B, annual renewal need ~$480M, multi-hundred-million gap). Machine-learning models on pipe age, break history, soil, traffic, and inspection imagery (already partially supported by the twin and mobile mapping) can rank assets and attach explicit cost-of-deferral figures. Transit fleets offer a clear Canadian analog: Saskatoon Transit’s AI predictive maintenance (sensor data + models) produced early reductions in labour hours, parts costs, and unscheduled work, with improved reliability and awards for the approach. A public ranked list with deferral costs makes the political cost of delay more visible across budget cycles.[](
**Budget-to-outcomes reconciliation** is the highest-leverage transparency play. An analytics or carefully constrained LLM-assisted layer can parse budget lines, map them to pre-registered outcome metrics (emissions trajectories relative to Energy Evolution modelling, housing units or wait-list movement, transit on-time performance with fixed definitions, landfill life extension, infrastructure backlog), and surface the arithmetic before votes. This is weaker on pure optimization and stronger on making underfunding or misalignment harder to obscure. Household-level distributional effects (different wards, income, tenure) can use aggregated/anonymized data. Independent evaluation (university or external body) and open reporting of recommendations versus decisions are essential.
Other domains (waste routing and contamination flagging, building retrofit ranking by emissions-per-dollar, transit scheduling from actual run times and ridership) follow the same pattern: measurable outcomes, limited immediate value conflict, existing data flows. Contested areas (taxation structure, eligibility rules) stay deferred until trust and methods are proven.
### Technical and methodological extensions - Optimization and simulation engines for routing, scheduling, and scenario testing, grounded in the Digital Twin. - Predictive models for failure and demand (maintenance, peak energy, flood/stormwater risk). - Multi-criteria decision analysis with auditable/explainable components (including LLM-assisted extraction of expert judgement into structured weights, with human review) so trade-offs are explicit rather than buried in a single score. - Fixed, pre-registered metrics decided before the pilot; independent evaluation; public dashboards of recommendations, actuals, and variances. - Open or publicly reported data layers where privacy allows, so residents and councillors can inspect the arithmetic.
Canadian municipal practice is already moving in practical directions: permit pre-screening and chatbots (multiple cities), predictive transit maintenance, road/asset assessment via imagery, and internal productivity tools. Roughly a quarter of Canadian municipalities report using AI, with many more exploring; priorities centre on efficiency, citizen service, and cybersecurity. Partnership models (e.g., with institutes such as Vector, or local capacity at Carleton/uOttawa) reduce pure vendor dependency.[](
### Governance, incentives, and limits The four forces (physical realities, human incentives, power dynamics, institutionalized systems) remain the binding constraints. AI improves the information available to those forces; it does not rewrite them. Guardrails from the original post are right and can be sharpened: published objectives and floors, independent evaluation, pre-registered metrics (dollars, outcomes, not plans), advisory-only with human override and exit, open reporting. Align explicitly with the City’s forthcoming AI framework. Data quality in the twin and legacy systems, model drift, procurement capture, and equity in who benefits or is burdened are real risks—mitigate with auditability, external review, and impact monitoring by geography/demographics rather than individual profiles.
Jurisdiction limits (provincial/federal/NCC roles, Ottawa–Gatineau flows) and political will remain decisive. Better models that go unfunded change little, as the Energy Evolution funding gap illustrates. The transparency layer is therefore not secondary; it is the mechanism that raises the cost of sustained mismatch between targets and budgets. Ward-level politics can still override system recommendations, which is why public arithmetic and fixed metrics matter.
### Practical extension A coherent next step is one well-scoped, independently evaluated pilot (winter operations or retrofit prioritization) with pre-registered metrics, Digital Twin integration, and a parallel public budget-to-outcomes dashboard for the same domain. Stable dedicated climate/infrastructure funding and open reporting rules are the complementary political asks. Results from the pilot and dashboard then inform whether and how to expand.
This stays within the advisor role, starts local and measurable, exploits assets Ottawa already owns, and treats the visibility of gaps as a primary deliverable rather than an afterthought. It does not solve political will, material constraints, or value conflicts—those remain human and institutional—but it can make the arithmetic and the trade-offs harder to ignore.

No comments:
Post a Comment