PTA Bible
The project, scope, philosophy
The network map
Every station in the network, plotted where it actually sits, coloured by the line it currently reads as. Pick a line and the map holds it on its own while that line opens beside it, straight out of the Bible. Grey is unassigned: a station that exists on the map but has no confirmed line yet.
Line assignments come from the in-game route tags and confirmed spot checks first, then from the alignments the Bibles themselves describe. It is not a finished stop list yet.
Status: IN PROGRESS. This is the high-level project document, covering what PTA is, the core thesis, philosophy, and framing. Operational content (lines, routes, service tiers, fleet) lives in PTA Metro Bible, PTA Regional Rail Bible, and PTA Keystone Rail Bible, not here.
What PTA Is
PTA (Philadelphia Transit Authority) is a fictional transit authority: a passion project of Therum Creative Studios. It's a speculative, design-driven reimagining of regional transit for Greater Philadelphia, built around an expansive, LA/London/Tokyo-scale metro network covering the full Philadelphia region. It is not a proposal to replace SEPTA. It is a systems-level thought experiment exploring how transit could function if designed today, with clarity, equity, scalability, and legibility at its core. The project combines urban planning, infrastructure logic, branding, mapping, wayfinding, and operational design into a single cohesive vision.
Multi-Modal Scope
PTA is not metro-only:
- Metro: the core of the project, everything documented in the Metro Bible.
- Regional Rail, documented in the Regional Rail Bible.
- Tram system, separate mode, not yet detailed.
- Bus network, separate mode, not yet detailed.
Alongside PTA's own modes, Keystone Rail is a separate, state-run rail authority: not a PTA mode, and not geographically connected to it. Its roster doesn't enter Philadelphia at all; it's a separate network across Lancaster, Berks, the Lehigh Valley, Harrisburg, and Scranton. Documented in its own Keystone Rail Bible (see below).
Real-World System Interoperability
Built into the map as real-world systems interoperating at the edges, not as build targets in their own right:
- NJ Transit, joint operations in South Jersey, already reflected on the Metro Red Line and throughout the Regional Rail Bible's NJT Branches section.
- Amtrak, modeled on a Shinkansen-style high-speed network, not standard Amtrak equipment/service as it exists today.
- Metro-North / NYC-area systems, likely interaction planned, not yet detailed.
- MARC (Maryland), whatever's accessible into Baltimore, likely MARC-based, not yet detailed.
Keystone Rail
A state-level rail system, operated by the Commonwealth of Pennsylvania, not PTA, and distinct from Amtrak. Philadelphia is the state's most populous city and functionally has "its own thing going on," which was the original reasoning for Keystone Rail's existence, but per the confirmed route roster, no Keystone Rail route actually enters Philadelphia or touches Center City. It's a separate network entirely, connecting western, northern, and northwestern Pennsylvania (Lancaster, Reading, the Lehigh Valley, Harrisburg, Scranton), corridors Amtrak doesn't serve in this project, but none of that mileage runs through the city PTA itself operates in. It's a separate operator with its own state-rail identity, not a re-skin of the federal system and not a PTA subsidiary. Full route buildout lives in the Keystone Rail Bible.
Geographic Scope
PTA is a true regional system, reflecting how people actually live and move across Greater Philadelphia rather than stopping at the city line. Coverage includes Philadelphia proper, Chester and Delaware Counties, Montgomery County, King of Prussia, Media and Springfield, the South Jersey suburbs, Philadelphia International Airport, and the major employment and transfer hubs that tie the region together. This positions PTA as a true metropolitan transit authority rather than a fragmented city service.
Explicit scope boundary: no interest in building out full metro systems for any other city. Philadelphia's metro is the entire point of the project, everything else (NJT, Amtrak, Metro-North, MARC) exists only as interoperating real-world connections at the edges of the map, not as their own build targets.
Design Philosophy: Network Construction Logic
The network's construction logic is a three-way sort, not a historical/non-historical split as originally framed:
- Present-day trackage, corridors that exist and operate today.
- Former/historical trackage, real alignments that existed but no longer operate, or were planned/proposed historically and never completed.
- Planned or uncompleted transit projects, proposals from the historical or present-day record that never got built, incorporated here as if they had been.
On top of that sorting logic, two structural moves recur across the network:
- Freight-to-metro conversion, repurposing active or former freight corridors into metro routes (e.g. Umber Line's freight-corridor stretch through Port Richmond).
- Regional-rail-to-metro conversion, taking existing regional rail branches and repurposing them as metro routes rather than leaving them as regional rail (e.g. the Metro Yellow Line's R6-corridor basis; also Route R7's historic Chestnut Hill West branch, now covered by Metro's Teal Line Route K instead).
Core driver: transit deserts. A major focus throughout has been present-day Philadelphia transit deserts, neighborhoods and corridors that don't have a one-seat ride to where people actually need to go, or don't have rail access at all in real life. Much of the network's routing logic exists specifically to close those gaps, not to recreate history for its own sake.
Naming Doctrine
Reading order: a route is read/labeled Mode → Route → Service Tier.
- Mode = the transit system/line itself (Metro line name, or the Regional Rail / Keystone Rail system).
- Route = the specific route identifier within that mode (a letter or number for Metro; a number for Regional Rail/Keystone Rail, where the R or K prefix does double duty as both mode-indicator and part of the route name).
- Service Tier = Local / Express / Super Express.
Worked examples:
- Metro: "Blue Line, Route C, Super Express"
- Metro: "Orange Line, Route 1, Super Express"
- Metro: "Green Line, Route 5, Super Express"
- Regional Rail: "R2, Express" (confirmed in-game tag: R2 Express)
- Keystone Rail: "K-[#], [tier TBD]": no Keystone Rail route has confirmed service-tier data yet (see the Keystone Rail Bible's Open Items).
R# (Regional Rail) and K# (Keystone Rail) prefix convention:
- Regional Rail: R# prefix. Roster is now fully populated at R0 through R10, plus RX (RX is a real confirmed route, 30th Street Station ↔ Allentown: not an unused placeholder).
- Keystone Rail: same numbering logic, K prefix instead of R. Roster is fully populated at K0 through K9, plus KX, K10 is retired/unused (K9 and K10 were merged into a single K9 route; see the Keystone Rail Bible). Ties Keystone Rail's naming directly to Regional Rail's convention even though the two are run by separate operators: a shared naming doctrine across the region's rail systems, not evidence Keystone Rail is a PTA mode.