Skip to content

Latest commit

 

History

History
27 lines (20 loc) · 1.54 KB

File metadata and controls

27 lines (20 loc) · 1.54 KB

Consequence scan

Date: 2026-07-10
Decision: Proceed with safeguards.

Intended outcomes

  • Help a small transit agency find the few GTFS changes most likely to help riders.
  • Give support staff a reproducible, plain-language view before an agency call.
  • Preserve open evidence for researchers and feed consumers.

Plausible harms and controls

Harm Who is affected Control and evidence
A low grade is treated as staff or service performance Agency staff and vendors Fix-first copy, comparison policy, no compliance claim, evidence-backed corrections
Small or rural agencies are penalized for lacking realtime Small agencies Realtime is optional and “not yet published” is neutral
Old or partial data drives a ranking Agencies and press Freshness/measurement eligibility, minimum cohort, dated artifacts, suppression metadata
A false listing or ownership claim changes public facts Agencies Human review and three evidence paths; requests are unverified by default
Automated outreach becomes spam Agency contacts Opt-in alerts, polling etiquette, cohort worklists rather than bulk unsolicited delivery
An accessibility visualization excludes a user Disabled users Semantic values/table alternatives, 320px/keyboard/axe gates, public barrier channel

Stop conditions

Pause publication if scoring cannot distinguish unavailable data from poor data, a comparison lacks a defensible cohort, a correction cannot be traced to evidence, or a core route fails the accessibility gate.