Also, what do you mean by trains being local-first? Trains by definition need to share the same tracks with catastrophic consequences for getting it wrong. You can't figure out if a train is going to possibly be on the same route locally, or if your route has been obstructed. Somebody gets a schoolbus stuck on a crossing, it takes over a mile to stop a train.
In the days before systems existed for publishing such schedules and emergency alerts, should public transit service not have been attempted at all?
> Trains by definition need to share the same tracks with catastrophic consequences for getting it wrong.
Just because it uses the same rail gauge as intercity freight doesn't require it to run on the same set of tracks. But if it did, I assume "local-first" entails other traffic just being excluded when an emergency in the local system necessitates it.
> Just because it uses the same rail gauge as intercity freight doesn't require it to run on the same set of tracks
Building a replica set of tracks that runs parallel to the current tracks just to avoid sharing doesn't strike me as a good use of anyone's time/money.
> "local-first" entails other traffic just being excluded
And how are you going to notify them that they are excluded when the network is down?