Edmonton's bike routes and the August 2026 committee vote
Did council pause the future bike routes when its own administration recommended it?
No. In the records we checked, council did not pause the routes. Its Infrastructure Committee neither adopted nor rejected administration's plan to set 14 bike routes aside, and the Council records we read show no decision on it by September 25.
TL;DR
- A committee motion to keep building the routes as planned failed on a 2 to 2 tie, so the committee decided nothing on the plan either way.
- A councillor has since asked Council to look at more money for the 14 routes, and Council put that motion off to October 6.
- The City's original plan would have dropped 14 bike routes for 2026 and 2027, but its latest version only proposed another look at them.
- Council voted down both bike-lane cuts Councillors Karen Principe and Jennifer Rice brought, and only one would have left $50 million of the $100 million approved in 2022.
- We have not answered whether the same seven councillors always backed Edmonton's bike-route program.
- Part holds; as stated it overreaches.More in the methodology
Partly. Council's Infrastructure Committee neither adopted nor voted down administration's plan for 14 bike routes, and full Council had not decided it by September 25 in the records the reviewers read.
Did Edmonton's administration recommend freezing 14 future bike routes to reassess them?
Part holds; as stated it overreaches.More in the methodologyPartly. Administration's original plan would have taken 14 bike routes out of the program for 2026 and 2027, but its latest only set them aside without saying they would wait. Its middle version held them back too.
- Part holds; as stated it overreaches.More in the methodology
Partly. Councillors Karen Principe and Jennifer Rice brought two cuts to Edmonton's bike-lane budget and council voted both down, but only one would have left about $50 million.
Verdicts by a Three AI model seats from two vendors: one Anthropic model and two OpenAI models. The two OpenAI seats are not independent of each other, so three agreeing verdicts are not three independent confirmations.More in the methodology under a A fixed synthesis rule, published in advance, turns the three verdicts into one finding word, so no person chooses the finding. The rule and every change to it are versioned in the methodology changelog.More in the methodology · The date the accounting window closes. Anything that happened after it is outside this check, and the date is fixed in the brief before any model runs.More in the methodology · The date we last re-read the cited sources and confirmed the page still matches them. It is not a claim that the records themselves changed.More in the methodology · When this is due for a fresh check of its sources. Past that date, treat it as unverified until it has been re-reviewed.More in the methodology · The version of the published method that produced these findings. Every change to the prompts, the merge and synthesis rules, the vocabulary or the validation bumps it.See what changed
What actually happened
The day after Edmonton’s Infrastructure Committee met on the bike-lane program on August 26, 2026, six people under one Facebook post made claims about what administration had proposed and what council did with it. One comment, by Amber Owl J., carries three of the four claims on this page.
Five of the six said council had not supported the review, had ignored it, or had passed up a second look. Amber Owl J. wrote that administration had recommended “freezing 14 future routes to reassess”, and that she and Councillor Karen Principe had twice brought motions to cut the bike-lane money to $50 million, and lost. One person said the same seven councillors voted for the program.
Three of the claims are checked against the City’s own report and council minutes, and each gets its own finding. The fourth was set aside and has none. The checks were made by a panel of three AI models, called the reviewers below, under rules fixed before they started. Why anyone voted as they did is not checked. Nor is whether the routes should be built.
What administration asked for
Report IS03688 went to the Infrastructure Committee on August 26, 2026. It asked the committee to recommend that City Council approve an updated approach for the program’s remaining routes, set out in the report’s Attachment 5. It gave two reasons. The provincial government was expected to change cities’ authority over bike lanes. And residents were complaining more about the trade-offs, such as lost parking. It said the change would not alter the program’s capital budget or its borrowing.
Attachment 5 came in three versions, all on the committee’s agenda. The City labelled the two replacements Version 1 and Version 2. All three split the same routes into two lists. Thirteen projects would continue as planned. Fourteen were set apart. The City’s route status table, dated August 10, 2026, describes them this way. Three had a contract awarded and no work started. Six had been scheduled for 2026, but installing them that year was “no longer viable”. Five had no delivery plan or schedule. For those five the table does not say in so many words whether work had started.
What would happen to the 14 is where the versions differ. The original said that if Council approved the change, they “would be removed from the scope” of the program for 2026 and 2027, and might be revisited later. Version 1 dropped that sentence but kept a rule that routes not yet built “would be evaluated to determine if they should proceed”. Version 2 says the remaining routes “will be evaluated for trade-offs, alternative design treatments and budget implications”, and that administration will report to Council in the first three months of 2027 for direction. It says the 14 “may be re-evaluated using alternate design approaches”.
So the finding on whether administration recommended a freeze depends on the version. Under the original it did, and in cross-review all three reviewers read Version 1 as holding the routes back too. Under Version 2, the latest, it recommended taking another look and reporting back, and did not say the routes would wait. The committee’s minutes add both replacements without saying which one members had in front of them, so this check reads Version 2 and the finding is Partially supported.
The report comes close to a freeze in other places. It says that because of the weather, construction not yet started is “best postponed to 2027”, though that covers every unstarted route, including those continuing as planned. The status table says the three tendered routes “may be delayed” or removed pending the Council report. Read together, these suggest the 14 would wait for Council. Before any research, this check decided that a freeze needs the plan’s own words to say the routes wait. No passage tied to Version 2 says the 14 must wait. One reviewer called it a close call.
What the committee did
The Infrastructure Committee has six members, the mayor among them. Seven other councillors attended. No member moved to adopt the recommendation.
Councillor A. Salvador moved instead that administration keep building within the program’s approved scope, push ahead with routes ready to tender, and get routes that could not go ahead in 2026 ready to build at the earliest chance in 2027. Councillor E. Rutherford moved to take out the part about making the most of the 2026 construction season. Both were defeated 2 to 2. Salvador and M. Janz voted for the main motion, and Rutherford and R. Clarke against. On the amendment the votes were the other way round. Mayor A. Knack and Councillor A. Paquette are recorded on neither vote, and the minutes do not say why.
So the committee neither adopted the plan nor turned it down. That is why the finding is Partially supported. The plan was not adopted. What the minutes do not show is the committee voting it down or voting to carry on against it, which is what “ignore” and “go their own route” describe. If “did not support” means only that the plan was not adopted, the claim holds.
A committee is not City Council. The report asked the committee to send the plan to Council with a recommendation, and the committee carried no motion on it. Nothing in the Council minutes the reviewers read decided it by the cut-off date of September 25. Those were chosen items from the September minutes, not whole meetings, and one reviewer’s look at the City’s open voting record, on September 29, found no Council vote on the report up to September 22. The minutes of Council’s two September public hearings, read here after the panel ran, have no item on it either. Salvador gave notice of a motion asking administration to prepare options for more money to finish the 14 routes in the 2027 to 2030 budget. Council put it off to its meeting of October 6, after this page’s cut-off date. No Council decision overrode the committee, because the committee made no decision on the plan to override.
The two motions to cut the money
Council approved the program in December 2022 at $100 million, by 9 votes to 4, with Principe and Rice, both councillors then, among the four against. Rice sat on Council until the October 2025 election.
In November 2023 Principe moved, and Rice seconded, a cut of $50 million from the program’s 2024 to 2026 funding, with less borrowing to match. Council defeated it 4 to 8. In December 2024 Principe moved, and Rice seconded, a cut of $33.65 million in each of 2025 and 2026, to defund the program’s planning, design and delivery. Council defeated it 4 to 7.
The first would have left $50 million. The second adds up to $67.3 million, which would have left about $32.7 million, about a third. Both remainders are calculations made here, against the $100 million approved in 2022. This site could not open or archive the program’s budget sheet from either date. GPT-6 Sol and GPT-6 Luna cited a September 2024 capital update showing $100 million. Claude Opus 5.5 and GPT-6 Sol got an error when they tried to open it in cross-review, and it is not in our archive. Administration’s August 2026 report still describes the program as $100 million approved in the 2023 to 2026 budget.
So the pair did bring two cuts, and both lost. Only the 2023 one matches the “$50M” in the claim. It is also the only one whose text says where the money would go, toward less borrowing. The 2024 text names the borrowing that funded the program but not where the money taken out would go. Neither text uses the comment’s words “core priorities”.
Three other recorded motions that one or both of them moved or seconded were not votes on cutting the program. A separate 2023 cut that Rice moved, which did not name the program, was withdrawn. In June 2024 the pair moved an amendment on new funding requests that did not name the program, and it lost 2 to 10. In September 2025 Principe seconded a motion to halt construction on bike lanes that had not started until every project was reviewed. It lost 4 to 9.
Why the ‘same seven’ claim is not answered here
One commenter said the same seven councillors voted for the program. This page does not test that, or what the commenter said about their intentions, and nothing above should be read as an answer to it.
A pattern like that shows only across all the votes, in both councils, the one before the October 2025 election and the one after. A single vote, or a list of who voted on one motion above, does not test it. Several budget-adjustment meetings in that period are not in our archive yet. Some budget votes bundle this program with many others, and which way each of those counts depends on documents that are not archived either. Depending on how those votes are counted, the answer could come out as no, as partly, or as nobody can tell. So the claim was set aside before the panel ran. It is listed among the claims with no finding. It can be checked again once those minutes and documents are archived and read.
What this page does not answer
Nothing here says why any member of council voted as they did, or whether the routes should be built, paused or cut. Whether the City consulted residents about the routes is a separate question, and so is how far the routes had got. Who spoke at the committee’s hearing that day, and how it cut their speaking time, is on its own page. Where the $100 million came from, and how it compares with the City’s renewal shortfall, is on another page.
Claims checked
Did council's Infrastructure Committee turn down administration's proposed pause on the remaining bike routes, and did full City Council later decide it?
Part holds; as stated it overreaches.More in the methodology· All three seats reached the same verdict. Panel agreement describes seats, not vendors; two OpenAI seats agreeing are not two independent vendor confirmations.More in the methodology panel
What kind of record answered the question — an audited statement, a council report, a dataset. It is reported apart from the finding, because a claim can be Supported on a thin basis.More in the methodology: Direct Edmonton evidence
- Report IS03688 asked the Infrastructure Committee to recommend to City Council that the updated approach for the remaining routes, as outlined in its Attachment 5, be approved. The report marked this "Council decision required". YF-EV-0118
- In Version 2 of Attachment 5, the latest of its three versions, routes that leave travel lanes and parking alone continue as planned, the remaining routes are to be evaluated for trade-offs, design options and budget, and administration would bring a report to Council in the first quarter of 2027 for direction and approval. It lists 14 projects that may be re-evaluated. YF-EV-0140
- The committee's minutes record no motion to adopt the recommendation, moved or put. YF-EV-0209
- Councillor A. Salvador moved that administration continue the program within its previously approved scope, advance tendering for routes ready to tender and get the rest ready for 2027. It was defeated 2 to 2, with A. Salvador and M. Janz in favour and E. Rutherford and R. Clarke opposed. YF-EV-0209
4 more facts
- Rutherford's amendment to drop the instruction to make the most of the remaining 2026 construction season was also defeated 2 to 2. Mayor A. Knack and Councillor A. Paquette, both committee members, are recorded on neither vote. Apart from two procedural motions to go into and out of a private session, the only motion on the item that carried kept a confidential attachment private, 4 to 0. YF-EV-0209
- At Executive Committee on September 2, 2026, Salvador could not make a pending motion on the program for lack of time and gave notice of it again. At City Council on September 8, that notice, asking administration to prepare options for more money to complete the 14 routes for the 2027 to 2030 budget, was laid over to October 6, 2026. YF-EV-0216, YF-EV-0227
- The City Council agenda for October 6, 2026, as published on September 25, lists Salvador's motion and no item on report IS03688 or its Attachment 5. YF-EV-0221
- The minutes of the Council public hearings of September 15 and 22, 2026 hold no item on report IS03688 or its Attachment 5. The only item on the active transportation network, on September 15, set a new due date for a separate report on updating the network in the City's planning bylaws. YF-EV-0228, YF-EV-0229
Also said as — 5 captured wordings
Quoted exactly from sources we hold. Each name is a pseudonym, one to a person within its source.
That review was also not supported by Council.
Amber Owl J. · in the register · the post
The city’s recommendation was to PAUSE the bike lines until more information was obtained to continue it in a thoughtful way that worked for residents that it affects as well as drivers and bikers. Council chose to ignore that.
Boreal Crow K. · in the register · the post
Typical city council, ignore a committee's decision and go thier own route.
Amber Coyote T. · in the register · the post
They already ignore the citizens, might as well ignore their own committees too.
Snowy Bluejay M. · in the register · the post
The motion was not to scrap the routes, but rather to not rapidly push them through without a second look.
Boreal Marmot L. · in the register · the post
Limitations
- The body that met on August 26, 2026 was the Infrastructure Committee, a committee of Council with six members, not City Council. A committee decision is not a Council decision. This finding is about the committee. For City Council as a whole, the records reviewed show no decision on the recommendation by September 25, 2026, and some Council meetings in that period were not reviewed.
- The finding reads "did not support" strictly, as a choice made, because that is what "ignore" and "go their own route" describe. Read loosely, as the plan simply not being adopted, the claim holds in full.
- No override happened. The committee made no decision on the plan for Council to overturn, and no later Council decision on it appears in the records the reviewers read.
- Which version of Attachment 5 was before the committee is not recorded. This check reads Version 2, the latest, because the record does not say. Under it, what went undecided was a plan to re-evaluate routes and report back, not a hold on them. Under the original version it was a hold, and all three reviewers came to see Version 1 as one too. The finding is the same either way, because the committee decided neither.
- The minutes do not say why the mayor and Councillor Paquette are not recorded on the two votes. Paquette was absent for part of the meeting.
- The reviewers read selected items from the September Council minutes, not every page of every Council meeting up to September 25. The September 15 and 22 public-hearing minutes were not among them. This site read them after the panel ran and found no item on the report. The City's open voting record, checked by one reviewer on September 29, 2026, showed no Council vote on the report through September 22.
- In the records read, the program kept the scope Council approved in December 2022, as later changed for 50 Street by Council on July 7, 2026. The report's own statement that construction not yet started was best postponed to 2027, because of the weather, is administration's assessment and not a Council decision.
Did Edmonton's administration recommend freezing 14 future bike routes to reassess them?
Part holds; as stated it overreaches.More in the methodology· All three seats reached the same verdict. Panel agreement describes seats, not vendors; two OpenAI seats agreeing are not two independent vendor confirmations.More in the methodology panel
What kind of record answered the question — an audited statement, a council report, a dataset. It is reported apart from the finding, because a claim can be Supported on a thin basis.More in the methodology: Direct Edmonton evidence
- Report IS03688, to the Infrastructure Committee on August 26, 2026, recommended that the committee ask City Council to approve the updated approach for the remaining routes set out in its Attachment 5. YF-EV-0118
- Attachment 5 exists in three versions, each listed on the committee's agenda: the original, a replacement marked Version 1 and a replacement marked Version 2. All three name the same 13 projects that would continue as planned and the same 14 set apart. Counting each bulleted entry once gives 14. Three entries each name two or three separate stretches of street, and counting those stretches separately gives 18. YF-EV-0210, YF-EV-0222, YF-EV-0223, YF-EV-0140
- The original version says that if Council approves the change, the 14 "would be removed from the scope of the Active Transportation Network Expansion Program for 2026 and 2027", and may be revisited later. YF-EV-0222
- Version 1 drops that sentence. It keeps a rule that routes not yet built "would be evaluated to determine if they should proceed", with routes that affect travel lanes or parking removed from the program, and says the 14 may be revisited using other designs or future initiatives. YF-EV-0223
5 more facts
- Version 2 says routes whose plans do not affect travel lanes or parking will continue as planned, and "The remaining routes will be evaluated for trade-offs, alternative design treatments and budget implications." In the first quarter of 2027 administration would bring a report for Council direction and approval. It says the 14 "may be re-evaluated using alternate design approaches". YF-EV-0140
- The report says that because of the weather, for routes where construction has not yet started, "construction is best postponed to 2027". That sentence covers every route not yet started, including routes continuing as planned. YF-EV-0118
- The City's route status table, accurate as of August 10, 2026, records three of the 14 as having a contract awarded and construction not yet started. Six were scheduled for 2026, but installing them in 2026 was "no longer viable". Five had no delivery plan or schedule, and the table gives no construction status for them in so many words. YF-EV-0226, YF-EV-0225
- The same table says the three tendered routes "may be delayed (in whole or in part) to 2027 or removed" pending the Council report, and that next steps for the six "will depend on Council's direction". YF-EV-0226
- The report says that approving the recommendation would not change the program's capital budget or its borrowing bylaws. YF-EV-0118
Also said as — 1 captured wording
Quoted exactly from sources we hold. Each name is a pseudonym, one to a person within its source.
Yesterday, City Administration recommended freezing 14 future routes to reassess
Amber Owl J. · in the register · the post
Limitations
- The finding depends on the version. The committee's minutes add Version 1 and Version 2 as replacements without saying which was before members, so this check reads Version 2, the latest. Read on its own words, Version 2 does not say the 14 routes wait for the evaluation or the 2027 report, so it does not meet the test of a freeze. The original version, which took the 14 out of the program for 2026 and 2027, would meet it. In cross-review all three reviewers said Version 1 would meet it too, because under it proceeding waits on the evaluation.
- On Version 1 the reviewers first disagreed. Claude Opus 5.5 read its rule, that routes not yet built would be evaluated to decide whether they should proceed, as a freeze from the start. GPT-6 Sol and GPT-6 Luna first read it as falling short, and in cross-review both agreed it met the test. GPT-6 Luna still would not call the claim Supported under Version 1, because the construction status of five routes is unresolved.
- "Freeze" was fixed before the research as a plan that says, in its own text, that the routes wait for a further evaluation, report or decision. The report's weather sentence, the status table's footnotes and Version 2 together suggest the routes would wait for Council. No passage says so, and an inference is not enough under that test. Claude Opus 5.5 called it a close call.
- Councillor A. Salvador's notice of motion, given at the meeting, names a heading found only in the original and Version 1. That shows at least one member worked from an earlier version. It does not show which version the committee considered.
- The status table is dated August 10, 2026, sixteen days before the meeting. No reviewer found a dated City record of each route's status on August 26.
- GPT-6 Luna said in cross-review that "no delivery plan or schedule" does not show construction had not started on five routes. The other two seats counted all 14 as unbuilt. Under Version 2 the finding is the same either way.
- Whether freezing, re-evaluating or building the routes is the right choice is not tested.
Did Councillors Karen Principe and Jennifer Rice twice try to cut Edmonton's bike-lane budget to $50 million, and did council vote them down?
Part holds; as stated it overreaches.More in the methodology· All three seats reached the same verdict. Panel agreement describes seats, not vendors; two OpenAI seats agreeing are not two independent vendor confirmations.More in the methodology panel
What kind of record answered the question — an audited statement, a council report, a dataset. It is reported apart from the finding, because a claim can be Supported on a thin basis.More in the methodology: Direct Edmonton evidence
- In December 2022 City Council approved the bike-lane program, capital profile CM-20-0330, at $100,000,000 for 2023 to 2026, funded by tax-supported debt. The vote was 9 to 4, and Rice and Principe were among the four against. YF-EV-0204
- At its November 2023 budget meeting, Council voted on an amendment moved by Principe and seconded by Rice to reduce the program by $50,000,000 ($16,350,000 in 2024, $16,825,000 in 2025 and $16,825,000 in 2026) "with a funding reduction from tax-supported debt". As first moved, it would have sent the $50 million "towards the tax levy". Principe re-stated it before the vote. YF-EV-0211
- It was defeated 4 to 8, with Principe and Rice among the four in favour. One councillor is not recorded on the vote. The minutes list every name. YF-EV-0211
- On a $100,000,000 base, the 2023 cut would have left $50,000,000, a calculation made here. YF-EV-0204, YF-EV-0211
5 more facts
- A year later, in December 2024, Principe moved and Rice seconded another amendment, to decrease the program by $33,650,000 in 2025 and $33,650,000 in 2026 "with funding from tax-supported debt, to defund planning, design and delivery" of the program. YF-EV-0212
- Council defeated it 4 to 7. Principe and Rice voted for it with two others, one councillor was absent and another is not recorded, and the minutes list every name. YF-EV-0212
- The 2024 cut adds up to $67,300,000. On a $100,000,000 base it would have left $32,700,000, about a third. Both figures are calculations made here. YF-EV-0204, YF-EV-0212
- In August 2026 administration still described the program as $100 million approved in the 2023-2026 capital budget. YF-EV-0118
- The minutes of the spring budget-adjustment meetings of June 2023, June 2024 and June 2025 hold no motion naming the program. In June 2024 Principe moved and Rice seconded an amendment on new capital profiles requesting funding, which does not name the program, and it was defeated 2 to 10. YF-EV-0230, YF-EV-0231, YF-EV-0232
Also said as — 1 captured wording
Quoted exactly from sources we hold. Each name is a pseudonym, one to a person within its source.
Councillor Karen Principe and I brought forward two motions — twice — to cut it to $50M and redirect the rest to core priorities. Council didn’t support them.
Amber Owl J. · in the register · the post
Limitations
- The part that holds is two cuts, each moved by Principe and seconded by Rice, on separate occasions, both put to Council and both defeated. The part that does not is the amount. The 2024 cut would have left far less than $50 million, outside the band of $45 million to $55 million fixed before the research.
- The 2023 text says where the money goes, a reduction in borrowing. The 2024 text names the borrowing that funds the program but does not say where the money taken out would go. Neither motion's text uses the words "core priorities", and this page does not judge whether a destination was one.
- On a looser reading, a cut of at least half, both motions qualify on size. The 2024 motion would still lack a stated destination, so the finding stays the same. GPT-6 Luna first said that reading gave a yes, and in cross-review agreed the 2024 text names no destination.
- This site could not open or archive the budget sheet for the program as it stood at either motion, so both cuts are measured against the $100,000,000 approved in December 2022. The 2024 cut would have left about $50 million only if the budget had risen to between $112.3 million and $122.3 million by then. No reviewer found a change that large, and the 2026 report still gives $100 million as the approved amount.
- Other recorded motions by the two councillors that bear on the program were not budget cuts that came to a vote. In November 2023 Rice moved, and Principe seconded, a $26,808,000 cut to the 2024 capital budget that did not name the program, and Rice withdrew it. In September 2025 Principe seconded T. Cartmell's motion to stop construction on bike lanes not yet started, pending a review of every project, and Council defeated it 4 to 9.
- The reviewers read the Council budget meetings of December 2022, November 2023 and December 2024 and several other Council meetings. They could not search the spring budget-adjustment meetings of 2023 to 2025. This site read those minutes after the panel ran and found no motion naming the program. Other Council meetings in the period were not searched, so another motion could exist.
Claims with no finding
These were made about this question and have not been through the panel. The question above is answered; these claims are not. Nothing here says whether any of them is true.
- The same seven councillors vote together to keep the bike lane expansion going.
Said in 2 comments
Set aside for this check, because some Council votes it needs, from late 2022 on, are not in our archive yet and some bundled budget votes are not sorted out. It can be checked once they are.
Edmonton evidence
- Active Transportation Implementation Acceleration Program Update (Infrastructure Services report IS03688, Infrastructure Committee, 2026-08-26)
City of Edmonton · retrieved · YF-EV-0118
The AI reviewers read our archived copy because the City’s portal blocked automated access. All the AI reviewers read the same copy. City original · How we handle this · SHA-256
a4a409732b8052a0951b2fc9b4092e95f09ab2386b27b77dba12c902e3513237 - Modified Approach for the Active Transportation Network Expansion Program (replacement Attachment 5 to IS03688, Infrastructure Committee, 2026-08-26)
City of Edmonton · retrieved · YF-EV-0140
The AI reviewers read our archived copy because the City’s portal blocked automated access. All the AI reviewers read the same copy. City original · How we handle this · SHA-256
7acca16e46a7150aa34fc2daec79328a1951b543171629f7aed86ed774061175 - City Council, Budget, November 30 to December 16, 2022: post-meeting minutes (all the meeting's minutes on one page)
City of Edmonton · retrieved · YF-EV-0204
The AI reviewers saw only the items on this City meeting page that our published rule picked, from our archived copy, because the City’s portal blocked automated access. All the AI reviewers read the same copy. We have found no permission to republish our copy, so check the items against the City’s own page. City page · The rule (v2) · Item index · How we handle this · page SHA-256
4c5c54791015a218012e048274cd07d623bb1e3250226e846acbda6317616737 - Infrastructure Committee, August 26, 2026: post-meeting minutes
City of Edmonton · retrieved · YF-EV-0209
The AI reviewers saw only the items on this City meeting page that our published rule picked, from our archived copy, because the City’s portal blocked automated access. All the AI reviewers read the same copy. We have found no permission to republish our copy, so check the items against the City’s own page. City page · The rule (v2) · Item index · How we handle this · page SHA-256
5d93351574120684be0b6d3393f41f0b4fd3b937cb56b52b09f804a7a5a315c2 - Infrastructure Committee, August 26, 2026: agenda page with the attachment list for item 7.6
City of Edmonton · retrieved · YF-EV-0210
The AI reviewers saw only the items on this City meeting page that our published rule picked, from our archived copy, because the City’s portal blocked automated access. All the AI reviewers read the same copy. We have found no permission to republish our copy, so check the items against the City’s own page. City page · The rule (v2) · Item index · How we handle this · page SHA-256
b739fd311561500b30bce23a5f493419f1799d89f2482f1601cbf3ca1ffe153d - City Council, Budget, November 21 to 28, 2023: post-meeting minutes (Fall 2023 Supplemental Capital Budget Adjustment)
City of Edmonton · retrieved · YF-EV-0211
The AI reviewers saw only the items on this City meeting page that our published rule picked, from our archived copy, because the City’s portal blocked automated access. All the AI reviewers read the same copy. We have found no permission to republish our copy, so check the items against the City’s own page. City page · The rule (v2) · Item index · How we handle this · page SHA-256
45e770bf382f4a2b48edff07757d3a8cd0a5446d251dcd92649252a508ad7ef8 - City Council, Budget, December 2 to 3, 2024: post-meeting minutes (Fall 2024 Supplemental Capital Budget Adjustment)
City of Edmonton · retrieved · YF-EV-0212
The AI reviewers saw only the items on this City meeting page that our published rule picked, from our archived copy, because the City’s portal blocked automated access. All the AI reviewers read the same copy. We have found no permission to republish our copy, so check the items against the City’s own page. City page · The rule (v2) · Item index · How we handle this · page SHA-256
c3e6491d26ddc6019dfbe8793bf8f1b1a49f5987768ae28dbd3574b5a4af0409 - City Council, September 16 to 17, 2025: post-meeting minutes
City of Edmonton · retrieved · YF-EV-0213
The AI reviewers saw only the items on this City meeting page that our published rule picked, from our archived copy, because the City’s portal blocked automated access. All the AI reviewers read the same copy. We have found no permission to republish our copy, so check the items against the City’s own page. City page · The rule (v2) · Item index · How we handle this · page SHA-256
2911cef24ab75be2917017aaddbfb472813ff76a0d878bf93ac8515dbd55ade9 - City Council, July 7 to 8, 2026: post-meeting minutes
City of Edmonton · retrieved · YF-EV-0214
The AI reviewers saw only the items on this City meeting page that our published rule picked, from our archived copy, because the City’s portal blocked automated access. All the AI reviewers read the same copy. We have found no permission to republish our copy, so check the items against the City’s own page. City page · The rule (v2) · Item index · How we handle this · page SHA-256
ae8883b3469f54e77ce28c0efd0dfe1b88fdb86e56a79a30bedc277d5cc11e2b - Executive Committee, September 2, 2026: post-meeting minutes
City of Edmonton · retrieved · YF-EV-0216
The AI reviewers saw only the items on this City meeting page that our published rule picked, from our archived copy, because the City’s portal blocked automated access. All the AI reviewers read the same copy. We have found no permission to republish our copy, so check the items against the City’s own page. City page · The rule (v2) · Item index · How we handle this · page SHA-256
3011af942a568c872f178c60fb336238b97673f5de76414b38a2c8bbed961283 - City Council, October 6, 2026: agenda as published on September 25, 2026
City of Edmonton · retrieved · YF-EV-0221
- Attachment 5 to IS03688 as first published: the modified approach, with its lists of 13 continuing and 14 re-evaluated routes (Infrastructure Committee, 2026-08-26)
City of Edmonton · retrieved · YF-EV-0222
The AI reviewers read our archived copy because the City’s portal blocked automated access. All the AI reviewers read the same copy. City original · How we handle this · SHA-256
9c76f3499566b5edcb2f80f6124d546be4876762fcb6db0d50ce0b43b33b4cc4 - Replacement Attachment 5, Version 1, to report IS03688: the same route lists, the routes listed apart may be revisited (2026-08-26 committee agenda)
City of Edmonton · retrieved · YF-EV-0223
The AI reviewers read our archived copy because the City’s portal blocked automated access. All the AI reviewers read the same copy. City original · How we handle this · SHA-256
582a2058b166bde9d8899d6dd1b420d1340f9a20a7ac966ab694fbb59f433100 - Attachment 3 to IS03688 as first published: locations and status updates for the program's routes, accurate as of August 10, 2026 (Infrastructure Committee, 2026-08-26)
City of Edmonton · retrieved · YF-EV-0225
The AI reviewers read our archived copy because the City’s portal blocked automated access. All the AI reviewers read the same copy. City original · How we handle this · SHA-256
022129877854062ecd0b681c01c0b7bff1240fd387f9d30799862c829d15bfa4 - Replacement Attachment 3 to IS03688: the same route status tables as the original, with a shortened note on routes that have no delivery plan (2026-08-26 committee agenda)
City of Edmonton · retrieved · YF-EV-0226
The AI reviewers read our archived copy because the City’s portal blocked automated access. All the AI reviewers read the same copy. City original · How we handle this · SHA-256
6ee56557e3b04b245a188d40a9c43c41bae0a0aeb9047d2f6bb54c7a182d0b17 - City Council, September 8 to 16, 2026: post-meeting minutes (as published on September 29, 2026)
City of Edmonton · retrieved · YF-EV-0227
The AI reviewers saw only the items on this City meeting page that our published rule picked, from our archived copy, because the City’s portal blocked automated access. All the AI reviewers read the same copy. We have found no permission to republish our copy, so check the items against the City’s own page. City page · The rule (v2) · Item index · How we handle this · page SHA-256
b8df8acace7d0e7faf5e1b84a5d38b5b280210058803e5aab8c3571034cb0cc2 - City Council Public Hearing, September 15, 2026: post-meeting minutes
City of Edmonton · retrieved · YF-EV-0228
- City Council Public Hearing, September 22, 2026: post-meeting minutes
City of Edmonton · retrieved · YF-EV-0229
- City Council, June 13, 2023: post-meeting minutes (Spring 2023 Supplemental Capital Budget Adjustment)
City of Edmonton · retrieved · YF-EV-0230
- City Council, June 11, 2024: post-meeting minutes (Spring 2024 Supplemental Capital Budget Adjustment)
City of Edmonton · retrieved · YF-EV-0231
- City Council, June 10, 2025: post-meeting minutes (Spring 2025 Supplemental Capital Budget Adjustment)
City of Edmonton · retrieved · YF-EV-0232
What remains unknown
- What City Council will do with Salvador's motion, laid over to October 6, 2026, after this page's cut-off date of September 25.
- Whether any Council meeting before September 25, 2026 that the reviewers did not read dealt with the report.
- Which version of Attachment 5 the committee had before it when it dealt with the item.
- What administration told the committee in its presentation, which no reviewer could read.
- The program's approved budget as it stood on the days of the 2023 and 2024 motions.
- Whether either councillor brought another reduction motion at a Council meeting that was not searched.
Missing evidence
Records we asked for and have not received, or that do not appear to exist publicly.
- Complete City Council minutes for every regular meeting from August 26 to September 25, 2026, read whole rather than as selected items (City of Edmonton, Office of the City Clerk).
- A clerk's record or the meeting video showing which version of Attachment 5 was before the committee, and administration's presentation on the item (City of Edmonton, Office of the City Clerk and Infrastructure Services).
- The program's capital budget sheet as approved at the fall 2023 and fall 2024 budget adjustments (City of Edmonton, Financial and Corporate Services).
AI review
Three AI model seats from two vendors research each claim: one Anthropic model and two OpenAI models. The two OpenAI seats are not independent of each other, so three agreeing verdicts are not three independent confirmations. The canonical finding is computed from the blind round-one verdicts by a deterministic rule published in advance; the models never vote and never decide. Cross-review documents their errors, and what it changed is shown below rather than folded into the finding. Authority comes from the methodology, not from the models.
Each reviewer's verdict and confidence are from round one, the round in which the reviewers worked independently.
| Claim | Claude Opus 5.5 | GPT-6 Sol | GPT-6 Luna | Panel finding |
|---|---|---|---|---|
| Did council's Infrastructure Committee turn down administration's proposed pause on the remaining bike routes, and did full City Council later decide it? | Partially supportedHigh | Partially supportedModerate | Partially supportedHigh | Partially supportedUnanimous panel |
| Did Edmonton's administration recommend freezing 14 future bike routes to reassess them? | Partially supportedModerate | Partially supportedModerate | Partially supportedModerate | Partially supportedUnanimous panel |
| Did Councillors Karen Principe and Jennifer Rice twice try to cut Edmonton's bike-lane budget to $50 million, and did council vote them down? | Partially supportedModerate | Partially supportedHigh | Partially supportedHigh | Partially supportedUnanimous panel |
Reviewer notes — Did council's Infrastructure Committee turn down administration's proposed pause on the remaining bike routes, and did full City Council later decide it?
Claude Opus 5.5
- Found no motion to adopt the recommendation in the committee's minutes, and a 2 to 2 tie that defeated the motion to keep building at the approved scope.
- Read Version 2 as not proposing a hold, and the first two versions as proposing one, with the same finding under each because the committee decided neither.
- Found the recommendation had not reached City Council by September 25, so nothing can be said about Council as a body.
After cross-review: No change in verdict. Corrected its own statement about how far the City's open voting record reached, which it found ran to September 22, 2026 and showed no Council vote on the report.
GPT-6 Sol
- The committee neither adopted the recommendation nor carried a motion against it, so it left it without a decision.
- Version 2 proposed evaluation and a report in the first quarter of 2027 without saying the 14 routes must wait.
- No later Council decision is shown, and no override.
After cross-review: No change. In cross-review it said one meeting's selected minutes cannot show that Council never received the recommendation across the whole period.
GPT-6 Luna
- The recommendation was not put to a vote, and the committee defeated a separate motion to continue at the approved scope.
- Council's related notice of motion was laid over to October 6, after the cut-off date.
After cross-review: No change.
Reviewer notes — Did Edmonton's administration recommend freezing 14 future bike routes to reassess them?
Claude Opus 5.5
- All three versions set apart the same 14 routes, none of them started as of August 10, 2026.
- The original and Version 1 held the routes back pending evaluation. Version 2 proposed re-evaluation and a report without saying the routes would wait.
- The minutes do not say which version the committee considered.
After cross-review: No change. In cross-review it pointed out that the councillor's notice of motion names a heading found only in the earlier versions.
GPT-6 Sol
- Version 2 lists 13 continuing and 14 set-apart entries and does not say all 14 must wait.
- The original says the 14 would be removed from the program for 2026 and 2027, which meets the test.
After cross-review: No change in verdict. In cross-review it accepted that Version 1's rule that routes would be evaluated to decide whether they proceed also meets the test.
GPT-6 Luna
- Version 2 says the 14 may be re-evaluated and does not expressly defer them.
- Only the original states removal from the program for a stated period.
After cross-review: Raised its confidence to High without changing its verdict. It said in cross-review that the status of five routes with no delivery plan is unresolved, so under the earlier versions it would not have reached a yes.
Reviewer notes — Did Councillors Karen Principe and Jennifer Rice twice try to cut Edmonton's bike-lane budget to $50 million, and did council vote them down?
Claude Opus 5.5
- Both amendments were moved by Principe and seconded by Rice, and both were defeated, 4 to 8 in 2023 and 4 to 7 in 2024.
- The 2023 cut would have left $50 million. The 2024 cut would have left about $32.7 million.
After cross-review: No change in verdict, confidence raised to High. In cross-review it agreed the 2024 text names no clear destination for the money.
GPT-6 Sol
- The 2023 amendment expressly reduced borrowing and would have left $50 million.
- The 2024 amendment would have left $32.7 million and names a funding source rather than a destination.
After cross-review: No change in verdict, confidence lowered to Moderate because the budget at each motion date rests on the 2022 approval.
GPT-6 Luna
- Two jointly brought cuts, on separate occasions, both defeated.
- On the $100 million base only the first falls in the $45 million to $55 million band.
After cross-review: No change in verdict. It corrected its round-one note, which named Rice as mover of the 2024 amendment, to Principe as the minutes record, and agreed the 2024 text names no destination.
That directory also holds the raw round-one and round-two JSON from every reviewer, the merged evidence and the synthesis output.
Every seat ran at its pinned high reasoning setting; the manifest records it per run.
How it was registered
Registered · Said in 9 comments
- How far the work has got
- Gate complete
- Whether it is worth checking
- Going ahead
- What a reader can see
- Published
The reason recorded for this question
Administration’s report and recorded votes can show what pause was recommended, which motions were made and how each councillor voted, without examining the allegation about councillors’ motives.
The committee report and the recorded council votes settle the recommendation, the motions and who voted which way.
Taken from Yegscoop post on council's 2026-08-26 bike lane decision, read end to end: facebook post, captured , 621 comments. Every factual claim in it was extracted and merged, so this question is listed whatever became of it.
Article history
- publishedPublished after the gate and the critique passed. Each check's report is committed with the editor's dispositions under reviews/council-pause-vote/2026-09-25/. Faithfulness checks by GPT-6 Sol and GPT-6 Luna (faithfulness/gpt-1.md, faithfulness/gpt-luna-1.md). A freshness audit by GPT-6 Sol (gate/freshness-audit.md), which led to five more City minutes pages, YF-EV-0228 to 0232. A plain-speech read by GPT-6 Sol (plain-speech/gpt-1.md). Source verification and a release check by a separate Claude Opus 5.5 audit session (gate/source-verification.md, gate/release-check.md), then two confirmations (gate/confirmation.md, gate/final.md); the gate passed after its final one-sentence fix. A critique of the rendered page with a phone test (critique-1.md), and two confirmations with phone tests (critique-1-confirmation.md, critique-1-final.md); the critique passed. No finding changed at any stage: three claims Partially supported, Unanimous, and the fourth set aside for this run.
- updatedRevised after the publication gate and a critique of the rendered page, each report committed with the editor's dispositions under reviews/council-pause-vote/2026-09-25/. Before the gate, two faithfulness checks (GPT-6 Sol and GPT-6 Luna), a freshness audit and a plain-speech read (both GPT-6 Sol) read the draft. The freshness audit led to five more City minutes pages, read after the panel ran (YF-EV-0228 to 0232). The gate corrected four statements: one commenter was described as a sitting councillor when she had left Council at the October 2025 election, claim 2's answer named only one of the two earlier versions that held the routes back, all three reviewers (not two) read Version 1 as a freeze in cross-review, and two procedural motions carried at the committee besides the confidential-attachment motion. That commenter is now shown under a pseudonym, as every commenter who is not an office-holder is. The critique led to a standfirst that answers the question asked, two plainer TL;DR bullets, and a line on the set-aside claim's own page. No finding changed.
- updatedDrafted from the panel run of 2026-09-29 for review before publication. The brief listed four claims. The panel tested three and reached findings on each, all Partially supported and unanimous. The fourth, that the same seven councillors vote together, was set aside before the rounds because the full set of recorded votes could not be assembled, and the page says so. The panel read the City's report and selected minutes items from our archived copies, because the City's meeting portal blocked automated access, and each of those sources is labelled.
Every revision is in the public commit history of this file.
