North Dakota

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.

Canonical Northern Plains sparse-node topology. The canonical atlas.md places North Dakota in the Northern Plains Sparse-Node Corridor, with a Northern Plains Sparse-Node Layer foundation and a Northern Interior Completion Layer completion. North Dakota's canonical Foundation Layer and Completion Layer are distinct — the Foundation Layer is the Northern Plains Sparse-Node Layer, shared with Montana and South Dakota in the three-state Northern Plains Sparse-Node Corridor cluster, while the Completion Layer is the Northern Interior Completion Layer, shared across the cluster and also reached by Minnesota's Upper Midwest Continuity Corridor. The canonical Jurisdiction Lens uses "within" to reflect that North Dakota's sparse-node Foundation resolves into the broader Northern Interior Completion Layer.

2. Scope Boundary Statement

The evidence layer records that this file records only corridor-relevant structural anchors retained for North Dakota 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 North Dakota package is an adjacency-bounded corridor-layer sufficient package: its evidence is retained from corridor continuity between adjacent Atlas states (Montana, South Dakota, Minnesota) plus a narrow Wyoming-facing western frame visible transitively through Montana, along with 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 4 evidence subsections documenting North Dakota's corridor-relevant structural anchors retained from adjacent-state continuity. Canonical sources are atlas-export internal topology references and adjacent-state metadata-layer files rather than state-sourced primary documents.

Northern plains sparse-node continuity

• The evidence layer records that atlas-export/docs/atlas.md places North Dakota in the Northern Plains Sparse-Node Corridor, with a Northern Plains Sparse-Node Layer foundation and a Northern Interior Completion Layer completion.
• The evidence layer records that Montana is retained in Atlas in the same Northern Plains Sparse-Node Corridor, with the same Northern Plains Sparse-Node Layer foundation and Northern Interior Completion Layer completion.
• The evidence layer records that South Dakota is retained in Atlas in the same Northern Plains Sparse-Node Corridor, with the same Northern Plains Sparse-Node Layer foundation and Northern Interior Completion Layer completion.
• The evidence layer records that Minnesota is retained in Atlas in the Upper Midwest Continuity Corridor, with the same Northern Interior Completion Layer completion.
• The evidence layer records that the retained Atlas topology therefore supports reading North Dakota as a northern-plains sparse-node continuity jurisdiction across the Montana, South Dakota, and Minnesota-facing northern-interior frame.

East-west northern interior continuity

• The evidence layer records that Montana preserves a west-facing Northern Plains Sparse-Node Corridor environment on the same Northern Interior Completion Layer as North Dakota.
• The evidence layer records that Minnesota preserves an east-facing Upper Midwest Continuity Corridor environment on the same Northern Interior Completion Layer as North Dakota.
• The evidence layer records that South Dakota preserves the shared northern-plains sparse-node frame south of North Dakota.
• The evidence layer records that the retained Atlas structure therefore supports an east-west northern interior continuity reading across North Dakota between Montana-facing sparse-node structure and Minnesota-facing northern-interior continuity.

Institutional adjacency continuity across the Montana–South Dakota–Minnesota frame

• The evidence layer records that Montana's retained Atlas placement preserves a west-facing northern-plains sparse-node frame adjacent to North Dakota.
• The evidence layer records that South Dakota's retained Atlas placement preserves a south-facing northern-plains sparse-node frame adjacent to North Dakota.
• The evidence layer records that Minnesota's retained Atlas placement preserves an east-facing upper-midwest northern-interior frame adjacent to North Dakota.
• The evidence layer records that North Dakota's retained position inside this adjacent-state frame supports an institutional adjacency continuity reading at the corridor layer.
• The evidence layer records that under the current corridor-scope restriction, this anchor is retained only as structural adjacency continuity and is not expanded into university-system mapping, research-network inventory treatment, or statewide institutional survey treatment.

Interior adjacency toward the Wyoming-facing western frame

• The evidence layer records that Montana's retained Atlas placement preserves a shared Northern Plains Sparse-Node Corridor frame west of North Dakota.
• The evidence layer records that Wyoming's retained Atlas placement preserves an Interior Western Statutory Flex Corridor frame to the south of Montana, forming the visible western interior contrast frame referenced in the current adjacency-bounded source set.
• The evidence layer records that North Dakota's retained topology therefore supports a narrow interior-adjacency-toward-the-Wyoming-facing-western-frame reading through the visible Montana–Wyoming western structure.
• The evidence layer records that under the current corridor-scope restriction, this anchor is retained only as structural frame adjacency and is not expanded into routing, readiness, or surface-assignment inference.

4. Signals Summary

Derivation constraint. The signals layer records that signals derive strictly from evidence.md.

The signals layer records 4 structural coordination signals directly detectable from the evidence layer.

Northern plains sparse-node continuity signal

The signals layer records that North Dakota shows a northern-plains-sparse-node-continuity signal through retained placement on the Northern Plains Sparse-Node Layer and Northern Interior Completion Layer across the Montana, South Dakota, and Minnesota-facing frame.

East-west northern interior continuity signal

The signals layer records that North Dakota shows an east-west-northern-interior-continuity signal through retained placement between Montana-facing sparse-node structure and Minnesota-facing northern-interior continuity.

Institutional adjacency signal

The signals layer records that North Dakota shows an institutional-adjacency signal through retained placement across the Montana, South Dakota, and Minnesota-facing corridor frame.

Interior adjacency toward Wyoming-facing western frame signal

The signals layer records that North Dakota shows an interior-adjacency-toward-the-Wyoming-facing-western-frame signal through the visible Montana–Wyoming western structure referenced in evidence.md.

5. Trust Dimensions Summary

Derivation constraint. The trust-dimensions layer records that dimensions derive strictly from signals.md.

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

Trust interpretation summary

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

• narrow but durable corridor coordination density across northern plains sparse-node continuity, east-west northern interior continuity, institutional adjacency continuity, and interior adjacency toward the Wyoming-facing western frame
• durable northern-plains continuity with visible east-west northern-interior structure at the corridor layer
• visible institutional adjacency across the Montana–South Dakota–Minnesota frame, with a narrow western interior frame reading through Montana and Wyoming
• industrial persistence not independently established beyond corridor continuity and adjacency
• research participation not independently established beyond institutional adjacency

Coordination density

Narrow but durable corridor coordination density.

• northern plains sparse-node continuity signal
• east-west northern interior continuity signal
• institutional adjacency signal
• interior adjacency toward Wyoming-facing western frame 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 north-south plains continuity between a Canada-facing northern frame and South Dakota-facing interior structure, freight or logistics continuity, rail visibility, energy-grid participation visibility, or BEAD coordination visibility

North Dakota shows corridor-relevant coordination density as a northern-plains sparse-node environment linking Montana-facing western structure, South Dakota-facing plains structure, Minnesota-facing northern-interior continuity, and a narrow Wyoming-facing western frame through the visible Montana–Wyoming structure.

Infrastructure continuity

Durable northern-plains continuity with visible east-west northern-interior structure.

• northern plains sparse-node continuity signal
• east-west northern interior continuity signal
• institutional adjacency signal

• the current package does not independently establish north-south plains continuity between a Canada-facing northern frame and South Dakota-facing interior structure
• the current package does not independently establish freight or logistics continuity
• the current package does not independently establish rail visibility
• the current package does not independently establish energy-grid participation visibility or BEAD coordination visibility
• the current package does not independently establish inland-waterway continuity
• the current package does not expand into statewide infrastructure surveys, port inventories, terminal inventories, or tonnage datasets

North Dakota shows durable corridor continuity where northern-plains sparse-node structure carries across a broader northern interior completion frame, but the package retains that continuity only at the corridor layer.

Institutional adjacency

Visible Montana–South Dakota–Minnesota institutional adjacency with a narrow western interior frame reading.

• institutional adjacency signal
• northern plains sparse-node continuity signal
• east-west northern interior continuity signal
• interior adjacency toward Wyoming-facing western frame signal

• the current package intentionally avoids university-system mapping, research-network inventory treatment, and broader institutional ranking treatment
• the current trust reading does not compare North Dakota institutions by depth, scale, or hierarchy

North Dakota shows institutional adjacency through its retained corridor position between Montana-facing western structure, South Dakota-facing plains continuity, Minnesota-facing northern-interior continuity, and the visible Montana–Wyoming western frame.

Industrial persistence

Not independently established beyond corridor continuity and adjacency.

• northern plains sparse-node continuity signal
• east-west northern interior continuity signal
• institutional adjacency signal

• the current package does not independently establish freight or logistics continuity, rail visibility, port inventories, terminal inventories, tonnage datasets, or broader industrial survey treatment
• the current trust reading does not support industrial ranking or manufacturing-depth claims for North Dakota from the retained corridor evidence alone

North Dakota sits inside a corridor whose retained topology preserves northern-plains sparse-node continuity and east-west northern-interior continuity, but this package does not independently establish North Dakota industrial persistence beyond that adjacency-bounded corridor structure.

Research participation

Not independently established beyond institutional adjacency.

• institutional adjacency signal
• northern plains sparse-node continuity signal

• the current package does not retain a corridor-visible research anchor for North Dakota beyond its adjacency-bounded corridor placement
• 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 North Dakota from the retained corridor evidence alone

North Dakota sits inside a visible northern-interior institutional frame, but the current retained evidence does not independently establish research participation beyond that adjacency 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 North Dakota currently reads within Atlas as a northern-plains and northern-interior continuity environment organized around northern plains sparse-node continuity, east-west northern interior continuity, institutional adjacency continuity, and interior adjacency toward the Wyoming-facing western frame.

Profile synthesis

The profile layer records that the current package shows:

• northern plains sparse-node continuity anchored in retained placement on the Northern Plains Sparse-Node Layer and Northern Interior Completion Layer across the Montana, South Dakota, and Minnesota-facing frame
• east-west northern interior continuity anchored in retained placement between Montana-facing sparse-node structure and Minnesota-facing northern-interior continuity
• institutional adjacency continuity anchored in retained placement across the Montana, South Dakota, and Minnesota-facing corridor frame
• interior adjacency toward the Wyoming-facing western frame anchored in the visible Montana–Wyoming western structure retained in the current corridor-bounded source set
• no independent retained basis for north-south plains continuity between a Canada-facing northern frame and South Dakota-facing interior structure, freight or logistics continuity, rail visibility, energy-grid participation visibility, BEAD coordination visibility, inland-waterway continuity, digital-asset statutory posture, or research participation beyond institutional adjacency under the current corridor-bounded scope

The profile layer records that, taken together, these conditions support a structural characterization of North Dakota as a northern-plains sparse-node continuity corridor within a broader northern interior frame.

Profile synthesis statement

The profile layer records that North Dakota currently reads within Atlas as a northern-plains sparse-node continuity corridor linking Montana-facing and South Dakota-facing plains structure to Minnesota-facing northern-interior continuity, with a narrow western interior frame visible through Montana and Wyoming.

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

Builder mode role summary

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

• a northern plains sparse-node continuity environment
• an east-west northern interior continuity environment
• an institutional adjacency environment across the Montana–South Dakota–Minnesota frame
• a narrow interior adjacency environment toward the Wyoming-facing western frame
• a narrow corridor environment rather than a standalone topology override or readiness case

Northern plains interpretation

The builder-mode layer records that for builder interpretation, North Dakota reads as a northern-plains sparse-node continuity environment where retained placement shares Northern Plains Sparse-Node Layer and Northern Interior Completion Layer continuity with adjacent plains structure without overriding atlas-controlled topology.

East-west continuity interpretation

The builder-mode layer records that for builder interpretation, North Dakota reads as an east-west northern interior continuity environment where retained structure preserves corridor continuity between Montana-facing sparse-node structure and Minnesota-facing northern-interior continuity.

Institutional adjacency interpretation

The builder-mode layer records that for builder interpretation, North Dakota reads as an institutional adjacency environment where retained structure preserves corridor continuity across the Montana–South Dakota–Minnesota frame without expanding into university-system mapping or research-network inventory treatment.

Western frame interpretation

The builder-mode layer records that for builder interpretation, North Dakota reads as a narrow interior adjacency environment toward the Wyoming-facing western frame through the visible Montana–Wyoming western structure retained in the current corridor-bounded source set.

Constraint interpretation

The builder-mode layer records that for builder interpretation, North Dakota should be read narrowly. The current package does not independently establish north-south plains continuity between a Canada-facing northern frame and South Dakota-facing interior structure, freight or logistics continuity, rail visibility, energy-grid participation visibility, BEAD coordination visibility, inland-waterway continuity, 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. The canonical North Dakota structural exclusions set uses the shortened canonical formulation — focused on survey/inventory/mapping-type exclusions — and is preserved verbatim from each canonical layer.

Evidence-layer structural exclusions

The evidence layer records that based on the retained corridor-visible evidence collected there, this file does not support characterizing North Dakota as any of the following:

• a routing-authority jurisdiction
• a coordination-tier jurisdiction
• a deployment-readiness jurisdiction
• a surface-assigned jurisdiction
• a statewide infrastructure-survey case
• a statewide freight-survey case
• a port-inventory or terminal-inventory case
• a municipal-inventory case
• a university-system mapping case
• a research-network inventory case
• an engineering-sector survey case
• an AI compute corridor
• a hyperscale designation
• a jurisdiction-ranking case
• 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 North Dakota 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 designation, a statewide infrastructure-survey case, a statewide freight-survey case, a port-inventory or terminal-inventory case, or a digital-asset statutory jurisdiction. The signals layer records that the current signal set also does not independently establish north-south plains continuity between a Canada-facing northern frame and South Dakota-facing interior structure, freight or logistics continuity, rail visibility, energy-grid participation visibility, BEAD coordination visibility, inland-waterway continuity, or research participation beyond institutional adjacency.

Trust-dimensions structural exclusions

The trust-dimensions layer records that this file does not support interpreting North Dakota 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 designation, or a digital-asset statutory jurisdiction. The trust-dimensions layer records that it should be read as trust interpretation of North Dakota's current structural posture within the normalized Atlas package only.

Profile-layer structural exclusions

The profile layer records that North Dakota'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 designation, a digital-asset statutory jurisdiction claim, or a topology reassignment of atlas-controlled metadata.

Builder-mode structural exclusions

The builder-mode layer records that this file does not support interpreting North Dakota 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 designation, or a digital-asset statutory jurisdiction. The builder-mode layer records that it should be read as builder-facing interpretation of North Dakota'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 designation, digital-asset statutory designation, or local reassignment of atlas-controlled North Dakota topology metadata.

9. Evidence Gaps

The canonical North Dakota evidence layer contains a native "Evidence gaps" subsection.

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, corridor-scope constraints applied throughout package construction, 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-18 evidence-first package population

The change-log records that the North Dakota 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, corridor-scope constraints applied throughout package construction, 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 designation, digital-asset statutory designation, or local reassignment of atlas-controlled North Dakota topology metadata.