Maine

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 terminal-edge topology. The canonical atlas.md places Maine in the Northeast Terminal Edge Corridor, the Northeast Completion Layer, and the Northeast Terminal Completion Layer. Unlike Rhode Island, Vermont, and New Hampshire — whose canonical Foundation Layer and Completion Layer are the same layer (Northeast Completion Layer) — Maine's canonical Foundation Layer and Completion Layer are distinct. Maine's Foundation Layer is the Northeast Completion Layer (shared with its Northeast Institutional Support Corridor siblings), while Maine's Completion Layer is the Northeast Terminal Completion Layer — a distinct layer whose only canonical member is Maine. Maine therefore reads within Atlas as the terminal-edge state where one canonical Completion Layer resolves into another, and the Jurisdiction Lens uses "transition into" rather than "within" to reflect the layer transition rather than the topology-collapse pattern.

2. Scope Boundary Statement

The evidence layer records that this file records only corridor-relevant structural anchors retained for Maine 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 Maine package is an adjacency-bounded corridor-layer sufficient package: its evidence is retained from corridor continuity between adjacent Atlas states (New Hampshire, Vermont, Massachusetts, New York) 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 4 evidence subsections documenting Maine's corridor-relevant structural anchors retained from adjacent-state continuity. Canonical sources are atlas-export internal topology references and adjacent-state package files (including New Hampshire at metadata, evidence, and signals levels) rather than state-sourced primary documents.

Northeast terminal-edge continuity

• 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 Atlas in the Northeast Institutional Support Corridor and the Northeast Completion Layer immediately upstream of Maine's terminal completion placement.
• The evidence layer records that Vermont is retained in Atlas in the same Northeast Institutional Support Corridor and Northeast Completion Layer as part of the northern Northeast support frame.
• 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 Maine as the terminal-edge continuation of the northern Northeast frame, without overriding atlas-controlled topology.

Terminal completion continuity beyond the northern Northeast support frame

• The evidence layer records that New Hampshire's retained Atlas package already records continuation into Maine's northern completion structure from the northern Northeast support frame.
• The evidence layer records that atlas-export/docs/atlas.md places Maine in the Northeast Terminal Completion Layer, beyond the Northeast Completion Layer carried by New Hampshire and Vermont.
• The evidence layer records that Maine's retained terminal placement therefore supports terminal completion continuity beyond the northern Northeast support frame at the corridor layer without overriding atlas-controlled topology.

Continuation from New Hampshire's northern support continuity

• The evidence layer records that New Hampshire's retained Atlas package already records northern Northeast institutional support continuity and inland northward continuity inside the northern Northeast frame.
• The evidence layer records that Maine's retained position beyond New Hampshire at the terminal edge supports continuation from New Hampshire's northern support continuity 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 statewide infrastructure or freight inventory treatment.

Terminal-position institutional adjacency

• The evidence layer records that New Hampshire's retained Atlas package already records a northern institutional-support frame linked to Massachusetts' research-bearing continuity and the broader New York-facing Northeast structure.
• The evidence layer records that Maine's retained terminal-edge position beyond New Hampshire therefore supports terminal-position institutional adjacency at the corridor layer within the same northern Northeast frame.
• The evidence layer records that under the current corridor-scope restriction, this anchor is retained only as structural institutional adjacency and is not expanded into university-system mapping or research-network 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 4 structural coordination signals directly detectable from the evidence layer.

Northeast terminal-edge continuity signal

The signals layer records that Maine shows a Northeast-terminal-edge-continuity signal through atlas-retained terminal placement beyond the New Hampshire and Vermont support frame inside the broader New York-facing Northeast structure.

Terminal completion continuity signal

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

Continuation from New Hampshire support continuity signal

The signals layer records that Maine shows a continuation-from-New-Hampshire-support-continuity signal through retained continuation from New Hampshire's northern support-position continuity into the Maine corridor position.

Terminal-position institutional adjacency signal

The signals layer records that Maine shows a terminal-position-institutional-adjacency signal through retained institutional adjacency beyond the New Hampshire support frame within the northern Northeast structure.

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

Trust interpretation summary

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

• narrow but durable corridor coordination density across terminal-edge continuity, terminal completion continuity, continuation from New Hampshire support continuity, and terminal-position institutional adjacency
• durable but narrow infrastructure continuity through terminal-edge and terminal completion continuity
• visible institutional adjacency between New Hampshire's support continuity, Massachusetts' research-bearing continuity, and the broader New York-facing frame at the northern edge of the Northeast structure
• industrial persistence not independently established beyond terminal-edge and completion continuity
• research participation not independently established beyond adjacency to the northern Northeast support and research-bearing frame

Coordination density

Narrow but durable corridor coordination density.

• Northeast terminal-edge continuity signal
• terminal completion continuity signal
• continuation from New Hampshire support continuity signal
• terminal-position institutional adjacency 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 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

Maine shows corridor-relevant coordination density as a terminal-edge environment where the northern Northeast support frame resolves into terminal completion continuity.

Infrastructure continuity

Durable but narrow terminal-edge-and-completion continuity.

• Northeast terminal-edge continuity signal
• terminal completion continuity signal
• continuation from New Hampshire support continuity signal

• 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

Maine shows durable corridor continuity where retained northern support continuity transitions into terminal completion structure at the edge of the Northeast frame.

Institutional adjacency

Visible terminal-position institutional adjacency.

• continuation from New Hampshire support continuity signal
• terminal-position institutional adjacency signal
• terminal completion continuity signal

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

Maine shows institutional adjacency through its retained terminal-edge position beyond New Hampshire's support continuity inside the broader northern Northeast frame.

Industrial persistence

Not independently established beyond terminal-edge and completion continuity.

• Northeast terminal-edge continuity signal
• terminal completion continuity signal

• 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 Maine from the retained corridor evidence alone

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

Research participation

Not independently established beyond northern-frame adjacency.

• terminal-position institutional adjacency signal
• continuation from New Hampshire support 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 Maine from the retained corridor evidence alone

Maine sits adjacent to the northern Northeast support and research-bearing frame, but the current retained evidence does not independently establish Maine research participation beyond that corridor position.

6. Profile Summary

Derivation constraint. The profile layer records that profile content derives strictly from evidence.md, signals.md, and trust-dimensions.md. The profile layer records that profile is the characterization layer of the package.

Jurisdiction summary

The profile layer records that Maine currently reads within Atlas as a Northeast terminal-edge jurisdiction organized around Northeast terminal-edge continuity, terminal completion continuity beyond the northern Northeast support frame, continuation from New Hampshire's northern support continuity, and terminal-position institutional adjacency inside the broader northern Northeast structure.

Profile synthesis

The profile layer records that the current package shows:

• Northeast terminal-edge continuity anchored in atlas-retained terminal placement beyond the New Hampshire and Vermont support frame inside the broader New York-facing Northeast structure
• terminal completion continuity beyond the northern Northeast support frame anchored in retained continuity between New Hampshire's support-position continuity and Maine's terminal completion structure
• continuation from New Hampshire's northern support continuity anchored in retained continuation from the New Hampshire northern support frame into the Maine corridor position
• terminal-position institutional adjacency anchored in retained institutional adjacency beyond the New Hampshire support frame within the broader northern Northeast structure
• 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 Maine as a Northeast terminal-edge continuity corridor.

Profile synthesis statement

The profile layer records that Maine currently reads within Atlas as a Northeast terminal-edge continuity corridor where retained northern support continuity resolves into terminal completion structure at the edge of the broader northern Northeast 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 Maine, compare Maine to other jurisdictions, or prescribe deployment eligibility.

Builder mode role summary

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

• a Northeast terminal-edge continuity environment
• a terminal completion continuity environment beyond the northern Northeast support frame
• a continuation environment from New Hampshire's northern support continuity
• a terminal-position institutional adjacency environment inside the broader northern Northeast structure
• a narrow terminal-edge environment rather than a standalone topology override or readiness case

Terminal-edge interpretation

The builder-mode layer records that for builder interpretation, Maine reads as a terminal-edge environment where retained corridor placement carries the northern Northeast frame to its terminal boundary without overriding atlas-controlled topology.

Completion interpretation

The builder-mode layer records that for builder interpretation, Maine reads as a terminal completion environment where retained structure continues beyond the New Hampshire support frame into the Northeast Terminal Completion Layer without expanding into statewide freight or terminal inventory treatment.

New Hampshire continuation interpretation

The builder-mode layer records that for builder interpretation, Maine reads as a continuation environment where New Hampshire's retained northern support continuity extends into the Maine corridor frame without expanding into statewide infrastructure survey treatment.

Institutional adjacency interpretation

The builder-mode layer records that for builder interpretation, Maine reads as a terminal-position institutional adjacency environment where retained structure preserves adjacency to the broader northern Northeast support and research-bearing frame without expanding into university-system mapping or research-network inventory treatment.

Constraint interpretation

The builder-mode layer records that for builder interpretation, Maine 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.

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

Evidence-layer structural exclusions

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

Trust-dimensions structural exclusions

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

Profile-layer structural exclusions

The profile layer records that Maine'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 Maine 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 Maine'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 Maine topology metadata.

9. Evidence Gaps

The canonical Maine 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 Maine 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 Maine topology metadata.