Public rider information
Public corrections
See what Otranspo published, what changed, why it changed, and which pages were corrected.
Versioned public record
Material corrections recorded
3
- Application source
- 3 of 3 corrected claims current
- Current production deployment
- 0 of 3 verified
Current method and publication status
Every correction below is complete in the application source. Production verification is tracked separately, so this page never treats a branch, review, or approval state as proof that otranspo.ca is running the corrected method.
Versioned public record
Service report publication state
complete in source; production verification pending
- Correction date
- Record published
- Version
- Revision 1
Superseded claim
monthly-service-report-v5
Final meant calendar coverage was complete and also said the figures would not change.
Historical record; no longer current in the application source.
Current corrected claim in application source
monthly-service-report-v6
Calendar coverage and frozen publication are separate states; mutable views identify their through-date, sample, coverage, as-of time and method.
Why it changed
A completed calendar calculation can still be an unpublished live recomputation. The prior wording promised immutability from coverage state alone and did not carry enough comparison and chart evidence for an independent reader to assess the claim.
How the problem was found
Cross-surface reconciliation of the August and September monthly pages, rolling day/week/28-day views, CSV export and stored-publication contract.
Affected pages and publication channels
These outputs carry, link to, or archive this correction. The complete cross-language manifest remains in the technical record.
Source, review, revision, and publication details
- Record identifier:
- correction:service-reports:2026-09-14:publication-state-v1
- Subject:
- method: service-reports:publication-and-coverage-state
- Independent approval:
- Independent approval pending: Open Data Steward independent verifier
- Release identifier:
- None recorded
- Production verified:
- None recorded
- Controlled facts:
- service-report-publication-state
Propagation evidence by channel
- screen: complete; /en/insights/reports, /fr/insights/reports and dated monthly reports; correction:service-reports:2026-09-14:publication-state-v1:revision-1
- api: complete; /api/public/v1/corrections; correction:service-reports:2026-09-14:publication-state-v1:revision-1
- download: complete; monthly report CSV exports and /api/public/v1/corrections?format=csv; correction:service-reports:2026-09-14:publication-state-v1:revision-1
- method: complete; monthly-service-report-v6 and settled-arrival-period-report-v2; correction:service-reports:2026-09-14:publication-state-v1:revision-1
- marketing: complete; controlled fact service-report-publication-state channel derivatives; correction:service-reports:2026-09-14:publication-state-v1:revision-1
- grant: complete; apps/otranspo/docs/comprehensive-build/S32-VERSIONED-SERVICE-REPORTS.md; correction:service-reports:2026-09-14:publication-state-v1:revision-1
- archive: complete; /en/corrections, /fr/corrections and immutable report documents; correction:service-reports:2026-09-14:publication-state-v1:revision-1
Complete affected-publication manifest
- /en/insights/reports
- /fr/insights/reports
- /en/insights/reports/2026-08
- /fr/insights/reports/2026-08
- /en/insights/reports/2026-09
- /fr/insights/reports/2026-09
- Monthly report CSV exports
- /en/corrections
- /fr/corrections
- /api/public/v1/corrections
Versioned public record
Transit application contract total
complete in source; production verification pending
- Correction date
- Record published
- Version
- Revision 1
Superseded claim
contract-disclosure-sum-v0
Close to CAD $700,000 across the article and letter.
Historical record; no longer current in the application source.
Current corrected claim in application source
contract-disclosure-sum-v1
CAD $1,157,794 across four disclosed entries, including the previously omitted CAD $462,000 2024 extension.
Why it changed
The first publication omitted a $462,000 extension in the City’s July to December 2024 delegated-contract disclosure. The total and every affected article, letter and summary must retain the corrected amount and this revision record.
How the problem was found
Jenna Jessop identified the omitted City disclosure row after receiving the earlier candidate letter.
Affected pages and publication channels
These outputs carry, link to, or archive this correction. The complete cross-language manifest remains in the technical record.
Source, review, revision, and publication details
- Record identifier:
- correction:transit-app-contract:2026-09-10:omitted-extension-v1
- Subject:
- content: insights:transit-app-contract:disclosed-total
- Independent approval:
- Independent approval pending: Civic/source verification owner
- Release identifier:
- None recorded
- Production verified:
- None recorded
- Controlled facts:
- transit-app-contract-disclosed-total
Propagation evidence by channel
- screen: complete; /en and /fr article, letter, public-record, costs and corrections surfaces; correction:transit-app-contract:2026-09-10:omitted-extension-v1:revision-1
- api: complete; /api/public/v1/corrections; correction:transit-app-contract:2026-09-10:omitted-extension-v1:revision-1
- download: complete; /api/public/v1/corrections?format=csv; correction:transit-app-contract:2026-09-10:omitted-extension-v1:revision-1
- method: complete; contract-disclosure-sum-v1 and accountable research article v2; correction:transit-app-contract:2026-09-10:omitted-extension-v1:revision-1
- marketing: complete; controlled fact transit-app-contract-disclosed-total derivatives; correction:transit-app-contract:2026-09-10:omitted-extension-v1:revision-1
- grant: complete; apps/otranspo/docs/comprehensive-build/S34-ACCOUNTABLE-RESEARCH-ARTICLES.md; correction:transit-app-contract:2026-09-10:omitted-extension-v1:revision-1
- archive: complete; /en/corrections, /fr/corrections and versioned corrections API; correction:transit-app-contract:2026-09-10:omitted-extension-v1:revision-1
Complete affected-publication manifest
- /en/insights/transit-app-contract
- /fr/insights/transit-app-contract
- /en/insights/transit-app-contract/letter
- /fr/insights/transit-app-contract/letter
- /en/public-record
- /fr/public-record
- /en/costs
- /fr/costs
- /en/corrections
- /fr/corrections
- /api/public/v1/corrections
Versioned public record
Network on-time reliability method
complete in source; production verification pending
- Correction date
- Record published
- Version
- Revision 1
Superseded claim
archived-prediction-rows-v0
86.7
Historical record; no longer current in the application source.
Current corrected claim in application source
settled-v1
77.4
Why it changed
The prior method counted repeated predictions as independent arrivals and treated large early departures as on time. The corrected method keeps the last prediction within ten minutes of each arrival and uses a two-sided five-minute window.
How the problem was found
Reconciliation of the durable GTFS-Realtime delay archive against distinct trip, stop, and service-date arrivals.
Affected pages and publication channels
These outputs carry, link to, or archive this correction. The complete cross-language manifest remains in the technical record.
- /en/city
- /en/corrections
- /api/realtime/network-health
- /api/public/v1/corrections
- Route and station reliability summaries
- Methods documentation
Source, review, revision, and publication details
- Record identifier:
- correction:reliability:2026-08-04:settled-v1
- Subject:
- method: network-reliability:on-time-percentage
- Independent approval:
- Independent approval pending: Open Data Steward independent verifier
- Release identifier:
- None recorded
- Production verified:
- None recorded
- Controlled facts:
- network-reliability-method
Propagation evidence by channel
- screen: complete; /en/corrections and /fr/corrections; correction:reliability:2026-08-04:settled-v1:revision-1
- api: complete; /api/public/v1/corrections; correction:reliability:2026-08-04:settled-v1:revision-1
- download: complete; /api/public/v1/corrections?format=csv; correction:reliability:2026-08-04:settled-v1:revision-1
- method: complete; /en/city, /fr/city, /en/methodology and /fr/methodology; correction:reliability:2026-08-04:settled-v1:revision-1
- marketing: complete; controlled fact network-reliability-method channel derivatives; correction:reliability:2026-08-04:settled-v1:revision-1
- grant: complete; apps/otranspo/docs/PUBLIC-CORRECTION-DRILL-2026-08-12.json; correction:reliability:2026-08-04:settled-v1:revision-1
- archive: complete; apps/otranspo/docs/PUBLIC-CORRECTION-DRILL-2026-08-12.json; correction:reliability:2026-08-04:settled-v1:revision-1
Complete affected-publication manifest
- /en/city
- /fr/city
- /en/corrections
- /fr/corrections
- /api/realtime/network-health
- /api/public/v1/corrections
- Route and station reliability summaries
- Methods documentation
Use or audit the register
The JSON response preserves bilingual records and propagation evidence. The CSV adds plain source and production status columns for analysis.