Alabama

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 Alabama in the Southeast Interior Support Corridor, the Southeast Interior Completion Layer, and the Southeast Interior 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 canonical topology-collapse pattern reflects the canonical meaning of the Southeast Interior Support Corridor as a support-position continuity environment that exists at the Southeast Interior Completion Layer without independent Foundation-Layer scaffolding. The canonical Jurisdiction Lens uses "within" (not "transition into") to reflect the topology-collapse pattern.

2. Scope Boundary Statement

The evidence layer records that this file records only corridor-relevant structural anchors retained for Alabama 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 Alabama package is an adjacency-bounded corridor-layer sufficient package: its evidence is retained from corridor continuity between adjacent Atlas states (Tennessee, Georgia, Mississippi, Florida) 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 3 evidence subsections documenting Alabama'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.

Inland Southeast continuity

• The evidence layer records that atlas-export/docs/atlas.md places Alabama in the Southeast Interior Support Corridor, the Southeast Interior Completion Layer, and the Southeast Interior Completion Layer.
• The evidence layer records that Georgia is retained in Atlas in the Atlantic Industrial Growth Corridor with the same Southeast Interior Completion Layer foundation and completion placement.
• The evidence layer records that Tennessee is retained in Atlas in the Southeast Interior Structural Corridor with the same Southeast Interior Completion Layer foundation.
• The evidence layer records that Mississippi is retained in Atlas in the Lower Mississippi River Corridor with the same Southeast Interior Completion Layer foundation.
• The evidence layer records that the retained Atlas topology therefore supports reading Alabama as an inland Southeast continuity jurisdiction inside the Tennessee, Georgia, and Mississippi-facing interior frame, without overriding atlas-controlled topology.

Gulf-facing continuity

• The evidence layer records that Mississippi's retained Atlas placement resolves from the shared Southeast Interior Completion Layer foundation into the Gulf Interior Completion Layer.
• The evidence layer records that Florida's retained Atlas placement resolves into the Southeast Coastal Completion Layer as the adjacent Gulf-facing coastal environment.
• The evidence layer records that Alabama's retained support placement between the interior Southeast frame and adjacent Gulf-facing completion environments supports a Gulf-facing continuity reading at the corridor layer.
• The evidence layer records that under the current corridor-scope restriction, this anchor is retained only as structural Gulf-facing continuity and is not expanded into port, terminal, or tonnage inventory treatment.

Southeast support-position adjacency continuity

• The evidence layer records that Alabama's retained Atlas position sits between Tennessee's interior structural continuity, Georgia's interior growth continuity, Mississippi's river-linked interior continuity, and Florida's coastal completion environment.
• The evidence layer records that the retained topology therefore supports reading Alabama as a Southeast support-position adjacency jurisdiction within the broader southeastern corridor frame.
• 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.

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

Inland Southeast continuity signal

The signals layer records that Alabama shows an inland-Southeast-continuity signal through atlas-retained placement inside the Tennessee, Georgia, and Mississippi-facing interior frame.

Gulf-facing continuity signal

The signals layer records that Alabama shows a Gulf-facing-continuity signal through retained support-position continuity between the interior Southeast frame and adjacent Gulf-facing completion environments.

Southeast support-position adjacency signal

The signals layer records that Alabama shows a Southeast-support-position-adjacency signal through retained adjacency across Tennessee's interior structural continuity, Georgia's interior growth continuity, Mississippi's river-linked continuity, and Florida's coastal completion environment.

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

Trust interpretation summary

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

• narrow but durable corridor coordination density across inland Southeast continuity, Gulf-facing continuity, and Southeast support-position adjacency
• durable but narrow infrastructure continuity through inland Southeast continuity and Gulf-facing continuity
• visible institutional adjacency across the Tennessee, Georgia, Mississippi, and Florida-facing southeastern corridor frame
• industrial persistence not independently established beyond interior and Gulf-facing continuity
• research participation not independently established beyond corridor adjacency inside the Southeast interior frame

Coordination density

Narrow but durable corridor coordination density.

• inland Southeast continuity signal
• Gulf-facing continuity signal
• Southeast support-position 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 freight or logistics continuity beyond the retained interior support reading, rail visibility, energy-grid participation, BEAD coordination, or inland-waterway continuity beyond the retained corridor anchors

Alabama shows corridor-relevant coordination density as a Southeast interior support environment linking inland continuity to adjacent Gulf-facing completion environments.

Infrastructure continuity

Durable but narrow interior-and-Gulf-facing continuity.

• inland Southeast continuity signal
• Gulf-facing continuity signal

• the current package does not independently establish freight or logistics continuity beyond the retained interior support reading
• the current package does not independently establish rail visibility
• the current package does not independently establish energy-grid participation or BEAD coordination
• the current package does not independently establish inland-waterway continuity
• the current package does not expand into statewide freight or asset inventory treatment

Alabama shows durable corridor continuity where retained inland Southeast structure carries toward adjacent Gulf-facing completion environments.

Institutional adjacency

Visible Southeast support-position institutional adjacency.

• inland Southeast continuity signal
• Southeast support-position adjacency signal
• Gulf-facing continuity signal

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

Alabama shows institutional adjacency through its retained support position between Tennessee's interior structural continuity, Georgia's interior growth continuity, Mississippi's river-linked continuity, and Florida's coastal completion environment.

Industrial persistence

Not independently established beyond interior and Gulf-facing continuity.

• inland Southeast continuity signal
• Gulf-facing 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 Alabama from the retained corridor evidence alone

Alabama may sit inside a corridor with visible inland and Gulf-facing continuity, but this package does not independently establish Alabama industrial persistence beyond the retained corridor anchors.

Research participation

Not independently established beyond corridor adjacency.

• Southeast support-position adjacency signal
• inland Southeast 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 Alabama from the retained corridor evidence alone

Alabama sits within a visible Southeast corridor frame, but the current retained evidence does not independently establish Alabama 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 Alabama currently reads within Atlas as a Southeast interior support jurisdiction organized around inland Southeast continuity, Gulf-facing continuity, and Southeast support-position adjacency inside the broader southeastern corridor frame.

Profile synthesis

The profile layer records that the current package shows:

• inland Southeast continuity anchored in atlas-retained placement inside the Tennessee, Georgia, and Mississippi-facing interior frame
• Gulf-facing continuity anchored in retained support-position continuity between the interior Southeast frame and adjacent Gulf-facing completion environments
• Southeast support-position adjacency anchored in retained adjacency across Tennessee's interior structural continuity, Georgia's interior growth continuity, Mississippi's river-linked continuity, and Florida's coastal completion environment
• no independent retained basis for freight or logistics continuity beyond the retained interior support reading, rail visibility, energy-grid participation, BEAD coordination, inland-waterway continuity, 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 Alabama as a Southeast interior support continuity corridor.

Profile synthesis statement

The profile layer records that Alabama currently reads within Atlas as a Southeast interior support continuity corridor linking retained inland Southeast structure to adjacent Gulf-facing completion environments inside the broader southeastern 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 Alabama, compare Alabama to other jurisdictions, or prescribe deployment eligibility.

Builder mode role summary

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

• a Southeast interior support continuity environment
• an inland Southeast continuity environment
• a Gulf-facing continuity environment at the edge of adjacent completion structures
• a Southeast support-position adjacency environment inside the broader southeastern corridor frame
• a narrow support environment rather than a standalone topology override or readiness case

Interior support interpretation

The builder-mode layer records that for builder interpretation, Alabama reads as a Southeast interior support environment where retained corridor placement links Tennessee's interior structural continuity, Georgia's interior growth continuity, and Mississippi's river-linked continuity without overriding atlas-controlled topology.

Gulf-facing interpretation

The builder-mode layer records that for builder interpretation, Alabama reads as a Gulf-facing continuity environment where retained support placement carries the interior Southeast frame toward adjacent Gulf-facing completion structures without expanding into port, terminal, or tonnage inventory treatment.

Adjacency interpretation

The builder-mode layer records that for builder interpretation, Alabama reads as a support-position adjacency environment where retained structure preserves corridor continuity across Tennessee, Georgia, Mississippi, and Florida-facing placements without expanding into university-system mapping or research-network inventory treatment.

Constraint interpretation

The builder-mode layer records that for builder interpretation, Alabama should be read narrowly. The current package does not independently establish freight or logistics continuity beyond the retained interior support reading, rail visibility, energy-grid participation, BEAD coordination, 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. Multiple layers record a distinct canonical exclusion: local reassignment of atlas-controlled Alabama topology metadata.

Evidence-layer structural exclusions

The evidence layer records that based on the evidence collected there, this file does not support characterizing Alabama 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 Alabama 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 freight or logistics continuity beyond the retained interior support reading, rail visibility, energy-grid participation, BEAD coordination, or inland-waterway continuity for Alabama.

Trust-dimensions structural exclusions

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

Profile-layer structural exclusions

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

9. Evidence Gaps

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