Vermont

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 topology collapse. The canonical atlas.md places Vermont 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 first established for Rhode Island, reflecting the canonical meaning of the Northeast Institutional Support Corridor as a support-position continuity environment that exists at the Completion Layer without independent Foundation-Layer scaffolding. Vermont's canonical Jurisdiction Lens is identical to Rhode Island's because both states share all three atlas-controlled topology fields.

2. Scope Boundary Statement

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

Inland Northeast continuity

• The evidence layer records that atlas-export/docs/atlas.md places Vermont in the Northeast Institutional Support Corridor, the Northeast Completion Layer, and the Northeast Completion Layer.
• The evidence layer records that New Hampshire 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 Vermont as an inland continuity jurisdiction inside the northern Northeast frame, without overriding atlas-controlled topology.

Institutional adjacency continuity within the northern Northeast frame

• The evidence layer records that Massachusetts' retained Atlas package already situates its Northeast research-bearing continuity inside a broader New York-facing Northeast frame.
• The evidence layer records that Vermont's retained support-corridor placement alongside New Hampshire inside the same Northeast Completion Layer supports institutional adjacency continuity within the 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.

Northward 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 Vermont's retained position north of Massachusetts inside the same Northeast Completion Layer supports a northward continuation reading 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.

East-west bridge continuity between New York-facing and New Hampshire-facing Northeast structure

• The evidence layer records that New York is retained in Atlas as the adjacent northeastern anchor environment.
• The evidence layer records that New Hampshire is retained in Atlas inside the same Northeast Institutional Support Corridor and Northeast Completion Layer as Vermont.
• The evidence layer records that Massachusetts' retained Atlas package already situates the northern Northeast frame within the broader New York-facing continuity environment.
• The evidence layer records that Vermont's retained inland support position therefore supports east-west bridge continuity between New York-facing and New Hampshire-facing Northeast structure at the corridor layer.

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.

Inland Northeast continuity signal

The signals layer records that Vermont shows an inland-Northeast-continuity signal through atlas-retained placement inside the northern Northeast frame between Massachusetts, New York, and New Hampshire continuity.

Northern Northeast institutional adjacency continuity signal

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

Northward research-bearing continuation signal

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

East-west bridge continuity signal

The signals layer records that Vermont shows an east-west-bridge-continuity signal through retained inland continuity between the New York-facing and New Hampshire-facing sides of the northern Northeast frame.

5. Trust Dimensions Summary

Derivation constraint. The trust-dimensions layer records that dimensions derive strictly from signals.md. The trust-dimensions layer records that absence of dimensions reflects absence of normalized signal-layer coverage.

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

Trust interpretation summary

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

• narrow but durable corridor coordination density across inland continuity, institutional adjacency continuity, northward research-bearing continuation, and east-west bridge continuity
• durable but narrow infrastructure continuity through inland and bridge-position continuity
• visible institutional adjacency within the northern Northeast frame between Massachusetts, New York, and New Hampshire continuity
• industrial persistence not independently established beyond inland and bridge-position continuity
• research participation not independently established beyond northward adjacency to Massachusetts' research-bearing structure

Coordination density

Narrow but durable corridor coordination density.

• inland Northeast continuity signal
• northern Northeast institutional adjacency continuity signal
• northward research-bearing continuation signal
• east-west bridge continuity 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 Class I rail visibility, National Highway Freight Network visibility, ISO-NE participation, or BEAD coordination beyond the retained corridor anchors

Vermont shows corridor-relevant coordination density as an inland northern-Northeast support environment linking Massachusetts' research-bearing continuation to New Hampshire-facing and New York-facing continuity.

Infrastructure continuity

Durable but narrow inland-and-bridge continuity.

• inland Northeast continuity signal
• east-west bridge continuity signal

• 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

Vermont shows durable corridor continuity where retained inland and bridge-position structure connect the Massachusetts, New York-facing, and New Hampshire-facing sides of the northern Northeast frame.

Institutional adjacency

Visible institutional adjacency.

• northern Northeast institutional adjacency continuity signal
• northward research-bearing continuation signal

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

Vermont shows institutional adjacency through its retained support position inside the northern Northeast frame between Massachusetts' research-bearing continuity and adjacent New York-facing and New Hampshire-facing structure.

Industrial persistence

Not independently established beyond inland and bridge-position continuity.

• inland Northeast continuity signal
• east-west bridge 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 Vermont from the retained corridor evidence alone

Vermont may sit inside a corridor with visible inland continuity, but this package does not independently establish Vermont industrial persistence beyond the retained inland and east-west bridge anchors.

Research participation

Not independently established beyond northward research-bearing adjacency.

• northward research-bearing continuation signal
• northern Northeast institutional adjacency 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 Vermont from the retained corridor evidence alone

Vermont sits adjacent to a research-bearing Northeast continuation environment, but the current retained evidence does not independently establish Vermont 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 Vermont currently reads within Atlas as a northern Northeast institutional-support jurisdiction organized around inland Northeast continuity, institutional adjacency continuity within the northern Northeast frame, northward continuation from Massachusetts' research-bearing Northeast structure, and east-west bridge continuity between New York-facing and New Hampshire-facing Northeast structure.

Profile synthesis

The profile layer records that the current package shows:

• inland Northeast continuity anchored in atlas-retained support-corridor placement inside the northern Northeast frame between Massachusetts, New York, and New Hampshire continuity
• institutional adjacency continuity anchored in Vermont's retained support position within the northern Northeast frame linking Massachusetts, New York-facing, and New Hampshire-facing structure
• northward continuation from Massachusetts' research-bearing Northeast structure anchored in retained continuation from Massachusetts' research-mesh position into the Vermont corridor frame
• east-west bridge continuity anchored in retained inland continuity between New York-facing and New Hampshire-facing Northeast structure
• no independent retained basis for 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 Vermont as an inland northern Northeast institutional-support continuity corridor.

Profile synthesis statement

The profile layer records that Vermont currently reads within Atlas as an inland northern Northeast institutional-support continuity corridor linking retained inland continuity, institutional adjacency, and east-west bridge structure inside the existing 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 Vermont, compare Vermont to other jurisdictions, or prescribe deployment eligibility.

Builder mode role summary

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

• an inland Northeast continuity environment
• a northern Northeast institutional adjacency continuity environment
• a northward continuation environment from Massachusetts' research-bearing Northeast structure
• an east-west bridge continuity environment between New York-facing and New Hampshire-facing Northeast structure
• a narrow inland support-position environment rather than a standalone topology override or readiness case

Inland continuity interpretation

The builder-mode layer records that for builder interpretation, Vermont reads as an inland continuity environment where retained corridor placement links the Massachusetts, New York-facing, and New Hampshire-facing sides of the northern Northeast frame.

Institutional adjacency interpretation

The builder-mode layer records that for builder interpretation, Vermont reads as an institutional support environment where adjacency value is derived from corridor position between Massachusetts' research-bearing continuity and neighboring New York-facing and New Hampshire-facing structure.

Northward continuation interpretation

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

East-west bridge interpretation

The builder-mode layer records that for builder interpretation, Vermont reads as a bridge-continuity environment where retained inland structure connects New York-facing and New Hampshire-facing Northeast continuity without expanding into freight or asset inventory treatment.

Constraint interpretation

The builder-mode layer records that for builder interpretation, Vermont should be read narrowly. The current package does not independently establish 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 Vermont topology metadata.

Evidence-layer structural exclusions

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

Trust-dimensions structural exclusions

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

Profile-layer structural exclusions

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

9. Evidence Gaps

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