1.7 KiB
CW-033 development notes
Version 0.1.0 is an archived tool prototype. No installable skill, plugin manifest, or new MCP server exists yet.
The data pipeline is OnSign native stop IDs → agency native API source-stop IDs → verified GTFS stops → active trips/routes → ordered GTFS shapes. GTFS coordinates remain authoritative; native coordinates are comparison evidence. Never join a native route ID to GTFS route_id by numerical equality.
The viewer supports online/offline signs, kiosks, excluded records, mapped-bay detail, Apple/Google navigation, vector basemap options, and credential-free fallback. It is a captured snapshot viewer, not live dispatch software.
Before another agency is supported, parameterize the RTC-specific dates/feed copy and add configuration/adapter contracts. Missing ID, name, station-parent, shape, or service-date evidence must be reported instead of guessed. A future predeployment spreadsheet/list input must use the same ID and provenance rules.
Credentials are supplied through the environment for acquisition. The renderer excludes a CARTO key unless explicitly asked to embed an approved browser key. Keep input/, dist/, private/, and all operational/customer sample-work out of the public repository. Upstream license notices remain under vendor/; no license has been selected for MPM-authored code.
Pending decisions: skill versus plugin/service boundary; multi-agency configuration; supported native adapters; ID-review workflow; refresh/access/hosting model; browser-key management; physical mobile navigation acceptance; and publication license. The full operational handoff and pilot evidence reside in the CW-033 Coordination Drive folder.