Minnesota

1. Topology Metadata

Classification source. The metadata layer records that this metadata is derived from atlas.md and records Atlas corridor-topology placement only.

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

2. Scope Boundary Statement

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

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

The change-log explicitly records that "No evidence gaps section was required" — indicating that absence of an evidence-gaps subsection is itself a canonical decision rather than an omission.

3. Evidence Summary

The evidence layer records 9 evidence subsections documenting Minnesota's corridor-relevant structural anchors across Duluth/Superior and Lake Superior continuity, Upper Mississippi freight continuity, inland waterway and bulk cargo structure, Class I rail, interstate freight corridors, intermodal freight structure, University of Minnesota engineering research, MISO transmission, and BEAD broadband coordination.

Duluth-Superior and Lake Superior continuity

• The evidence layer records that MnDOT states Minnesota's marine freight system plays a vital role in the state's multimodal freight transportation system and that the Great Lakes-St. Lawrence Seaway provides access to other Great Lakes ports and the Atlantic Ocean.
• The evidence layer records that MnDOT states Minnesota has three ports on Lake Superior and identifies Duluth/Superior as one of the state's active Lake Superior ports.
• The evidence layer records that MnDOT states Minnesota's Lake Superior ports handled 56.1 million tons in 2019, with Duluth/Superior alone accounting for 33.5 million tons.
• The evidence layer records that MnDOT states commodities handled by Duluth/Superior include taconite, western coal, grain, cement, salt, steel, limestone, and wind generator components.

Upper Mississippi freight continuity

• The evidence layer records that MnDOT states Minnesota shipped over 14 million tons of commodities down the Mississippi River in 2020.
• The evidence layer records that MnDOT states the Mississippi River system stretches over 195 miles in Minnesota and supports four port areas whose combined 2019 tonnage was 11 million net tons.
• The evidence layer records that MnDOT states the Mississippi River provides access to river ports to the south and the Gulf of Mexico via New Orleans.
• The evidence layer records that MnDOT states the river accounts for over 50 percent of Minnesota's agricultural exports.

Inland waterway and bulk cargo structure

• The evidence layer records that MnDOT states Minnesota's river ports handle grain, fertilizer, cement, sand and gravel, salt, coal, steel, scrap metals, petroleum, caustic soda, vegetable oils, molasses, and anhydrous ammonia.
• The evidence layer records that MnDOT states the U.S. Army Corps of Engineers dredges the Mississippi River channel for 9-foot-deep barges and operates the Upper Mississippi locks and dams.
• The evidence layer records that MnDOT states Great Lakes taconite shipped from Minnesota amounted to 42.2 million tons in 2019 and represented 75 percent of Minnesota's Great Lakes tonnage that year.
• The evidence layer records that MnDOT states Duluth/Superior also handles grain, cement, salt, steel, limestone, and wind generator components, confirming bulk-cargo rather than passenger-only waterborne structure.

Class I rail visibility

• The evidence layer records that MnDOT states Minnesota has 4,278 route miles of railroads serviced by 21 railroad companies.
• The evidence layer records that MnDOT lists four Class I railroads serving Minnesota: BNSF Railway, Canadian National, Canadian Pacific Kansas City Southern, and Union Pacific.
• The evidence layer records that MnDOT states the Minnesota freight rail system is a critical part of the state's multimodal transportation system and provides efficient connections to markets beyond state borders and to the Great Lakes.

Interstate freight corridor continuity

• The evidence layer records that MnDOT states the I-35 and I-90 interchange near Albert Lea is the meeting point of two interstates that are part of the National Highway Freight Network.
• The evidence layer records that MnDOT states the Minnesota Highway Freight Program funds projects that improve freight transportation safety, mobility, efficiency, and access to freight facilities, including first-and-last-mile connections, and maintains a National Highway Freight Network in Minnesota project map.
• The evidence layer records that MnDOT's freight project-selection page lists freight-program activity on I-94, including truck-parking expansion at the Enfield and Big Spunk Lake rest areas and I-94 and Highway 24 improvements.
• The evidence layer records that the retained corridor evidence therefore confirms direct freight-program visibility for I-35, I-90, and I-94 without expanding into a full statewide highway inventory.

Intermodal freight structure

• The evidence layer records that MnDOT states the Minnesota freight system is multimodal in nature and includes highway, rail, waterway, intermodal, and air-cargo transportation.
• The evidence layer records that MnDOT's freight data page provides a statewide intermodal terminals map and states its Freight Network Optimization Tool allows users to analyze and visualize the Minnesota intermodal freight network.
• The evidence layer records that MnDOT's freight data page also points to a freight facilities database intended to support integrated multimodal transportation planning.

University of Minnesota engineering and applied research visibility

• The evidence layer records that the University of Minnesota Twin Cities states it is a top 10 U.S. public research university with more than 2.1 million square feet of research space and $1.35 billion in research expenditures.
• The evidence layer records that the University of Minnesota College of Science and Engineering states research across its 12 departments and multiple research centers addresses major scientific and engineering problems.
• The evidence layer records that the same college states it maintains industry research partnerships, including sponsored and non-sponsored support for faculty research, industry use of research facilities, and technology-transfer activity.

MISO transmission participation

• The evidence layer records that MISO states its long-range transmission plan focuses on regional system solutions to enhance grid reliability and efficiency, and that approved Tranche 1 and Tranche 2.1 portfolios address the MISO Midwest subregion.
• The evidence layer records that the Minnesota Public Utilities Commission states MISO approved a $10.3 billion investment package of 18 transmission projects, three of which are entirely or partially located in Minnesota.
• The evidence layer records that the same Minnesota PUC page lists Minnesota Tranche One projects including Big Stone South-Alexandria-Big Oaks, Mankato to Mississippi, and Northland Reliability.

Minnesota BEAD and broadband coordination

• The evidence layer records that the Minnesota Governor's Task Force on Broadband states the Office of Broadband Development works directly with NTIA to ensure effective design and implementation of the Broadband Equity, Access and Deployment (BEAD) and Digital Equity Act programs.
• The evidence layer records that the same report states new federal BEAD mandates will require greater statewide coordination and collaboration to ensure funds are invested in unserved and underserved communities.
• The evidence layer records that the same report states OBD issued a request for proposal for a broadband cost-gap analysis to determine funding needed under BEAD for Minnesota service targets.

4. Signals Summary

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

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

Lake Superior continuity signal

The signals layer records that Minnesota shows a Lake-Superior-continuity signal through documented Duluth/Superior port activity, documented Lake Superior tonnage, and documented Great Lakes-Seaway access.

Upper Mississippi freight continuity signal

The signals layer records that Minnesota shows an Upper-Mississippi-freight-continuity signal through documented river tonnage, documented 195-mile Mississippi-system visibility, and documented southbound river access toward the Gulf of Mexico.

Inland bulk-cargo structure signal

The signals layer records that Minnesota shows an inland-bulk-cargo-structure signal through directly documented bulk and liquid commodity handling on both the Mississippi River system and the Lake Superior port system.

Class I rail visibility signal

The signals layer records that Minnesota shows a Class-I-rail-visibility signal through directly documented presence of BNSF, Canadian National, CPKC, and Union Pacific in the retained source set.

Interstate freight corridor continuity signal

The signals layer records that Minnesota shows an interstate-freight-corridor-continuity signal through directly documented National Highway Freight Network visibility at I-35 and I-90 plus documented freight-program activity along I-94.

Intermodal freight structure signal

The signals layer records that Minnesota shows an intermodal-freight-structure signal through directly documented statewide intermodal terminals mapping, a documented intermodal freight-network optimization tool, and documented multimodal freight-system framing.

Research-institution engineering visibility signal

The signals layer records that Minnesota shows a research-institution-engineering-visibility signal through directly documented University of Minnesota Twin Cities research scale, CSE research activity, and industry research partnership channels.

MISO transmission participation signal

The signals layer records that Minnesota shows a MISO-transmission-participation signal through directly documented MISO Midwest long-range transmission planning and directly documented Minnesota Tranche One transmission projects under state review.

Broadband coordination signal

The signals layer records that Minnesota shows a broadband-coordination signal through directly documented Office of Broadband Development work with NTIA on BEAD and Digital Equity programs plus directly documented statewide coordination requirements tied to BEAD deployment.

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

Trust interpretation summary

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

• durable western Great Lakes and Upper Mississippi continuity through Duluth/Superior, Lake Superior, and Mississippi-system freight structure
• durable infrastructure continuity through waterways, Class I rail, interstate freight corridors, intermodal structure, and transmission-planning visibility
• visible institutional adjacency through University of Minnesota engineering research and Office of Broadband Development / PUC-linked support layers
• visible industrial persistence through bulk-cargo and multimodal freight continuity
• sufficient support-layer visibility through MISO participation and BEAD coordination

Coordination density

Durable corridor coordination density.

• Lake Superior continuity signal
• Upper Mississippi freight continuity signal
• Class I rail visibility signal
• interstate freight corridor continuity signal
• intermodal freight structure signal

• the current signal layer does not provide a routing-authority model
• the current package does not support corridor hierarchy or coordination-tier assignment

Minnesota shows corridor-relevant coordination density where Lake Superior ports, Upper Mississippi freight continuity, Class I rail visibility, interstate freight corridors, and intermodal structure are all directly documented.

Infrastructure continuity

Durable multimodal continuity.

• Lake Superior continuity signal
• Upper Mississippi freight continuity signal
• inland bulk-cargo structure signal
• Class I rail visibility signal
• interstate freight corridor continuity signal
• intermodal freight structure signal
• MISO transmission participation signal
• broadband coordination signal

• the current package does not establish a full statewide infrastructure inventory beyond the corridor-layer anchors
• the current evidence does not support compute-corridor, hyperscale, or deployment-readiness interpretation

Minnesota shows durable continuity across Lake Superior and Upper Mississippi freight structure, Class I rail, interstate freight corridors, intermodal freight structure, MISO-linked transmission planning, and BEAD coordination.

Institutional adjacency

Visible but narrow institutional adjacency.

• research-institution engineering visibility signal
• MISO transmission participation signal
• broadband coordination signal

• the current package intentionally avoids a complete university inventory
• the current trust reading does not compare institutions by rank or statewide breadth

Minnesota shows corridor-relevant institutional adjacency through University of Minnesota engineering visibility and through state-linked transmission and broadband coordination structures.

Industrial persistence

Visible logistics-linked industrial persistence.

• inland bulk-cargo structure signal
• Lake Superior continuity signal
• Upper Mississippi freight continuity signal
• Class I rail visibility signal
• intermodal freight structure signal

• the current package does not provide a statewide plant-by-plant industrial map
• the current trust reading does not support economic-ranking or sector-leadership narratives

Minnesota shows industrial persistence where recurring bulk-cargo, waterway, rail, and intermodal structure remain coupled to documented commodity movement across Lake Superior and Upper Mississippi systems.

Research participation

Visible research participation.

• research-institution engineering visibility signal

• the current package intentionally limits research treatment to University of Minnesota engineering and applied research visibility only
• the current trust reading does not support frontier-AI, statewide research-network, or federal-lab classification

Minnesota shows research participation sufficient for corridor interpretation through University of Minnesota research and engineering visibility, without expanding into a broader statewide research-hierarchy claim.

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 Minnesota currently reads within Atlas as an Upper Midwest continuity jurisdiction organized around Duluth/Superior and Lake Superior freight continuity, Upper Mississippi freight continuity, Class I rail and interstate corridor visibility, intermodal freight structure, University of Minnesota engineering visibility, MISO transmission participation, and BEAD coordination.

Profile synthesis

The profile layer records that the current package shows:

• Duluth/Superior and Lake Superior continuity anchored in documented Great Lakes-Seaway access, documented Lake Superior port tonnage, and documented bulk-cargo handling
• Upper Mississippi continuity anchored in documented river tonnage, documented port-area continuity, and documented southbound waterway access toward the Gulf
• inland bulk-cargo structure anchored in documented commodity movement across river and lake systems
• Class I rail visibility anchored in directly documented BNSF, Canadian National, CPKC, and Union Pacific presence
• interstate freight corridor continuity anchored in directly documented I-35 and I-90 National Highway Freight Network visibility plus freight-program activity along I-94
• intermodal freight structure anchored in MnDOT's documented intermodal terminals mapping and intermodal network-optimization tooling
• University of Minnesota engineering and applied research visibility as the package's research anchor
• MISO participation and BEAD coordination as the package's support-layer anchors

The profile layer records that, taken together, these conditions support a structural characterization of Minnesota as an Upper Mississippi + western Great Lakes logistics continuity corridor.

Profile synthesis statement

The profile layer records that Minnesota currently reads within Atlas as an Upper Mississippi + western Great Lakes logistics continuity corridor linking Duluth/Superior and Lake Superior freight structure, Upper Mississippi continuity, Class I rail visibility, I-35/I-90/I-94 freight-corridor visibility, intermodal structure, University of Minnesota engineering research, MISO-linked transmission planning, and BEAD coordination.

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

Builder mode role summary

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

• a Duluth/Superior and Lake Superior logistics continuity environment
• an Upper Mississippi freight continuity environment
• a multimodal inland corridor environment across Class I rail, intermodal structure, and I-35/I-90/I-94 freight visibility
• a corridor environment with visible University of Minnesota engineering participation
• a corridor environment with narrow but explicit MISO and BEAD support-layer continuity

Great Lakes interpretation

The builder-mode layer records that for builder interpretation, Minnesota reads as a western Great Lakes continuity environment where Duluth/Superior and the Lake Superior port system keep bulk-freight structure visible without requiring a statewide port inventory.

River interpretation

The builder-mode layer records that for builder interpretation, Minnesota reads as an Upper Mississippi continuity environment where documented river tonnage, port-area structure, and southbound waterway access remain structurally relevant.

Inland transport interpretation

The builder-mode layer records that for builder interpretation, Minnesota reads as an inland transport environment where Class I rail visibility, intermodal structure, and freight-program visibility across I-35, I-90, and I-94 reinforce corridor continuity.

Research and support-layer interpretation

The builder-mode layer records that for builder interpretation, Minnesota reads as a corridor environment with visible University of Minnesota engineering participation and narrow but explicit support-layer continuity through MISO transmission planning and BEAD coordination.

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

Evidence-layer structural exclusions

The evidence layer records that based on the evidence collected there, this file does not support characterizing Minnesota 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 Minnesota 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.

Trust-dimensions structural exclusions

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

Profile-layer structural exclusions

The profile layer records that Minnesota'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, or a digital-asset statutory jurisdiction claim.

Builder-mode structural exclusions

The builder-mode layer records that this file does not support interpreting Minnesota 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 Minnesota'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 IX concentration designation, or local reassignment of atlas-controlled Minnesota topology metadata.

9. Scope Boundaries & Canonical Narrowing

The canonical Minnesota package does not record an "Evidence gaps" section. The change-log explicitly records "No evidence gaps section was required" — making this an intentional canonical decision rather than an omission. Instead, the change-log records the canonical scope-constraints applied during evidence-first package population.

Scope constraints applied during population

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

10. Change-Log Notes & Normalization Notes

Topology metadata sync

The change-log records that metadata.md was reviewed against atlas-export/docs/atlas.md, with updated fields for Corridor Group, Foundation Layer, 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-15 evidence-first package population

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

Structural exclusions

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