Atlas · Jurisdiction Intelligence Engine · U.S. State Record

New Hampshire

This page renders the canonical New Hampshire Atlas jurisdiction package. The canonical package positions New Hampshire within the Northeast Institutional Support Corridor under the canonical jurisdiction lens "Northeast institutional support continuity within Northeast completion" — a topology-constrained reading derived exclusively from the three atlas-controlled topology fields and identical to Rhode Island's and Vermont's canonical lenses. New Hampshire completes the three-state Northeast Institutional Support Corridor cluster (Rhode Island, Vermont, New Hampshire). New Hampshire is an adjacency-bounded corridor-layer sufficient state — its evidence layer is retained from corridor continuity between adjacent Atlas states rather than from independent state-sourced research. All completeness statuses are recorded as corridor-layer sufficient.

Jurisdiction: New Hampshire (NH · US-NH)
Jurisdiction lens: Northeast institutional support continuity within Northeast completion
Completeness: corridor-layer sufficient
Surface assignment: none
Adjacency-bounded package

1. Topology Metadata

Corridor Group
Northeast Institutional Support Corridor
Foundation Layer
Northeast Completion Layer
Completion Layer
Northeast Completion Layer
Jurisdiction Lens
Northeast institutional support continuity within Northeast completion

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.

Canonical topology collapse. The canonical atlas.md places New Hampshire in the Northeast Institutional Support Corridor, the Northeast Completion Layer, and the Northeast Completion Layer — the Foundation Layer and Topology Completion Layer are the same layer. The evidence layer quotes this canonical configuration verbatim from atlas.md. This matches the canonical topology-collapse pattern established across the full Northeast Institutional Support Corridor cluster (Rhode Island, Vermont, New Hampshire). Because all three cluster members share identical atlas-controlled topology fields, their canonical Jurisdiction Lenses are identical — New Hampshire's canonical lens is the same as Rhode Island's and Vermont's.

Metadata status: topology metadata attached · Surface assignment status: none
Source: metadata.md · atlas_converted.md (Corridor Group, Foundation Layer, Topology Completion Layer)

2. Scope Boundary Statement

The evidence layer records that this file records only corridor-relevant structural anchors retained for New Hampshire 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 Hampshire package is an adjacency-bounded corridor-layer sufficient package: its evidence is retained from corridor continuity between adjacent Atlas states (Massachusetts, Vermont, New York, Maine) 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".

Evidence completeness status: corridor-layer sufficient · Surface assignment status: none
Source: evidence.md — Scope; change-log.md — Scope constraints applied during population

3. Evidence Summary

The evidence layer records 4 evidence subsections documenting New Hampshire's corridor-relevant structural anchors retained from adjacent-state continuity. Canonical sources are atlas-export internal topology references and adjacent-state package files (including forward-chained adjacency reference to Maine's metadata.md) rather than state-sourced primary documents.

Northern Northeast institutional support continuity

  • The evidence layer records that atlas-export/docs/atlas.md places New Hampshire in the Northeast Institutional Support Corridor, the Northeast Completion Layer, and the Northeast Completion Layer.
  • The evidence layer records that Vermont is retained in Atlas inside the same Northeast Institutional Support Corridor and Northeast Completion Layer.
  • The evidence layer records that Massachusetts is retained in Atlas as a neighboring Northeast Research Mesh Corridor jurisdiction inside the same Northeast Completion Layer.
  • The evidence layer records that New York is retained in Atlas as the adjacent northeastern anchor environment.
  • The evidence layer records that the retained Atlas topology therefore supports reading New Hampshire as a northern Northeast institutional-support continuity jurisdiction inside the Massachusetts, Vermont, and New York-facing frame, without overriding atlas-controlled topology.
Canonical sources
  • atlas-export/docs/atlas.md
  • atlas-export/jurisdictions/us/states/massachusetts/metadata.md
  • atlas-export/jurisdictions/us/states/vermont/metadata.md
  • atlas-export/jurisdictions/us/states/new-york/metadata.md

Continuation from Massachusetts' research-bearing Northeast structure

  • The evidence layer records that Massachusetts' retained Atlas package already records that Massachusetts functions as the research-bearing continuation of the Northeast institutional mesh.
  • The evidence layer records that New Hampshire's retained position north of Massachusetts inside the Northeast Completion Layer supports continuation from that research-bearing Northeast structure at the corridor layer.
  • The evidence layer records that under the current corridor-scope restriction, this anchor is retained only as structural continuation and is not expanded into university-system mapping or research-network inventory treatment.
Canonical sources
  • atlas-export/jurisdictions/us/states/massachusetts/evidence.md
  • atlas-export/jurisdictions/us/states/massachusetts/signals.md
  • atlas-export/docs/atlas.md

Continuation into Maine's northern completion structure

  • The evidence layer records that atlas-export/docs/atlas.md places Maine in the Northeast Terminal Edge Corridor, the Northeast Completion Layer, and the Northeast Terminal Completion Layer.
  • The evidence layer records that New Hampshire is retained in the Northeast Institutional Support Corridor and the Northeast Completion Layer between Massachusetts / Vermont continuity and Maine's terminal completion structure.
  • The evidence layer records that New Hampshire's retained position therefore supports continuation into Maine's northern completion structure at the corridor layer without overriding atlas-controlled topology.
Canonical sources
  • atlas-export/docs/atlas.md
  • atlas-export/jurisdictions/us/states/maine/metadata.md
  • atlas-export/jurisdictions/us/states/massachusetts/metadata.md
  • atlas-export/jurisdictions/us/states/vermont/metadata.md

Inland northward continuity inside the northern Northeast frame

  • The evidence layer records that Vermont's retained Atlas package already records inland Northeast continuity inside the northern Northeast frame between Massachusetts, New York, and New Hampshire continuity.
  • The evidence layer records that New Hampshire's retained support position alongside Vermont and north of Massachusetts supports inland northward continuity inside the same northern Northeast frame.
  • The evidence layer records that under the current corridor-scope restriction, this anchor is retained only as structural inland continuity and is not expanded into statewide freight or infrastructure inventory treatment.
Canonical sources
  • atlas-export/jurisdictions/us/states/vermont/evidence.md
  • atlas-export/jurisdictions/us/states/vermont/signals.md
  • atlas-export/jurisdictions/us/states/massachusetts/evidence.md
  • atlas-export/jurisdictions/us/states/new-york/metadata.md
  • atlas-export/docs/atlas.md
Evidence completeness status: corridor-layer sufficient · Surface assignment status: none
Source: evidence.md — 4 evidence subsections with canonical atlas-export path citations (including forward-chained adjacency reference to Maine's metadata.md and canonical citations of Vermont's evidence.md and signals.md)

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

Northern Northeast institutional support continuity signal

The signals layer records that New Hampshire shows a northern-Northeast-institutional-support-continuity signal through atlas-retained placement inside the Massachusetts, Vermont, and New York-facing northern Northeast frame.

Northward research-bearing continuation signal

The signals layer records that New Hampshire shows a northward-research-bearing-continuation signal through retained continuation from Massachusetts' research-bearing Northeast structure into the New Hampshire corridor position.

Maine completion-continuation signal

The signals layer records that New Hampshire shows a Maine-completion-continuation signal through retained support-position continuity between the northern Northeast completion frame and Maine's terminal completion structure.

Inland northward continuity signal

The signals layer records that New Hampshire shows an inland-northward-continuity signal through retained inland continuity linking Vermont, Massachusetts, and the New York-facing northern Northeast frame.

Canonical signal-layer non-establishment

The signals layer records that the current signal set also does not independently establish coastal adjacency continuity within the Gulf of Maine frame, Class I rail visibility, National Highway Freight Network visibility, ISO-NE participation, or BEAD coordination for New Hampshire.

Signal completeness status: corridor-layer sufficient · Surface assignment status: none
Source: signals.md — 4 signal clusters

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

Trust interpretation summary

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

  • narrow but durable corridor coordination density across northern institutional-support continuity, research-bearing continuation, Maine-directed completion continuity, and inland northward continuity
  • durable but narrow infrastructure continuity through inland northward continuity and Maine-directed completion continuity
  • visible institutional adjacency between Massachusetts' research-bearing continuity, Vermont's support continuity, Maine's terminal completion direction, and the broader New York-facing frame
  • industrial persistence not independently established beyond inland and completion continuity
  • research participation not independently established beyond adjacency to Massachusetts' research-bearing structure

Coordination density

Current interpretation

Narrow but durable corridor coordination density.

Supporting basis
  • northern Northeast institutional support continuity signal
  • northward research-bearing continuation signal
  • Maine completion-continuation signal
  • inland northward continuity signal
Constraint basis
  • 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 coastal adjacency continuity within the Gulf of Maine frame, Class I rail visibility, National Highway Freight Network visibility, ISO-NE participation, or BEAD coordination beyond the retained corridor anchors
Atlas reading

New Hampshire shows corridor-relevant coordination density as a northern support-position environment linking Massachusetts' research-bearing continuity, Vermont's inland support continuity, and Maine's terminal completion direction inside the broader New York-facing frame.

Infrastructure continuity

Current interpretation

Durable but narrow inland-and-completion continuity.

Supporting basis
  • inland northward continuity signal
  • Maine completion-continuation signal
Constraint basis
  • the current package does not independently establish coastal adjacency continuity within the Gulf of Maine frame
  • the current package does not independently establish Class I rail corridor visibility
  • the current package does not independently establish National Highway Freight Network visibility
  • the current package does not independently establish ISO-NE participation or BEAD coordination
  • the current package does not expand into statewide freight or asset inventory treatment
Atlas reading

New Hampshire shows durable corridor continuity where retained inland structure carries the northern Northeast frame toward Maine's terminal completion environment.

Institutional adjacency

Current interpretation

Visible institutional adjacency.

Supporting basis
  • northern Northeast institutional support continuity signal
  • northward research-bearing continuation signal
  • Maine completion-continuation signal
Constraint basis
  • the current package intentionally avoids university-system inventory or broader institutional ranking treatment
  • the current trust reading does not compare New Hampshire institutions by depth, scale, or hierarchy
Atlas reading

New Hampshire shows institutional adjacency through its retained support position between Massachusetts' research-bearing continuity, Vermont's inland support continuity, and the transition toward Maine's terminal completion structure.

Industrial persistence

Current interpretation

Not independently established beyond inland and completion continuity.

Supporting basis
  • inland northward continuity signal
  • Maine completion-continuation signal
Constraint basis
  • the current package intentionally excludes statewide freight surveys, terminal inventories, tonnage datasets, and statewide industrial survey treatment
  • the current trust reading does not support industrial ranking or manufacturing-depth claims for New Hampshire from the retained corridor evidence alone
Atlas reading

New Hampshire may sit inside a corridor with visible inland and completion continuity, but this package does not independently establish New Hampshire industrial persistence beyond the retained inland and Maine-directed completion anchors.

Research participation

Current interpretation

Not independently established beyond northward research-bearing adjacency.

Supporting basis
  • northward research-bearing continuation signal
  • northern Northeast institutional support continuity signal
Constraint basis
  • 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 Hampshire from the retained corridor evidence alone
Atlas reading

New Hampshire sits adjacent to a research-bearing Northeast continuation environment, but the current retained evidence does not independently establish New Hampshire research participation beyond that corridor position.

Trust-dimension completeness status: corridor-layer sufficient · Surface assignment status: none
Source: trust-dimensions.md — Trust interpretation summary + 5 dimension fields (4-field pattern: current / supporting / constraint / Atlas reading)

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 Hampshire currently reads within Atlas as a northern Northeast institutional-support jurisdiction organized around northern Northeast institutional support continuity, continuation from Massachusetts' research-bearing Northeast structure, continuation into Maine's northern completion structure, and inland northward continuity inside the northern Northeast frame.

Profile synthesis

The profile layer records that the current package shows:

  • northern Northeast institutional support continuity anchored in atlas-retained support-corridor placement inside the Massachusetts, Vermont, and New York-facing northern Northeast frame
  • continuation from Massachusetts' research-bearing Northeast structure anchored in retained northward continuation from Massachusetts' research-mesh position into the New Hampshire corridor frame
  • continuation into Maine's northern completion structure anchored in retained support-position continuity between the northern Northeast completion frame and Maine's terminal completion structure
  • inland northward continuity anchored in retained inland continuity linking Vermont, Massachusetts, and the New York-facing northern Northeast frame
  • no independent retained basis for coastal adjacency continuity within the Gulf of Maine frame, Class I rail corridor visibility, National Highway Freight Network visibility, ISO-NE 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 Hampshire as a northern Northeast institutional-support continuity corridor.

Profile synthesis statement

The profile layer records that New Hampshire currently reads within Atlas as a northern Northeast institutional-support continuity corridor linking retained inland continuity, research-bearing adjacency, and Maine-directed completion structure inside the existing northern Northeast frame.

Profile completeness status: corridor-layer sufficient · Surface assignment status: none
Source: profile.md — Jurisdiction summary + Profile synthesis + Profile synthesis statement

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 Hampshire, compare New Hampshire to other jurisdictions, or prescribe deployment eligibility.

Builder mode role summary

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

  • a northern Northeast institutional support continuity environment
  • a continuation environment from Massachusetts' research-bearing Northeast structure
  • a continuation environment into Maine's northern completion structure
  • an inland northward continuity environment inside the northern Northeast frame
  • a narrow northern support-position environment rather than a standalone topology override or readiness case

Institutional support interpretation

The builder-mode layer records that for builder interpretation, New Hampshire reads as a northern institutional-support environment where retained corridor placement links Massachusetts' research-bearing continuity, Vermont's inland support continuity, and the broader New York-facing frame.

Massachusetts continuation interpretation

The builder-mode layer records that for builder interpretation, New Hampshire reads as a northward continuation environment where Massachusetts' retained research-bearing Northeast structure carries into the New Hampshire corridor frame without expanding into university-system mapping or research-network inventory treatment.

Maine continuation interpretation

The builder-mode layer records that for builder interpretation, New Hampshire reads as a completion-transition environment where retained structure carries the northern Northeast frame toward Maine's terminal completion structure without overriding atlas-controlled topology.

Inland continuity interpretation

The builder-mode layer records that for builder interpretation, New Hampshire reads as an inland continuity environment where retained structure links Vermont, Massachusetts, and the New York-facing northern Northeast frame without expanding into statewide freight or asset inventory treatment.

Constraint interpretation

The builder-mode layer records that for builder interpretation, New Hampshire should be read narrowly. The current package does not independently establish coastal adjacency continuity within the Gulf of Maine frame, Class I rail corridor visibility, National Highway Freight Network visibility, ISO-NE participation, BEAD coordination, digital-asset statutory posture, or any deployment or routing posture.

Builder-mode completeness status: corridor-layer sufficient · Surface assignment status: none
Source: builder-mode.md — Role summary + 5 interpretation subsections (including canonical Constraint interpretation)

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 Hampshire topology metadata.

Evidence-layer structural exclusions

The evidence layer records that based on the evidence collected there, this file does not support characterizing New Hampshire 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 Hampshire 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 coastal adjacency continuity within the Gulf of Maine frame, Class I rail visibility, National Highway Freight Network visibility, ISO-NE participation, or BEAD coordination for New Hampshire.

Trust-dimensions structural exclusions

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

Profile-layer structural exclusions

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

Source: evidence.md, signals.md, trust-dimensions.md, profile.md, builder-mode.md, change-log.md — Structural exclusions

9. Evidence Gaps

The canonical New Hampshire 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

The evidence layer records

The current adjacency-bounded Atlas structure does not independently establish the following New Hampshire anchors for retention in this package:

  • coastal adjacency continuity within the Gulf of Maine frame
  • Class I rail corridor visibility
  • National Highway Freight Network corridor visibility
  • ISO-NE participation visibility
  • BEAD coordination visibility
  • digital-asset statutory posture

Scope constraints applied during population

The change-log records the following scope constraints applied during evidence-first package population:
  • adjacent-state corridor continuity only
  • no open infrastructure research
  • corridor-layer anchors only
  • no statewide infrastructure survey or statewide freight survey
  • no municipal inventories, university-system inventory, research-network inventory, or engineering-sector survey
  • no tonnage datasets, terminal inventories, or port inventories
  • no workforce, tourism, agriculture, lifestyle, or economic-ranking treatment
  • no compute-corridor or hyperscale inference
  • no routing-authority, coordination-tier, readiness, ranking, or surface assignment inference
  • no local override of atlas-controlled topology metadata

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.

Source: evidence.md — Evidence gaps; change-log.md — 2026-04-17 evidence-first package population (Scope constraints applied)

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

Normalization status: corridor-layer sufficient · Surface assignment status: none
Source: change-log.md