Pennsylvania

1. Topology Metadata

Classification source. The metadata layer records that the Corridor Group, Foundation Layer, and Topology Completion Layer are derived from atlas-export/docs/atlas.md. The metadata layer records that the Jurisdiction Lens is derived from Pennsylvania's corridor-layer evidence, signal, and trust review and does not override atlas-controlled topology placement.

Interpretation boundary. The metadata layer records that this file is structural topology metadata only. It does not assign routing authority, coordination tiers, Atlas surfaces, readiness, rank jurisdictions, modify evidence-layer interpretation, override evidence sufficiency boundaries, infer deployment suitability, or locally reclassify atlas-controlled corridor metadata.

2. Scope Boundary Statement

The evidence layer records that this file records only corridor-relevant structural anchors documented for Pennsylvania that are sufficient to support Atlas signal derivation. The evidence layer records that it does not perform an open-ended statewide infrastructure survey and does not assign trust posture, routing role, coordination tier, or Atlas surfaces.

This rendering mirrors the canonical package. The canonical Pennsylvania package is explicitly scope-narrowed to corridor-layer anchors — all completeness statuses across evidence, signals, trust, profile, and builder-mode are canonically recorded as "corridor-layer sufficient" rather than "preliminary". This is a distinct canonical neutrality category.

The canonical package repeatedly emphasizes that Pennsylvania's jurisdiction lens is interpretive only and does not override atlas-controlled topology metadata. The Great Lakes and inland-river references in the lens inform evidence interpretation, but Pennsylvania's canonical topology placement remains Northeast Institutional Mesh Corridor under atlas-controlled metadata.

3. Evidence Summary

The evidence layer records 9 evidence subsections documenting Pennsylvania's corridor-relevant structural anchors across Great Lakes port continuity, inland river logistics, Class I rail, interstate convergence, Pittsburgh air cargo, research institutions, PJM transmission, BEAD broadband coordination, and corridor-linked industrial persistence.

Great Lakes port continuity

• The evidence layer records that the Erie-Western Pennsylvania Port Authority states Erie is Pennsylvania's only commercial lake port and the region's import and export link to the world through the St. Lawrence Seaway.
• The evidence layer records that the Port of Erie commercial materials state the port has efficient links to rail and Interstates 79 and 90.
• The evidence layer records that the same materials document drydocking, ship repair, dockage, warehousing, rail connection, and bulk-material handling at corridor-relevant Erie terminals.

Inland river logistics system

• The evidence layer records that the Port of Pittsburgh Commission states it promotes the commercial use and development of inland waterways for the residents and industries of southwestern Pennsylvania.
• The evidence layer records that Port of Pittsburgh materials identify the Allegheny, Monongahela, and Ohio rivers as the core inland-waterway structure, noting eight locks and dams on the Allegheny, Monongahela gateway continuity from West Virginia into Pennsylvania, and the Ohio River confluence in downtown Pittsburgh.
• The evidence layer records that the Pittsburgh Intermodal Terminals page documents an Ohio River site in Ambridge Industrial Park handling dry bulk, heavy lifts, lumber, steel, and palletized goods with substantial open and covered storage.

Class I rail and intermodal visibility

• The evidence layer records that the Pennsylvania Public Utility Commission states it regulates approximately 65 railroad companies operating in the state and that Pennsylvania has nearly 5,600 miles of track.
• The evidence layer records that the Pennsylvania PUC railroad-company list includes both CSX Transportation Inc. and Norfolk Southern Railway Company as operating railroad companies in Pennsylvania.
• The evidence layer records that the Pittsburgh Intermodal Terminals page documents Class I Norfolk Southern rail access at an Ohio River terminal.

Interstate corridor convergence

• The evidence layer records that PennDOT's 2045 Freight Movement Plan materials describe the Port of Pittsburgh district as served by CSX and Norfolk Southern and by interstate corridors including I-79, I-76 / PA Turnpike, and I-80.
• The evidence layer records that PennDOT's public statewide rail-map, National Highway System, and highway-statistics materials provide direct corridor visibility for I-76, I-79, I-80, I-81, and I-95 in Pennsylvania's freight environment.
• The evidence layer records that the Port of Erie commercial materials add direct corridor linkage to I-79 and I-90 at the Great Lakes edge of the state.

Pittsburgh air cargo logistics visibility

• The evidence layer records that PIT Cargo states Pittsburgh International Airport provides a faster, smarter, more efficient cargo gateway with domestic and international access.
• The evidence layer records that PIT Cargo states the airport has a strategic location between New York and Chicago for east-west distribution.
• The evidence layer records that PIT Cargo states the airport is within 500 miles of 50% of the U.S. population and 54% of U.S. buying power, with no congestion and easy ground access.

Research-institution engineering and research visibility

• The evidence layer records that Carnegie Mellon engineering materials document cross-disciplinary robotics research spanning soft and wearable robotics, legged and aerial robots, medical robotics, micro and nano robotics, underwater robots, and IoT robots.
• The evidence layer records that Carnegie Mellon materials also document the opening of the Robotics Innovation Center for research and partners.
• The evidence layer records that University of Pittsburgh research materials state Pitt spends more than $1 billion in research expenditures each year and generated $2.4 billion in Pennsylvania economic impact in fiscal year 2023.

PJM transmission participation

• The evidence layer records that PJM states it coordinates the movement of electricity through all or parts of Pennsylvania and other Mid-Atlantic and Midwest jurisdictions.
• The evidence layer records that PJM states its public transmission maps include infrastructure from 69 kV up to 765 kV.

Pennsylvania BEAD broadband coordination

• The evidence layer records that the Pennsylvania Broadband Development Authority states Pennsylvania will receive more than $1.16 billion in federal BEAD funding.
• The evidence layer records that PBDA states Pennsylvania completed a BEAD 5-Year Action Plan approved in October 2023.
• The evidence layer records that PBDA states approved BEAD proposal materials cover community anchor institutions, local coordination efforts, implementation activities, and related broadband deployment planning.

Corridor-linked industrial persistence

• The evidence layer records that Port of Erie commercial materials document shipbuilding, dry-docking, cargo management, material handling, and rail-connected bulk-terminal operations on Lake Erie.
• The evidence layer records that Port of Pittsburgh materials describe the Monongahela as a river once home to many of Pittsburgh's steel mills, and the Pittsburgh Intermodal Terminals page documents steel among the commodities handled on the Ohio River.
• The evidence layer records that Pennsylvania manufacturing materials state manufacturing employs 1 in 10 residents, contributes more than $111 billion annually to the state economy, and includes metallurgy and metal manufacturing that strengthen robotics, technology, and energy.

4. Signals Summary

Derivation constraint. The signals layer records that signals derive strictly from evidence.md. The signals layer records that absence of signals reflects absence of normalized documentary coverage.

The signals layer records 9 structural coordination signals directly detectable from the evidence layer. Signal clusters use snake_case canonical keys.

great_lakes_port_continuityGreat Lakes port-continuity signal

The signals layer records that Pennsylvania shows a Great Lakes port-continuity signal through Erie's documented St. Lawrence Seaway linkage, rail connectivity, Interstate 79 and 90 linkage, and commercial port operations.

inland_river_logistics_systemInland-river logistics-system signal

The signals layer records that Pennsylvania shows an inland-river logistics-system signal through the documented Allegheny, Monongahela, and Ohio river structure and the Ohio River intermodal terminal activity documented by the Port of Pittsburgh Commission.

class_i_rail_and_intermodal_visibilityClass I rail and intermodal-visibility signal

The signals layer records that Pennsylvania shows a Class I rail and intermodal-visibility signal through documented CSX and Norfolk Southern operating presence, substantial statewide rail mileage, and Norfolk Southern visibility at an Ohio River intermodal terminal.

interstate_transition_corridor_visibilityInterstate transition-corridor visibility signal

The signals layer records that Pennsylvania shows an interstate transition-corridor visibility signal through documented corridor presence for I-76, I-79, I-80, I-81, and I-95, with Erie and Pittsburgh-linked freight materials reinforcing west and central corridor continuity.

pittsburgh_air_cargo_visibilityPittsburgh air-cargo visibility signal

The signals layer records that Pennsylvania shows a Pittsburgh air-cargo visibility signal through PIT's documented east-west distribution position, population reach, buying-power reach, and cargo-gateway framing.

research_institution_adjacencyResearch-institution adjacency signal

The signals layer records that Pennsylvania shows a research-institution adjacency signal through documented Carnegie Mellon robotics and engineering activity and University of Pittsburgh research scale and continuity.

pjm_transmission_participationPJM transmission-participation signal

The signals layer records that Pennsylvania shows a PJM transmission-participation signal through documented inclusion in PJM territory and visibility into regional transmission infrastructure maps.

broadband_coordination_visibilityBroadband-coordination visibility signal

The signals layer records that Pennsylvania shows a broadband-coordination visibility signal through documented BEAD funding, a completed 5-Year Action Plan, and approved proposal materials covering local coordination and community-anchor planning.

corridor_linked_industrial_persistenceCorridor-linked industrial-persistence signal

The signals layer records that Pennsylvania shows a corridor-linked industrial-persistence signal through documented Great Lakes port industry, Ohio River steel-handling continuity, and statewide manufacturing materials tied to metallurgy, robotics, technology, and energy.

5. Trust Dimensions Summary

Derivation constraint. The trust-dimensions layer records that dimensions derive strictly from signals.md. The trust-dimensions layer records that absence of signals reflects absence of normalized signal-layer coverage.

The trust-dimensions layer records 6 trust dimensions with a canonical 2-field pattern (current interpretation + "most visible in" basis list). Dimensions use snake_case canonical keys.

corridor_interface_continuityCorridor-interface continuity

The trust-dimensions layer records that Pennsylvania shows corridor-interface continuity through the combination of Erie Great Lakes access, Pittsburgh inland-river logistics, and documented interstate corridor presence across western, central, and eastern freight structure.

• Erie Great Lakes and St. Lawrence Seaway linkage
• Allegheny, Monongahela, and Ohio river logistics structure
• interstate visibility across I-76, I-79, I-80, I-81, and I-95

multimodal_logistics_densityMultimodal logistics density

The trust-dimensions layer records that Pennsylvania shows multimodal logistics density where documented through port, river, rail, highway, and air-cargo anchors.

• Port of Erie commercial port and terminal structure
• Port of Pittsburgh inland-waterway and intermodal terminal structure
• PIT cargo-gateway positioning
• Class I rail visibility across CSX and Norfolk Southern documentation

research_adjacency_continuityResearch-adjacency continuity

The trust-dimensions layer records that Pennsylvania shows research-adjacency continuity through documented Carnegie Mellon engineering and robotics activity and University of Pittsburgh research scale.

• Carnegie Mellon robotics and engineering research activity
• University of Pittsburgh research expenditure and institutional scale

industrial_persistenceIndustrial persistence

The trust-dimensions layer records that Pennsylvania shows industrial persistence where documented through Great Lakes port operations, Ohio River steel-handling continuity, and manufacturing-sector visibility tied to metallurgy and advanced industry.

• Erie shipbuilding, dry-docking, and bulk-terminal activity
• Monongahela and Ohio River industrial-freight continuity
• statewide manufacturing materials linked to metal, robotics, technology, and energy sectors

transmission_coordination_visibilityTransmission-coordination visibility

The trust-dimensions layer records that Pennsylvania shows transmission-coordination visibility through documented participation in PJM's regional electricity-coordination footprint and public transmission-map visibility.

• Pennsylvania inclusion in PJM territory
• public transmission-map coverage from 69 kV to 765 kV

broadband_program_coordinationBroadband-program coordination

The trust-dimensions layer records that Pennsylvania shows broadband-program coordination visibility through approved BEAD planning materials, local-coordination references, and community-anchor planning structure.

• PBDA's 5-Year Action Plan
• approved BEAD proposal volumes
• documented local coordination and community-anchor planning treatment

6. Profile Summary

Derivation constraint. The profile layer records that profile content derives strictly from evidence.md, signals.md, and trust-dimensions.md.

The profile layer records 5 profile subsections with snake_case canonical keys.

corridor_interface_structureCorridor-interface structure

The profile layer records that Pennsylvania currently presents as a corridor-interface jurisdiction where Great Lakes continuity, inland-river logistics, and Mid-Atlantic transition structure intersect inside the documented record.

multimodal_logistics_structureMultimodal logistics structure

The profile layer records that Pennsylvania currently presents with documented multimodal logistics structure across Erie port continuity, Pittsburgh inland-waterway and intermodal activity, Class I rail visibility, interstate corridor presence, and PIT cargo positioning.

research_adjacency_structureResearch-adjacency structure

The profile layer records that Pennsylvania currently presents with strong research adjacency in the documented record through Carnegie Mellon engineering and robotics activity and University of Pittsburgh research scale.

transmission_and_broadband_coordinationTransmission and broadband coordination

The profile layer records that Pennsylvania currently presents with visible regional transmission and broadband-program coordination through PJM participation and PBDA BEAD planning activity.

corridor_linked_industrial_structureCorridor-linked industrial structure

The profile layer records that Pennsylvania currently presents with corridor-linked industrial structure through Erie commercial port industry, Monongahela and Ohio River freight-industrial continuity, and manufacturing materials tied to metallurgy and advanced industry.

7. Builder Mode Summary

Derivation constraint. The builder-mode layer records that builder-mode content derives strictly from normalized jurisdiction layers.

The builder-mode layer records 6 builder interpretation subsections with snake_case canonical keys, including an explicit topology_interpretation_boundary subsection.

corridor_interpretationCorridor interpretation

The builder-mode layer records that Pennsylvania should be interpreted as a transition environment where Great Lakes continuity, inland-river freight structure, and Mid-Atlantic corridor passage meet in the documented record.

logistics_interpretationLogistics interpretation

The builder-mode layer records that Pennsylvania should be interpreted as a multimodal freight environment with visible port, river, rail, highway, and air-cargo anchors, without expanding into a full statewide infrastructure inventory.

research_interpretationResearch interpretation

The builder-mode layer records that Pennsylvania should be interpreted as having strong research adjacency through Carnegie Mellon engineering and robotics visibility and University of Pittsburgh research scale.

transmission_and_broadband_interpretationTransmission and broadband interpretation

The builder-mode layer records that Pennsylvania should be interpreted as having visible regional transmission and broadband-program coordination through PJM participation and PBDA BEAD planning activity.

industrial_interpretationIndustrial interpretation

The builder-mode layer records that Pennsylvania should be interpreted as retaining corridor-linked industrial persistence through Erie commercial-port activity, Pittsburgh river-industrial continuity, and manufacturing-sector visibility tied to metallurgy and advanced industry.

topology_interpretation_boundaryTopology interpretation boundary

The builder-mode layer records that Pennsylvania's jurisdiction lens should inform evidence interpretation, but atlas-controlled corridor group, foundation layer, and topology completion layer remain those recorded in atlas-export/docs/atlas.md unless that canonical source changes first.

8. Structural Exclusions

The canonical package records structural exclusions across the evidence, signals, trust-dimensions, profile, builder-mode, and change-log layers. Multiple layers record a distinct canonical exclusion: local reassignment of atlas-controlled Pennsylvania topology metadata.

Evidence-layer structural exclusions

The evidence layer records that based on the evidence collected there, this file does not support characterizing Pennsylvania as any of the following:

• a Great Lakes Industrial Core topology reassignment case inside atlas-controlled metadata
• a routing-authority jurisdiction
• a coordination-tier jurisdiction
• a deployment-readiness jurisdiction
• a surface-assigned jurisdiction
• a jurisdiction-ranking case
• an AI compute corridor
• a hyperscale anchor corridor
• a federal governance corridor
• a federal hosting corridor
• a national routing spine designation
• a primary Internet-exchange concentration environment
• a digital-asset statutory jurisdiction

Signals-layer structural exclusions

The signals layer records that the current evidence set does not support signal treatment for: Atlas surface assignment, routing-role assignment, coordination-tier classification, deployment-readiness classification, jurisdiction ranking, AI compute-corridor designation, hyperscale-corridor designation, federal-governance-corridor designation, federal-hosting-corridor designation, national routing-spine designation, primary IX concentration classification, atlas-controlled topology reassignment, or digital-asset statutory-jurisdiction designation.

Trust-dimensions structural exclusions

The trust-dimensions layer records that the current evidence and signal set does not support trust-dimension treatment for: Atlas surface assignment, routing-role assignment, coordination-tier classification, deployment-readiness classification, jurisdiction ranking, AI compute-corridor designation, hyperscale-corridor designation, federal-governance-corridor designation, federal-hosting-corridor designation, national routing-spine designation, primary IX concentration classification, atlas-controlled topology reassignment, or digital-asset statutory-jurisdiction designation.

Profile-layer structural exclusions

The profile layer records that the current evidence and signal set does not support profile characterization as: an Atlas surface assignment, a routing-role classification, a coordination-tier classification, a deployment-readiness classification, a jurisdiction-ranking case, an AI compute corridor, a hyperscale anchor corridor, a federal governance corridor, a federal hosting corridor, a national routing spine, a primary IX concentration environment, an atlas-controlled topology reassignment case, or a digital-asset statutory jurisdiction.

Builder-mode structural exclusions

The builder-mode layer records that the current Pennsylvania record does not support builder-mode interpretation as: an Atlas surface assignment, a routing-role assignment, a coordination-tier assignment, a deployment-readiness assignment, a jurisdiction-ranking case, an AI compute corridor, a hyperscale anchor corridor, a federal governance corridor, a federal hosting corridor, a national routing spine, a primary IX concentration environment, a local override of atlas-controlled topology metadata, or a digital-asset statutory jurisdiction.

Change-log structural exclusions

The change-log records that this package population does not authorize: Atlas surface assignment, routing-role assignment, coordination-tier assignment, deployment-readiness assignment, jurisdiction ranking, AI compute-corridor designation, hyperscale-corridor designation, federal governance or hosting-corridor designation, national routing-spine designation, primary IX concentration designation, or local reassignment of atlas-controlled Pennsylvania topology metadata.

9. Scope Boundaries & Canonical Narrowing

The canonical Pennsylvania package does not record an "Evidence gaps" section. Instead, the change-log records the canonical scope-constraints applied during evidence-first package population, explicitly enumerating what was excluded from the package.

Scope constraints applied during population

The change-log records the current status: evidence layer populated to corridor sufficiency, downstream layers derived strictly from the corridor-limited evidence set, jurisdiction lens attached in metadata.md, surface assignment remains none.

10. Change-Log Notes & Normalization Notes

Topology metadata sync

The change-log records that metadata.md was reviewed against atlas-export/docs/atlas.md, with updated fields for Corridor Group, Foundation Layer, and Topology Completion Layer. The change-log records that this sync is structural only and does not alter evidence, signals, trust interpretation, profile, builder-mode, or surface neutrality.

2026-04-15 evidence-first package population

The change-log records that the Pennsylvania state package was populated in topology-normalized order: evidence.md, signals.md, trust-dimensions.md, metadata.md, profile.md, builder-mode.md. The change-log records that scope constraints were applied during population (rendered in Section 9 above). The change-log records the current status: evidence layer populated to corridor sufficiency, downstream layers derived strictly from the corridor-limited evidence set, jurisdiction lens attached in metadata.md, and surface assignment remains none.

Structural exclusions

The change-log records explicit structural exclusions: this package population does not authorize Atlas surface assignment, routing-role assignment, coordination-tier assignment, deployment-readiness assignment, jurisdiction ranking, AI compute-corridor designation, hyperscale-corridor designation, federal governance or hosting-corridor designation, national routing-spine designation, primary IX concentration designation, or local reassignment of atlas-controlled Pennsylvania topology metadata.