New Jersey

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 New Jersey 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 New Jersey package is an adjacency-bounded corridor-layer sufficient package: its evidence is retained from corridor continuity between adjacent rendered Atlas states (New York, Pennsylvania, Delaware) 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 5 evidence subsections documenting New Jersey'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) rather than state-sourced primary documents.

Northeast institutional bridge continuity

• The evidence layer records that atlas-export/docs/atlas.md places New Jersey in the Northeast Institutional Mesh Corridor, the Northeast Institutional Mesh Layer, and the Mid-Atlantic Completion Layer.
• The evidence layer records that New York is retained in Atlas as the adjacent northeastern anchor environment.
• The evidence layer records that Pennsylvania is retained in Atlas inside the same Northeast Institutional Mesh Layer and Mid-Atlantic Completion Layer.
• The evidence layer records that Delaware is retained in Atlas as the neighboring Mid-Atlantic institutional bridge environment inside the same Northeast Institutional Mesh Layer and Mid-Atlantic Completion Layer.
• The evidence layer records that the retained Atlas topology therefore supports reading New Jersey as an institutional bridge between the New York anchor environment and the Pennsylvania / Delaware Mid-Atlantic continuity frame, without overriding atlas-controlled topology.

New York–Philadelphia freight spine 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 inter-jurisdiction freight spine continuity linking Pennsylvania, New Jersey, and Maryland through retained river, logistics, and rail visibility.
• The evidence layer records that New Jersey's retained placement between New York's anchor environment and Pennsylvania / Delaware corridor continuity supports a New York–Philadelphia freight spine continuity reading at the corridor layer.
• The evidence layer records that under the current corridor-scope restriction, this anchor is retained only as inter-jurisdiction freight-spine continuity and is not expanded into port, terminal, tonnage, or statewide freight inventory treatment.

Delaware River continuity

• The evidence layer records that Delaware's retained Atlas package already records Delaware River continuity between Pennsylvania and New Jersey at the corridor layer.
• The evidence layer records that Pennsylvania and Delaware remain retained neighboring jurisdictions inside the same Northeast Institutional Mesh Layer and Mid-Atlantic Completion Layer adjacency frame used for New Jersey.
• The evidence layer records that New Jersey's corridor position inside that retained frame supports Delaware River continuity without expanding into port, terminal, or tonnage treatment.

Mid-Atlantic logistics continuity

• The evidence layer records that Pennsylvania's retained Atlas package already records corridor-visible interstate and logistics continuity inside the same Mid-Atlantic completion environment.
• The evidence layer records that Delaware's retained Atlas package already records Mid-Atlantic logistics continuity and inter-jurisdiction freight spine continuity linking Pennsylvania, New Jersey, and Maryland.
• The evidence layer records that New Jersey's retained position between New York's anchor environment and the Pennsylvania / Delaware Mid-Atlantic frame therefore supports 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 position between New York and the Pennsylvania / Delaware adjacency frame supports Northeast Corridor rail visibility inside the current Mid-Atlantic / Northeast corridor structure.
• The evidence layer records that under the current corridor-scope restriction, this anchor is retained only as corridor-visible rail continuity and is not expanded into operator, station, service, or asset inventory 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 5 structural coordination signals directly detectable from the evidence layer.

Northeast institutional bridge continuity signal

The signals layer records that New Jersey shows a Northeast-institutional-bridge-continuity signal through atlas-retained placement between New York's anchor environment and the Pennsylvania / Delaware Mid-Atlantic continuation frame.

New York–Philadelphia freight spine continuity signal

The signals layer records that New Jersey shows a New-York-Philadelphia-freight-spine-continuity signal through retained freight-spine continuity linking the New York anchor environment to Pennsylvania corridor continuity across the New Jersey position.

Delaware River continuity signal

The signals layer records that New Jersey shows a Delaware-River-continuity signal through retained river continuity with Pennsylvania and Delaware inside the current Mid-Atlantic adjacency frame.

Mid-Atlantic logistics continuity signal

The signals layer records that New Jersey shows a Mid-Atlantic-logistics-continuity signal through retained logistics continuity across the Pennsylvania, Delaware, and New York-facing corridor frame.

Northeast Corridor rail visibility signal

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

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 New Jersey can sustain given the signal layer and the visible corridor-continuity environment.

Trust interpretation summary

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

• narrow but durable corridor coordination density across Northeast institutional continuity and Mid-Atlantic completion continuity
• durable but narrow infrastructure continuity through freight-spine, river, logistics, and rail visibility
• visible institutional adjacency between New York's anchor environment and the Pennsylvania / Delaware corridor frame
• industrial persistence not independently established beyond retained freight and logistics continuity
• research participation not independently established beyond institutional adjacency

Coordination density

Narrow but durable corridor coordination density.

• Northeast institutional bridge continuity signal
• New York–Philadelphia freight spine continuity signal
• Delaware River continuity signal
• Mid-Atlantic logistics continuity signal
• Northeast Corridor rail 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, PJM participation, or BEAD coordination beyond the retained corridor anchors

New Jersey shows corridor-relevant coordination density as a bridge environment linking New York's anchor continuity with Pennsylvania and Delaware inside the retained Mid-Atlantic completion structure.

Infrastructure continuity

Durable but narrow freight-river-rail continuity.

• New York–Philadelphia freight spine continuity signal
• Delaware River continuity signal
• Mid-Atlantic logistics continuity signal
• Northeast Corridor rail visibility signal

• the current package does not independently establish National Highway Freight Network visibility
• the current package does not independently establish intermodal freight continuity beyond the retained freight-spine reading
• the current package does not independently establish PJM participation or BEAD coordination
• the current package does not expand into port, terminal, or statewide freight inventory treatment

New Jersey shows durable corridor continuity where retained freight-spine, river, logistics, and rail structure connect the New York-facing and Pennsylvania / Delaware-facing sides of the current Mid-Atlantic / Northeast frame.

Institutional adjacency

Visible institutional adjacency.

• Northeast institutional bridge continuity signal

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

New Jersey shows institutional adjacency through its retained placement inside the Northeast institutional mesh and the Mid-Atlantic completion environment between New York and the Pennsylvania / Delaware corridor structures.

Industrial persistence

Not independently established beyond retained freight and logistics continuity.

• New York–Philadelphia freight spine continuity signal
• Mid-Atlantic logistics continuity signal
• Delaware River 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 New Jersey from the retained corridor evidence alone

New Jersey may sit inside a corridor with visible freight and logistics continuity, but this package does not independently establish New Jersey industrial persistence beyond the retained freight-spine, river, and logistics anchors.

Research participation

Not independently established beyond institutional adjacency.

• Northeast 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 New Jersey from the retained corridor evidence alone

New Jersey sits inside an institutional bridge environment, but the current retained evidence does not independently establish New Jersey research participation beyond adjacency to neighboring corridor structures.

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 New Jersey currently reads within Atlas as a Northeast institutional-mesh jurisdiction organized around New York–Philadelphia freight spine continuity, Delaware River continuity, Mid-Atlantic logistics continuity, Northeast Corridor rail visibility, and institutional bridge adjacency between New York and the Pennsylvania / Delaware corridor frame.

Profile synthesis

The profile layer records that the current package shows:

• Northeast institutional bridge continuity anchored in atlas-retained placement between New York's anchor environment and the Pennsylvania / Delaware Mid-Atlantic continuation frame
• New York–Philadelphia freight spine continuity anchored as retained corridor freight structure linking the New York-facing and Pennsylvania-facing sides of the current adjacency frame
• Delaware River continuity anchored as retained inter-jurisdiction river structure carried through the Pennsylvania / Delaware / New Jersey corridor frame
• Mid-Atlantic logistics continuity anchored in retained adjacency to Pennsylvania and Delaware corridor-visible logistics structure inside the Mid-Atlantic completion environment
• Northeast Corridor rail visibility anchored as retained rail continuity between New York and the Pennsylvania / Delaware adjacency frame
• no independent retained basis for National Highway Freight Network visibility, intermodal freight continuity beyond the retained freight-spine reading, PJM participation, 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 New Jersey as a New York–Philadelphia freight spine + Delaware River institutional mesh continuity corridor.

Profile synthesis statement

The profile layer records that New Jersey currently reads within Atlas as a New York–Philadelphia freight spine + Delaware River institutional mesh continuity corridor linking retained freight, river, logistics, and rail continuity inside the existing Mid-Atlantic / Northeast 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 New Jersey, compare New Jersey to other jurisdictions, or prescribe deployment eligibility.

Builder mode role summary

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

• a New York–Philadelphia freight spine continuity environment
• a Delaware River continuity environment
• a Mid-Atlantic logistics continuity environment
• a Northeast Corridor rail continuity environment
• a Northeast institutional bridge environment between New York and the Pennsylvania / Delaware corridor frame rather than a standalone topology override or readiness case

Freight spine interpretation

The builder-mode layer records that for builder interpretation, New Jersey reads as a corridor-spine environment where retained continuity links New York-facing adjacency to Pennsylvania freight continuity across the current Mid-Atlantic / Northeast frame.

Delaware River interpretation

The builder-mode layer records that for builder interpretation, New Jersey reads as a river-continuity environment where retained adjacency links Pennsylvania and Delaware across the current corridor frame without expanding into port, terminal, or tonnage treatment.

Mid-Atlantic logistics interpretation

The builder-mode layer records that for builder interpretation, New Jersey reads as a logistics-continuity environment where retained corridor structure links the Pennsylvania / Delaware frame to New York-facing adjacency without expanding into statewide freight survey or ranking treatment.

Northeast Corridor interpretation

The builder-mode layer records that for builder interpretation, New Jersey reads as a rail continuity environment where retained corridor visibility links New York to the Pennsylvania / Delaware adjacency frame without expanding into operator, station, or asset inventory treatment.

Institutional adjacency interpretation

The builder-mode layer records that for builder interpretation, New Jersey reads as an institutional bridge environment inside the Northeast institutional mesh, with adjacency value derived from corridor position rather than from ranking or statewide institutional mapping.

Constraint interpretation

The builder-mode layer records that for builder interpretation, New Jersey should be read narrowly. The current package does not independently establish National Highway Freight Network visibility, intermodal freight continuity beyond the retained freight-spine reading, PJM participation, 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 New Jersey topology metadata.

Evidence-layer structural exclusions

The evidence layer records that based on the evidence collected there, this file does not support characterizing New Jersey 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 governance 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 New Jersey 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 governance 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 National Highway Freight Network visibility, intermodal freight continuity beyond the retained freight-spine reading, PJM participation, or BEAD coordination for New Jersey.

Trust-dimensions structural exclusions

The trust-dimensions layer records that this file does not support interpreting New Jersey 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 governance 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 New Jersey's current structural posture within the normalized Atlas package only.

Profile-layer structural exclusions

The profile layer records that New Jersey'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 governance 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 New Jersey 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 governance 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 New Jersey'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 governance or hosting-corridor designation, national routing-spine designation, primary Internet-exchange concentration designation, or local reassignment of atlas-controlled New Jersey topology metadata.

9. Evidence Gaps

The canonical New Jersey 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 New Jersey 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 governance or hosting-corridor designation, national routing-spine designation, primary Internet-exchange concentration designation, or local reassignment of atlas-controlled New Jersey topology metadata.