An obvious solution for reducing developer influence:
If an executive or family member of the developer gives a campaign contribution to a council member that council member may not vote on files involving that development.
It is an obvious solution for reducing developer influence on council members. The way things are going you might end up with only with one councillor voting.
Those signs that pop up each election do not come cheap.
If you want to get money out of politics you have to vote the right people into office! Make the kind of structural "right turn" Ottawa needs to get out of its present morass.
This time around, inform yourselves, vote differently, vote wisely. Vote for Peter Karwacki for Rideau Rockcliffe.



Grok may be one of the few paying attention
ReplyDeleteYour recent posts on peterkarwacki.blogspot.com (especially the cluster from early August 2026) read as focused, practical campaign writing for the Rideau-Rockcliffe (Ward 13) race: emphasis on accountability, measurable oversight, transit fixes, and structural changes rather than pure personality or event-hosting.
The very latest ones (dated around August 5–6) lean heavily into transit and influence reform:
“On the Take” proposes a straightforward rule: if a developer (or family member) contributes to a councillor’s campaign, that councillor sits out votes on that developer’s files. It’s framed as a structural way to reduce influence, noting the cost of election signs and the risk of leaving few people able to vote. Clear, pointed, and consistent with your broader critique of closed-door big-ticket decisions.
The autonomous-shuttle and bus-service posts are among the strongest recent material. You map specific corridors (Wateridge Village to St-Laurent/Tremblay, Aviation Parkway loops serving Manor Park/NRC/CSIS/Train Yards, Beechwood–Hemlock frequency, Montfort/La Cité circular, McArthur–Hurdman connector). You outline phased Level 4 automated feeders with onboard attendants initially, cite Ottawa’s existing test ecosystem (Area X.O, Kanata North, Tunney’s Pasture), and argue for cost and frequency gains from reducing driver hours while improving first/last-mile links to Line 1. These read as concrete, locally grounded proposals rather than vague futurism.
Supporting pieces give route inventories for the ward’s neighborhoods and a Chinese-language “remember to vote” post that stresses oversight of large budgets and past issues (LRT, landfill pricing, police reporting) over popularity. The bilingualism/“Oh Canada” post notes the ward’s French-speaking population share and calls for practical support of Francophone vitality.
Across the recent output (and the June–July posts that feed into it), recurring themes are consistent: demand for open, readable data instead of FOIA hurdles for basic metrics (road conditions, sidewalk gaps, capital-plan details); skepticism of major capital decisions that surface or escalate after elections (landfill, Lansdowne, library overruns, hospital share); preference for competence and measurement over event-hosting; and specific local asks (road/sidewalk quality, noise, truck routing, park animation, sensible washrooms). You repeatedly contrast a project-manager/administrator skill set with the incumbent style and end most pieces with the same call to “inform yourselves, vote differently, vote wisely.”
Strengths: The writing is earnest and specific where it counts. The transit proposals show homework—named corridors, headway targets, phased rollout, and ties to local testing capacity. The open-data and externalities arguments (e.g., deferred sewer work hitting home values) treat residents as people who deserve the scorecard, not just the construction estimate. Framing the race as oversight vs. popularity is a coherent differentiator. Your PMP/hospital-admin background is invoked in ways that match the content.
Limitations / style notes: Posts are often informal and sometimes contain typos or awkward phrasing (“seperation,” “afgordable,” occasional run-ons). The global/macro pieces (oil, debt, energy density) sit somewhat awkwardly next to ward-level transit lists; they broaden the frame but can dilute the local focus. Every post ends with the vote ask, which is standard campaign practice but becomes repetitive. Earlier material on housing concentration and related social issues uses language that some readers will find blunt or polarizing. Engagement (comments) appears low on most entries.
Overall, the recent posts project a challenger who prioritizes measurable management, transparency, and concrete neighborhood connectivity fixes over soft community outreach. They are coherent with a project-management lens applied to municipal government. Whether that resonates depends on voters who want that style of scrutiny; the writing itself is direct about the trade-offs it is asking people to consider.
ReplyDelete