Maryland

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 a topology-constrained reading derived from those atlas-controlled fields only and does not override atlas-controlled topology.

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 retained for Maryland from adjacent-state continuity already visible inside Atlas. 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, readiness, or Atlas surfaces.

This rendering mirrors the canonical package. The canonical Maryland package is an adjacency-bounded corridor-layer sufficient package: its evidence is retained from corridor continuity between adjacent rendered Atlas states (Delaware, Pennsylvania, New Jersey, Virginia) and atlas.md topology references, rather than from independent state-sourced research. All completeness statuses across evidence, signals, trust, profile, and builder-mode are canonically recorded as "corridor-layer sufficient".

3. Evidence Summary

The evidence layer records 6 evidence subsections documenting Maryland's corridor-relevant structural anchors retained from adjacent-state continuity. Canonical sources are atlas-export internal topology references and adjacent-state package files (metadata, evidence, and signals layers across Delaware, Pennsylvania, New Jersey, and Virginia) rather than state-sourced primary documents.

Chesapeake Bay continuity

• The evidence layer records that atlas-export/docs/atlas.md places Maryland in the Chesapeake Federal Interface Corridor, the Federal Interface Governance Layer, and the Mid-Atlantic Completion Layer.
• The evidence layer records that Virginia is retained in Atlas inside the same Federal Interface Governance Layer and Mid-Atlantic Completion Layer.
• The evidence layer records that Delaware is retained in Atlas as the neighboring Mid-Atlantic Institutional Bridge Corridor inside the same Mid-Atlantic Completion Layer.
• The evidence layer records that the retained Atlas topology therefore supports reading Maryland as a Chesapeake-facing continuity jurisdiction linking Delaware's northern bridge frame to Virginia's southern federal-interface continuation, without overriding atlas-controlled topology.

Mid-Atlantic institutional bridge continuity

• The evidence layer records that Delaware's retained Atlas package already records Mid-Atlantic institutional bridge continuity between Pennsylvania, New Jersey, and Maryland across Northeast institutional-mesh and Mid-Atlantic completion continuity.
• The evidence layer records that Pennsylvania and New Jersey remain retained northern continuation environments inside the Northeast Institutional Mesh Layer and the Mid-Atlantic Completion Layer.
• The evidence layer records that Maryland's retained position between Delaware's bridge frame and Virginia's federal-interface continuity supports Mid-Atlantic institutional bridge continuity at the corridor layer without overriding atlas-controlled topology.

I-95 / Mid-Atlantic logistics continuity

• The evidence layer records that Pennsylvania's retained Atlas package documents interstate transition-corridor visibility including I-95 inside a freight environment already connected to the Mid-Atlantic completion frame.
• The evidence layer records that Delaware's retained Atlas package already records Mid-Atlantic logistics continuity linking Pennsylvania, New Jersey, and Maryland.
• The evidence layer records that New Jersey's retained Atlas package records New York–Philadelphia freight spine continuity and Mid-Atlantic logistics continuity across the same adjacency frame.
• The evidence layer records that Maryland's retained position south of Delaware inside the same Mid-Atlantic completion environment therefore supports I-95 / Mid-Atlantic logistics continuity at the corridor layer without expanding into statewide freight surveys or logistics rankings.

Northeast Corridor rail visibility

• The evidence layer records that Delaware's retained Atlas package already records Northeast Corridor rail visibility between Pennsylvania, New Jersey, and Maryland.
• The evidence layer records that New Jersey's retained Atlas package retains Northeast Corridor rail visibility across the same Mid-Atlantic / Northeast frame.
• The evidence layer records that Maryland's retained position south of Delaware inside the current Mid-Atlantic completion structure supports Northeast Corridor rail visibility at the corridor layer without expanding into operator, station, service, or asset inventory treatment.

Intermodal freight continuity

• The evidence layer records that Pennsylvania's retained Atlas package already documents corridor-visible interstate and intermodal continuity inside the same Mid-Atlantic completion environment.
• The evidence layer records that Delaware's retained Atlas package records inter-jurisdiction freight spine continuity linking Pennsylvania, New Jersey, and Maryland through retained river, logistics, and rail visibility.
• The evidence layer records that Maryland's retained position south of Delaware therefore supports intermodal freight continuity at the corridor layer without expanding into terminal, yard, or asset-depth treatment.

PJM participation visibility

• The evidence layer records that Pennsylvania's retained Atlas package documents PJM transmission participation in Pennsylvania and other Mid-Atlantic jurisdictions.
• The evidence layer records that the current Virginia Atlas package already records that Virginia's grid environment is linked to PJM participation.
• The evidence layer records that Maryland's retained position between Pennsylvania, Delaware, and Virginia inside the current Mid-Atlantic adjacency frame supports PJM participation visibility at the corridor layer without expanding into transmission-asset inventory or readiness treatment.

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 6 structural coordination signals directly detectable from the evidence layer.

Chesapeake Bay continuity signal

The signals layer records that Maryland shows a Chesapeake-Bay-continuity signal through atlas-retained Chesapeake corridor placement linking Delaware's northern bridge frame to Virginia's federal-interface continuation.

Mid-Atlantic institutional bridge continuity signal

The signals layer records that Maryland shows a Mid-Atlantic-institutional-bridge-continuity signal through retained adjacency between Delaware's institutional-bridge frame, the Pennsylvania / New Jersey northern continuation environment, and Virginia's federal-interface continuity.

I-95 / Mid-Atlantic logistics continuity signal

The signals layer records that Maryland shows an I-95-and-Mid-Atlantic-logistics-continuity signal through retained logistics continuity linking Pennsylvania, Delaware, New Jersey, and the Maryland corridor position.

Northeast Corridor rail visibility signal

The signals layer records that Maryland shows a Northeast-Corridor-rail-visibility signal through retained rail continuity between Delaware and the broader Pennsylvania / New Jersey adjacency frame.

Intermodal freight continuity signal

The signals layer records that Maryland shows an intermodal-freight-continuity signal through retained continuity between Pennsylvania's documented intermodal environment and Delaware's freight-spine continuity linking Maryland into the same Mid-Atlantic frame.

PJM participation visibility signal

The signals layer records that Maryland shows a PJM-participation-visibility signal through retained Mid-Atlantic adjacency between Pennsylvania's documented PJM participation and Virginia's existing PJM-linked package visibility.

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 dimensions reflects absence of normalized signal-layer coverage.

The trust-dimensions layer records that trust evaluates what kinds of stability conditions Maryland can sustain given the signal layer and the visible corridor-continuity environment.

Trust interpretation summary

The trust-dimensions layer records that Maryland currently presents a trust profile characterized by:

• narrow but durable coordination density across Chesapeake continuity, institutional bridge continuity, logistics continuity, rail visibility, and PJM-linked Mid-Atlantic adjacency
• durable but narrow infrastructure continuity through Chesapeake-facing continuity, I-95 logistics, Northeast Corridor rail visibility, intermodal continuity, and PJM visibility
• visible institutional adjacency between Delaware's bridge frame, the Pennsylvania / New Jersey northern continuation environment, and Virginia's federal-interface continuity
• industrial persistence not independently established beyond retained logistics and intermodal continuity
• research participation not independently established beyond institutional adjacency

Coordination density

Narrow but durable corridor coordination density.

• Chesapeake Bay continuity signal
• Mid-Atlantic institutional bridge continuity signal
• I-95 / Mid-Atlantic logistics continuity signal
• Northeast Corridor rail visibility signal
• intermodal freight continuity signal
• PJM participation visibility signal

• the current signal layer does not provide a routing-authority model
• the current package does not support coordination-tier assignment
• the current package does not independently establish National Highway Freight Network visibility or BEAD coordination beyond the retained corridor anchors

Maryland shows corridor-relevant coordination density as a Chesapeake-facing Mid-Atlantic bridge environment linking Delaware's northern bridge continuity to Virginia's federal-interface continuation.

Infrastructure continuity

Durable but narrow bay-logistics-rail continuity.

• Chesapeake Bay continuity signal
• I-95 / Mid-Atlantic logistics continuity signal
• Northeast Corridor rail visibility signal
• intermodal freight continuity signal
• PJM participation visibility signal

• the current package does not independently establish inland-waterway continuity beyond the retained Chesapeake-facing continuity reading
• the current package does not independently establish National Highway Freight Network visibility
• the current package does not independently establish BEAD coordination
• the current package does not expand into port, terminal, statewide freight, or transmission-asset inventory treatment

Maryland shows durable corridor continuity where retained Chesapeake-facing, logistics, rail, intermodal, and PJM-linked structure connect the northern Mid-Atlantic frame to the Virginia continuation environment.

Institutional adjacency

Visible institutional adjacency.

• Mid-Atlantic institutional bridge continuity signal
• Chesapeake Bay continuity signal

• the current package intentionally avoids university-system inventory or broader institutional ranking treatment
• the current trust reading does not compare Maryland institutions by depth, scale, or hierarchy

Maryland shows institutional adjacency through its retained placement between Delaware's institutional-bridge frame and Virginia's federal-interface continuity inside the Mid-Atlantic completion environment.

Industrial persistence

Not independently established beyond retained logistics and intermodal continuity.

• I-95 / Mid-Atlantic logistics continuity signal
• intermodal freight continuity signal
• Chesapeake Bay continuity signal

• the current package intentionally excludes port inventories, terminal inventories, tonnage datasets, and statewide industrial survey treatment
• the current trust reading does not support industrial ranking or manufacturing-depth claims for Maryland from the retained corridor evidence alone

Maryland may sit inside a corridor with visible logistics and intermodal continuity, but this package does not independently establish Maryland industrial persistence beyond the retained Chesapeake-facing and freight-continuity anchors.

Research participation

Not independently established beyond institutional adjacency.

• Mid-Atlantic institutional bridge continuity signal

• the current package intentionally avoids university-system mapping and research-network inventory treatment
• the current trust reading does not support a research-hierarchy claim for Maryland from the retained corridor evidence alone

Maryland sits inside a visible Mid-Atlantic institutional adjacency frame, but the current retained evidence does not independently establish Maryland research participation beyond that corridor position.

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 that profile is the characterization layer of the package.

Jurisdiction summary

The profile layer records that Maryland currently reads within Atlas as a Chesapeake-facing Mid-Atlantic jurisdiction organized around Chesapeake Bay continuity, Mid-Atlantic institutional bridge continuity, I-95 / Mid-Atlantic logistics continuity, Northeast Corridor rail visibility, intermodal freight continuity, and PJM participation visibility.

Profile synthesis

The profile layer records that the current package shows:

• Chesapeake Bay continuity anchored in atlas-retained Chesapeake corridor placement linking Delaware's northern bridge frame to Virginia's federal-interface continuation
• Mid-Atlantic institutional bridge continuity anchored in retained adjacency between Delaware's bridge frame, the Pennsylvania / New Jersey northern continuation environment, and Maryland's Chesapeake-facing position
• I-95 / Mid-Atlantic logistics continuity anchored in retained Pennsylvania, Delaware, and New Jersey logistics continuity carried through the Maryland corridor position
• Northeast Corridor rail visibility anchored as retained rail continuity between Delaware and the broader Pennsylvania / New Jersey adjacency frame extending through Maryland's Mid-Atlantic placement
• intermodal freight continuity anchored in retained Pennsylvania intermodal visibility and Delaware freight-spine continuity carried into the Maryland corridor frame
• PJM participation visibility anchored in retained Mid-Atlantic adjacency between Pennsylvania's documented PJM participation and Virginia's existing PJM-linked package visibility
• no independent retained basis for inland-waterway continuity beyond the retained Chesapeake-facing continuity reading, National Highway Freight Network visibility, BEAD coordination, or digital-asset statutory posture under the current adjacency-bounded scope

The profile layer records that, taken together, these conditions support a structural characterization of Maryland as a Chesapeake-facing Mid-Atlantic institutional and logistics continuity corridor.

Profile synthesis statement

The profile layer records that Maryland currently reads within Atlas as a Chesapeake-facing Mid-Atlantic institutional and logistics continuity corridor linking retained bay continuity, bridge adjacency, logistics, rail, intermodal, and PJM-linked structure inside the existing adjacency frame.

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 that this file provides structural interpretation only, and does not rank Maryland, compare Maryland to other jurisdictions, or prescribe deployment eligibility.

Builder mode role summary

The builder-mode layer records that Maryland is best understood for builder purposes as:

• a Chesapeake Bay continuity environment
• a Mid-Atlantic institutional bridge continuity environment
• an I-95 / Mid-Atlantic logistics continuity environment
• a Northeast Corridor rail continuity environment
• an intermodal freight continuity environment
• a PJM-linked Mid-Atlantic continuity environment rather than a standalone topology override or readiness case

Chesapeake interpretation

The builder-mode layer records that for builder interpretation, Maryland reads as a Chesapeake-facing continuity environment where retained topology links Delaware's northern bridge frame to Virginia's federal-interface continuation without expanding into port, terminal, or inland-waterway asset inventory treatment.

Institutional bridge interpretation

The builder-mode layer records that for builder interpretation, Maryland reads as a Mid-Atlantic institutional bridge environment where retained adjacency links Delaware, the Pennsylvania / New Jersey northern continuation environment, and Virginia's federal-interface continuity.

Logistics interpretation

The builder-mode layer records that for builder interpretation, Maryland reads as a logistics-continuity environment where retained I-95-linked corridor structure carries the Pennsylvania, Delaware, and New Jersey freight frame through Maryland without expanding into statewide freight survey or ranking treatment.

Northeast Corridor interpretation

The builder-mode layer records that for builder interpretation, Maryland reads as a rail continuity environment where retained corridor visibility extends south from Delaware and the broader Pennsylvania / New Jersey frame without expanding into operator, station, or asset inventory treatment.

Intermodal and PJM interpretation

The builder-mode layer records that for builder interpretation, Maryland reads as an intermodal and PJM-linked continuity environment where retained Mid-Atlantic freight and grid-adjacency structure are visible without expanding into terminal inventories, transmission-asset inventories, or readiness claims.

Constraint interpretation

The builder-mode layer records that for builder interpretation, Maryland should be read narrowly. The current package does not independently establish inland-waterway continuity beyond the retained Chesapeake-facing continuity reading, National Highway Freight Network visibility, BEAD coordination, digital-asset statutory posture, or any deployment or routing posture.

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 Maryland topology metadata. Maryland's canonical structural exclusions lists do not include "federal governance corridor" — the canonical exclusions are adjusted to avoid self-contradiction with Maryland's Federal Interface Governance Layer Foundation classification.

Evidence-layer structural exclusions

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

• 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 hosting corridor
• a national routing spine designation
• a primary Internet-exchange concentration environment
• a custody-regime jurisdiction
• a DAO-wrapper jurisdiction
• a digital-asset statutory jurisdiction

Signals-layer structural exclusions

The signals layer records that based on the currently derived signals, this file does not support characterizing Maryland as any of the following: a routing-authority jurisdiction, a coordination-tier jurisdiction, a deployment-readiness jurisdiction, a surface-eligibility determination, a jurisdiction-ranking claim, an AI compute corridor, a hyperscale anchor corridor, a federal hosting corridor, a national routing spine designation, a primary Internet-exchange concentration environment, a custody-regime jurisdiction, a DAO-wrapper jurisdiction, or a digital-asset statutory jurisdiction. The signals layer records that the current signal set also does not independently establish inland-waterway continuity beyond the retained Chesapeake-facing continuity reading, National Highway Freight Network visibility, or BEAD coordination for Maryland.

Trust-dimensions structural exclusions

The trust-dimensions layer records that this file does not support interpreting Maryland as any of the following: a routing-authority jurisdiction, a coordination-tier jurisdiction, a deployment-readiness jurisdiction, an Atlas surface-eligibility determination, a jurisdiction-ranking case, an AI compute corridor, a hyperscale anchor corridor, a federal hosting corridor, a national routing spine designation, a primary Internet-exchange concentration environment, a custody-regime jurisdiction, a DAO-wrapper jurisdiction, or a digital-asset statutory jurisdiction. The trust-dimensions layer records that it should be read as trust interpretation of Maryland's current structural posture within the normalized Atlas package only.

Profile-layer structural exclusions

The profile layer records that Maryland's profile should not be read as: a routing-authority assignment, a coordination-tier assignment, a deployment-readiness classification, an Atlas surface-eligibility determination, a jurisdiction ranking claim, an AI compute corridor claim, a hyperscale anchor corridor claim, a federal hosting corridor claim, a national routing spine claim, a primary Internet-exchange concentration claim, a custody-regime jurisdiction claim, a DAO-wrapper jurisdiction claim, a digital-asset statutory jurisdiction claim, or a topology reassignment of atlas-controlled metadata.

Builder-mode structural exclusions

The builder-mode layer records that the current Maryland record does not support builder-mode interpretation as any of the following: a routing-authority jurisdiction, a coordination-tier jurisdiction, a deployment-readiness jurisdiction, an Atlas surface-eligibility determination, a jurisdiction-ranking case, an AI compute corridor, a hyperscale anchor corridor, a federal hosting corridor, a national routing spine designation, a primary Internet-exchange concentration environment, a custody-regime jurisdiction, a DAO-wrapper jurisdiction, or a digital-asset statutory jurisdiction. The builder-mode layer records that it should be read as builder-facing interpretation of Maryland's current structural posture within the normalized Atlas package only.

Change-log 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 hosting-corridor designation, national routing-spine designation, primary Internet-exchange concentration designation, or local reassignment of atlas-controlled Maryland topology metadata.

9. Evidence Gaps

The canonical Maryland evidence layer contains a native "Evidence gaps" subsection. The change-log also records: "Evidence gaps retained where adjacency-bounded Atlas structure did not independently confirm broader anchors."

Evidence gaps from the evidence layer

Scope constraints applied during population

The change-log records the current status: topology metadata synced to atlas-export/docs/atlas.md, evidence layer populated to corridor sufficiency, evidence gaps retained where adjacency-bounded Atlas structure did not independently confirm broader anchors, downstream layers derived strictly from corridor-limited evidence, 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, Topology Completion Layer, and Jurisdiction lens. 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-17 evidence-first package population

The change-log records that the Maryland state package was populated in topology-normalized order as a numbered canonical sequence: evidence.md, signals.md, trust-dimensions.md, metadata.md, profile.md, builder-mode.md, change-log.md. The change-log records that scope constraints were applied during population (rendered in Section 9 above). The change-log records the current status: topology metadata synced to atlas-export/docs/atlas.md, evidence layer populated to corridor sufficiency, evidence gaps retained where adjacency-bounded Atlas structure did not independently confirm broader anchors, downstream layers derived strictly from corridor-limited evidence, 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 hosting-corridor designation, national routing-spine designation, primary Internet-exchange concentration designation, or local reassignment of atlas-controlled Maryland topology metadata.