The Signal · Special Edition · October 2026
The Triumphant Return
Published October 16, 2026 · By Justin Spencer Smith · Also on LinkedIn
Published off-cycle, on the day the map became whole again.
On October 15, 2026, The Signal published a special edition titled "Shut Down by the Meter." It closed with a hope, stated carefully: to be back in the future with fuller live coverage, when the data arrangements allowed it. That was stated as hope and intent — not as a promise, and not with a date. The return began the same day. This special edition records it.
What came back
SMART is back on Live Transit Detroit — all of it. On the afternoon of October 15, SMART had been removed from the map: its segment of the stop registry was tombstoned, set aside rather than deleted, in a removal built to be reversible. That evening the segment was restored at its original positions: 5,437 SMART stops returned, bringing the registry back to 10,583 stops and the map back to 83 routes — 37 DDOT, 45 SMART, and the QLINE streetcar. Because the removal had been designed for reversal, the return was a restoration, not a rebuild, and it could happen in hours instead of weeks.
How it came back: a key, a license, and terms first
The shutdown had two causes: the hosted proxy behind the live data exhausted its host's meter, and DDOT's BusTime key hit its daily transaction cap. SMART's return runs on a different arrangement entirely. Swiftly, the transit data platform, issued the Academy an API key for SMART data on October 15 (agency key detroit-smartbus), covering GTFS-Realtime vehicle positions and trip updates, with a usage limit of 180 requests per 15 minutes.
The draw against that limit is deliberately small. The rebuilt feed reads Swiftly on a fixed five-minute cadence — about 12 requests per hour, roughly 1.7 percent of the issued limit — and the volume does not grow with the audience. That is the lesson of the meter, applied.
The license posture is display-only, and it is structural rather than promised. Under the license's terms (§4(vi)), SMART vehicles render on the map from a separate display payload; they are never merged into the public vehicles feed, and the telemetry archive excludes SMART records by construction. Both separations were proven with live data on the day of the return. And before a single SMART bus reappeared, the end-user terms the license requires were published on the site (build 20261015-1919). SMART was reactivated that evening on those terms (build 20261015-2034) — with SMART enabled, the evening's verification counted 114 live vehicles on the map.
From beta to production
For its first hours back, SMART returned under its pre-removal treatment: a filter group labeled "SMART (beta)", off by default, with each visitor's choice remembered. That night it was uplifted to full production (build 20261015-2249). The group is now labeled simply "SMART" and is on by default, like DDOT and QLINE; a visitor who has chosen otherwise keeps their choice — the stored preference wins over the default. Beta was the right posture for a feed of uncertain standing. The Swiftly arrangement is licensed, metered at a fraction of its limit, and verified; production is the right posture for that.
Verified the same night
The return was audited the night it happened. A two-pass UAT fidelity audit compared the production map against the approved state of the nine items shipped across this build-out — the home framing, route naming, camera memory, the planner service-day fix, the app-lock fix, the feed migration, the service degradation notice, the end-user terms, and the SMART reactivation itself. Static fidelity first, then interactive checks on the live page. The result: every item measured as approved, with zero unexplained divergences. A return that is verified is a return that can be announced, and this one was.
A thank-you, by name
One person made the same-day return possible, and he should be named in the same public way the shutdown was. Dante' of Swiftly Technical Support issued the Academy's key on October 15 — the day it was needed — with the agency scope, the endpoints, and the limits set out plainly. When the first retest stumbled on a wrong agency slug in our own request path, the issuance on record is what the correction was checked against. A direct thank-you has already gone to Dante' from us; this is the public one. Thank you, Dante'. The regional map is whole again in part because a support engineer did his work well and quickly, and that deserves to be said where everyone can read it.
The last dark layer
The honest remainder, and the reason this edition waited to publish: DDOT's live vehicles. DDOT positions went dark on October 15 when the key hit its daily cap, and they stayed dark while SMART returned — a regional map with a dark home agency is a return with an asterisk, and we were not going to print "triumphant" over it. The asterisk is gone. DDOT live positions returned early on Friday, October 16 — in the first build cycles after midnight, when the BusTime daily transaction limit reset — and at the restoration verification the feed carried 33 DDOT buses alongside 93 SMART vehicles and the QLINE's streetcar: 127 live vehicles on the map.
What remains open sits with DDOT, and it is the only open item left: the request to raise the key's daily cap to 50,000 transactions per day, with 25,000 stated as acceptable, sent on October 15. No decision had been recorded when this edition was finalized; the checkpoint stands on October 22. The daily reset restored service without the raise — the rebuilt feed runs at roughly 2,040 transactions a day against the key's default cap of 10,000 a day, inside the limit that reset at midnight. The request is about headroom, not survival — and the distinction is the whole story of October 15.
The QLINE, for the record, never went dark. Its feed never depended on the shut-down host or the DDOT key, and it carried 4 streetcars, live, throughout — the interim this morning's edition described, now over.
The close
This morning's edition retired a public API and recorded an arrangement that did not hold. This edition records the arrangement that replaced it: licensed data, terms published before the feature returned, a draw of 1.7 percent of the issued limit, a display-only separation proven in the data itself, and a production state verified the same night by audit. The map is regional again — 83 routes, 10,583 stops, three agencies, live on infrastructure the Academy runs itself. The next arrangement was announced when it existed. It exists.
Canonical record and full technical detail: the Live Transit Detroit series and the Academy's publish logs, at detroitautomationacademy.com/live-transit-detroit/.
The Signal is the newsletter of Detroit Automation Academy — where Detroit builds what's next. If you know a young builder who should be in the room, send them our way.