North Carolina

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 research-corridor foundation topology. The canonical atlas.md places North Carolina in the Southeast Research & Defense Corridor, with a Southeast Research Corridor Layer foundation and a Southeast Interior Completion Layer completion. North Carolina's canonical Foundation Layer and Completion Layer are distinct — the Foundation Layer is the Southeast Research Corridor Layer, a canonical layer whose only member is North Carolina and whose name carries "Corridor Layer" rather than "Completion Layer", while the Completion Layer is the Southeast Interior Completion Layer shared with other Southeast Interior Completion Layer cluster members. The canonical Jurisdiction Lens uses "within" to reflect that North Carolina's research-themed Foundation resolves into the broader Southeast Interior Completion Layer.

2. Scope Boundary Statement

The evidence layer records that this file records only corridor-relevant structural anchors retained for North Carolina from adjacent-state continuity already visible inside Atlas. The evidence layer records that it does not perform an open-ended statewide infrastructure survey and does not assign trust posture, routing role, coordination tier, readiness, or Atlas surfaces.

This rendering mirrors the canonical package. The canonical North Carolina package is an adjacency-bounded corridor-layer sufficient package: its evidence is retained from corridor continuity between adjacent Atlas states (Virginia, Tennessee, South Carolina, Georgia) 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 5 evidence subsections documenting North Carolina'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.

Southeast interior continuity

• The evidence layer records that atlas-export/docs/atlas.md places North Carolina in the Southeast Research & Defense Corridor, with a Southeast Research Corridor Layer foundation and a Southeast Interior Completion Layer completion.
• The evidence layer records that Tennessee is retained in Atlas in the Southeast Interior Structural Corridor, with a Southeast Interior Completion Layer foundation and a Central Interior Completion Layer completion.
• The evidence layer records that Georgia is retained in Atlas in the Atlantic Industrial Growth Corridor, with a Southeast Interior Completion Layer foundation and completion placement.
• The evidence layer records that South Carolina is retained in Atlas in the Atlantic Industrial & Port Support Corridor, with a Southeast Interior Completion Layer foundation and a Southeast Coastal Completion Layer completion.
• The evidence layer records that the retained Atlas topology therefore supports reading North Carolina as part of a broader Southeast interior continuity frame through its Southeast Interior Completion Layer placement and its adjacency to Tennessee, Georgia, and South Carolina.

Atlantic-facing support continuity

• The evidence layer records that Georgia's retained Atlas placement preserves an Atlantic Industrial Growth Corridor environment on North Carolina's south-facing side.
• The evidence layer records that South Carolina's retained Atlas placement preserves an Atlantic Industrial & Port Support Corridor environment and resolves into the Southeast Coastal Completion Layer.
• The evidence layer records that Virginia's retained Atlas placement preserves a north-facing Mid-Atlantic Completion Layer frame above North Carolina.
• The evidence layer records that North Carolina's retained position between these adjacent Atlantic-facing and Mid-Atlantic frames supports an Atlantic-facing support continuity reading at the corridor layer.
• The evidence layer records that under the current corridor-scope restriction, this anchor is retained only as structural Atlantic-facing support continuity and is not expanded into port, terminal, tonnage, or coastal inventory treatment.

Institutional adjacency continuity across the Virginia–Tennessee–South Carolina–Georgia frame

• The evidence layer records that Virginia's retained Atlas placement preserves a north-facing federal-interface and Mid-Atlantic frame adjacent to North Carolina.
• The evidence layer records that Tennessee's retained Atlas placement preserves a west-facing Southeast interior structural frame adjacent to North Carolina.
• The evidence layer records that South Carolina's retained Atlas placement preserves a south-facing Atlantic support frame adjacent to North Carolina.
• The evidence layer records that Georgia's retained Atlas placement preserves a south-facing Southeast interior growth frame adjacent to North Carolina.
• The evidence layer records that North Carolina's retained position inside this adjacent-state frame supports an institutional adjacency continuity reading at the corridor layer.
• The evidence layer records that under the current corridor-scope restriction, this anchor is retained only as structural adjacency continuity and is not expanded into university-system mapping, research-network inventory treatment, or statewide institutional survey treatment.

Inland continuity between Tennessee-facing and South Carolina-facing structure

• The evidence layer records that Tennessee's retained Atlas placement preserves a Southeast Interior Structural Corridor environment west of North Carolina.
• The evidence layer records that South Carolina's retained Atlas placement preserves an Atlantic Industrial & Port Support Corridor environment south of North Carolina, with a Southeast Coastal Completion Layer completion.
• The evidence layer records that North Carolina's retained Atlas placement sits between those adjacent structures as a Southeast Research & Defense Corridor environment with Southeast Research Corridor Layer foundation and Southeast Interior Completion Layer completion.
• The evidence layer records that the retained topology therefore supports an inland continuity reading across North Carolina between Tennessee-facing interior structure and South Carolina-facing Atlantic support structure.

North-south transition continuity between Virginia-facing and Georgia-facing structure

• The evidence layer records that Virginia's retained Atlas placement resolves from the Federal Interface Governance Layer into the Mid-Atlantic Completion Layer.
• The evidence layer records that North Carolina's retained Atlas placement resolves from the Southeast Research Corridor Layer into the Southeast Interior Completion Layer.
• The evidence layer records that Georgia's retained Atlas placement remains on the Southeast Interior Completion Layer for both foundation and completion.
• The evidence layer records that North Carolina's retained corridor position therefore supports a north-south transition reading between the Virginia-facing federal and Mid-Atlantic frame and the Georgia-facing Southeast interior growth frame.
• The evidence layer records that under the current corridor-scope restriction, this anchor is retained only as structural transition continuity and is not expanded into freight/logistics, routing, readiness, or surface-assignment inference.

4. Signals Summary

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

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

Southeast interior continuity signal

The signals layer records that North Carolina shows a Southeast-interior-continuity signal through retained placement on the Southeast Interior Completion Layer and its visible adjacency to Tennessee, Georgia, and South Carolina.

Atlantic-facing support signal

The signals layer records that North Carolina shows an Atlantic-facing-support signal through retained placement between Georgia and South Carolina's Atlantic-facing corridor structure and Virginia's north-facing Mid-Atlantic frame.

Institutional adjacency signal

The signals layer records that North Carolina shows an institutional-adjacency signal through retained placement inside the Virginia, Tennessee, South Carolina, and Georgia-facing corridor frame.

Inland Tennessee-to-South Carolina continuity signal

The signals layer records that North Carolina shows an inland-Tennessee-to-South-Carolina-continuity signal through retained placement between Tennessee-facing interior structure and South Carolina-facing Atlantic support structure.

North-south transition signal

The signals layer records that North Carolina shows a north-south-transition signal through retained placement between the Virginia-facing federal and Mid-Atlantic frame and the Georgia-facing Southeast interior growth 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 trust evaluates what kinds of stability conditions North Carolina can sustain given the signal layer and the visible corridor-continuity environment.

Trust interpretation summary

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

• narrow but durable corridor coordination density across Southeast interior continuity, Atlantic-facing support continuity, institutional adjacency continuity, inland Tennessee-to-South Carolina continuity, and north-south transition continuity
• durable interior continuity with visible Atlantic-facing and Mid-Atlantic transition structure at the corridor layer
• visible multi-adjacent institutional adjacency across the Virginia, Tennessee, South Carolina, and Georgia-facing frame
• industrial persistence not independently established beyond corridor continuity and adjacency
• research participation not independently established beyond institutional adjacency

Coordination density

Narrow but durable corridor coordination density.

• Southeast interior continuity signal
• Atlantic-facing support signal
• institutional adjacency signal
• inland Tennessee-to-South Carolina continuity signal
• north-south transition 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, rail visibility, energy-grid participation visibility, or BEAD coordination visibility

North Carolina shows corridor-relevant coordination density as a Southeast research-aligned interior environment linking Virginia-facing federal and Mid-Atlantic structure, Tennessee-facing interior structure, South Carolina-facing Atlantic support structure, and Georgia-facing Southeast interior growth structure.

Infrastructure continuity

Durable interior continuity with visible Atlantic-facing and Mid-Atlantic transition structure.

• Southeast interior continuity signal
• Atlantic-facing support signal
• inland Tennessee-to-South Carolina continuity signal
• north-south transition signal

• the current package does not independently establish freight or logistics continuity
• the current package does not independently establish rail visibility
• the current package does not independently establish energy-grid participation visibility or BEAD coordination visibility
• the current package does not independently establish inland-waterway continuity
• the current package does not expand into statewide infrastructure surveys, port inventories, terminal inventories, or tonnage datasets

North Carolina shows durable corridor continuity where a Southeast interior completion frame carries between inland and Atlantic-facing adjacent structures, but the package retains that continuity only at the corridor layer.

Institutional adjacency

Visible multi-adjacent institutional adjacency.

• institutional adjacency signal
• Southeast interior continuity signal
• Atlantic-facing support signal
• north-south transition signal

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

North Carolina shows institutional adjacency through its retained corridor position between Virginia-facing federal and Mid-Atlantic structure, Tennessee-facing interior structure, South Carolina-facing Atlantic support structure, and Georgia-facing Southeast interior growth structure.

Industrial persistence

Not independently established beyond corridor continuity and adjacency.

• Southeast interior continuity signal
• Atlantic-facing support signal
• inland Tennessee-to-South Carolina continuity signal

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

North Carolina sits inside a corridor whose retained topology preserves interior and Atlantic-facing continuity, but this package does not independently establish North Carolina industrial persistence beyond that adjacency-bounded corridor structure.

Research participation

Not independently established beyond institutional adjacency.

• institutional adjacency signal
• Southeast interior continuity signal

• the current package does not retain a corridor-visible research anchor for North Carolina beyond its adjacency-bounded corridor placement
• the current package intentionally avoids university-system mapping and research-network inventory treatment
• the current trust reading does not support a research-hierarchy claim for North Carolina from the retained corridor evidence alone

North Carolina sits inside a visible Southeast institutional frame, but the current retained evidence does not independently establish research participation beyond that adjacency position.

6. Profile Summary

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

Jurisdiction summary

The profile layer records that North Carolina currently reads within Atlas as a Southeast interior and Atlantic-facing support environment organized around Southeast interior continuity, Atlantic-facing support continuity, institutional adjacency continuity, inland Tennessee-to-South Carolina continuity, and north-south transition continuity.

Profile synthesis

The profile layer records that the current package shows:

• Southeast interior continuity anchored in retained placement on the Southeast Interior Completion Layer and visible adjacency to Tennessee, Georgia, and South Carolina
• Atlantic-facing support continuity anchored in retained placement between Georgia and South Carolina's Atlantic-facing corridor structure and Virginia's north-facing Mid-Atlantic frame
• institutional adjacency continuity anchored in retained placement inside the Virginia, Tennessee, South Carolina, and Georgia-facing corridor frame
• inland Tennessee-to-South Carolina continuity anchored in retained placement between Tennessee-facing interior structure and South Carolina-facing Atlantic support structure
• north-south transition continuity anchored in retained placement between the Virginia-facing federal and Mid-Atlantic frame and the Georgia-facing Southeast interior growth frame
• no independent retained basis for freight or logistics continuity, rail visibility, energy-grid participation visibility, BEAD coordination visibility, inland-waterway continuity, digital-asset statutory posture, or research participation beyond institutional adjacency under the current corridor-bounded scope

The profile layer records that, taken together, these conditions support a structural characterization of North Carolina as a Southeast interior and Atlantic-facing support continuity corridor within the broader southeastern frame.

Profile synthesis statement

The profile layer records that North Carolina currently reads within Atlas as a Southeast interior support continuity corridor linking a Virginia-facing transition frame to Georgia and South Carolina-facing southeastern continuity.

7. Builder Mode Summary

Derivation constraint. The builder-mode layer records that builder-mode content derives strictly from normalized jurisdiction layers. The builder-mode layer records that this file provides structural interpretation only, and does not rank North Carolina, compare North Carolina to other jurisdictions, or prescribe deployment eligibility.

Builder mode role summary

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

• a Southeast interior continuity environment
• an Atlantic-facing support continuity environment
• an institutional adjacency environment across the Virginia, Tennessee, South Carolina, and Georgia-facing frame
• an inland continuity environment between Tennessee-facing interior structure and South Carolina-facing Atlantic support structure
• a north-south transition environment between Virginia-facing and Georgia-facing structure
• a narrow corridor environment rather than a standalone topology override or readiness case

Southeast interior interpretation

The builder-mode layer records that for builder interpretation, North Carolina reads as a Southeast interior continuity environment where retained placement carries into the Southeast Interior Completion Layer and remains connected to adjacent southeastern structure without overriding atlas-controlled topology.

Atlantic-facing interpretation

The builder-mode layer records that for builder interpretation, North Carolina reads as an Atlantic-facing support continuity environment where retained structure preserves adjacency between Georgia and South Carolina's Atlantic-facing corridor positions and the Virginia-facing northern frame without expanding into port, terminal, or tonnage inventory treatment.

Institutional adjacency interpretation

The builder-mode layer records that for builder interpretation, North Carolina reads as an institutional adjacency environment where retained structure preserves corridor continuity across Virginia, Tennessee, South Carolina, and Georgia-facing placements without expanding into university-system mapping or research-network inventory treatment.

Inland continuity interpretation

The builder-mode layer records that for builder interpretation, North Carolina reads as an inland continuity environment where retained structure preserves corridor continuity between Tennessee-facing interior structure and South Carolina-facing Atlantic support structure.

Transition interpretation

The builder-mode layer records that for builder interpretation, North Carolina reads as a north-south transition environment where retained structure carries between the Virginia-facing federal and Mid-Atlantic frame and the Georgia-facing Southeast interior growth frame without expanding into freight/logistics, routing, or readiness treatment.

Constraint interpretation

The builder-mode layer records that for builder interpretation, North Carolina should be read narrowly. The current package does not independently establish freight or logistics continuity, rail visibility, energy-grid participation visibility, BEAD coordination visibility, inland-waterway continuity, digital-asset statutory posture, or any deployment or routing posture.

8. Structural Exclusions

The canonical package records structural exclusions across the evidence, signals, trust-dimensions, profile, builder-mode, and change-log layers. The canonical North Carolina structural exclusions set uses the shortened canonical formulation — focused on survey/inventory/mapping-type exclusions — and is preserved verbatim from each canonical layer.

Evidence-layer structural exclusions

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

• a routing-authority jurisdiction
• a coordination-tier jurisdiction
• a deployment-readiness jurisdiction
• a surface-assigned jurisdiction
• a statewide infrastructure-survey case
• a statewide freight-survey case
• a port-inventory or terminal-inventory case
• a municipal-inventory case
• a university-system mapping case
• a research-network inventory case
• an engineering-sector survey case
• an AI compute corridor
• a hyperscale designation
• a jurisdiction-ranking case
• a digital-asset statutory jurisdiction

Signals-layer structural exclusions

The signals layer records that based on the currently derived signals, this file does not support characterizing North Carolina as any of the following: a routing-authority jurisdiction, a coordination-tier jurisdiction, a deployment-readiness jurisdiction, a surface-eligibility determination, a jurisdiction-ranking claim, an AI compute corridor, a hyperscale designation, a statewide infrastructure-survey case, a statewide freight-survey case, a port-inventory or terminal-inventory case, or a digital-asset statutory jurisdiction. The signals layer records that the current signal set also does not independently establish freight or logistics continuity, rail visibility, energy-grid participation visibility, BEAD coordination visibility, inland-waterway continuity, or research participation beyond institutional adjacency.

Trust-dimensions structural exclusions

The trust-dimensions layer records that this file does not support interpreting North Carolina as any of the following: a routing-authority jurisdiction, a coordination-tier jurisdiction, a deployment-readiness jurisdiction, an Atlas surface-eligibility determination, a jurisdiction-ranking case, an AI compute corridor, a hyperscale designation, or a digital-asset statutory jurisdiction. The trust-dimensions layer records that it should be read as trust interpretation of North Carolina's current structural posture within the normalized Atlas package only.

Profile-layer structural exclusions

The profile layer records that North Carolina's profile should not be read as: a routing-authority assignment, a coordination-tier assignment, a deployment-readiness classification, an Atlas surface-eligibility determination, a jurisdiction ranking claim, an AI compute corridor claim, a hyperscale designation, a digital-asset statutory jurisdiction claim, or a topology reassignment of atlas-controlled metadata.

Builder-mode structural exclusions

The builder-mode layer records that this file does not support interpreting North Carolina as any of the following: a routing-authority jurisdiction, a coordination-tier jurisdiction, a deployment-readiness jurisdiction, an Atlas surface-eligibility determination, a jurisdiction-ranking case, an AI compute corridor, a hyperscale designation, or a digital-asset statutory jurisdiction. The builder-mode layer records that it should be read as builder-facing interpretation of North Carolina's current structural posture within the normalized Atlas package only.

Change-log structural exclusions

The change-log records explicit structural exclusions: this package population does not authorize Atlas surface assignment, routing-role assignment, coordination-tier assignment, deployment-readiness assignment, jurisdiction ranking, AI compute-corridor designation, hyperscale designation, digital-asset statutory designation, or local reassignment of atlas-controlled North Carolina topology metadata.

9. Evidence Gaps

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

Evidence gaps from the evidence layer

Scope constraints applied during population

The change-log records the current status: topology metadata synced to atlas-export/docs/atlas.md, evidence layer populated to corridor sufficiency, corridor-scope constraints applied throughout package construction, downstream layers derived strictly from corridor-limited evidence, surface assignment remains none.

10. Change-Log Notes & Normalization Notes

Topology metadata sync

The change-log records that metadata.md was reviewed against atlas-export/docs/atlas.md, with updated fields for Corridor Group, Foundation Layer, Topology Completion Layer, and Jurisdiction lens. The change-log records that this sync is structural only and does not alter evidence, signals, trust interpretation, profile, builder-mode, or surface neutrality.

2026-04-18 evidence-first package population

The change-log records that the North Carolina state package was populated in topology-normalized order as a numbered canonical sequence: evidence.md, signals.md, trust-dimensions.md, metadata.md, profile.md, builder-mode.md, change-log.md. The change-log records that scope constraints were applied during population (rendered in Section 9 above). The change-log records the current status: topology metadata synced to atlas-export/docs/atlas.md, evidence layer populated to corridor sufficiency, corridor-scope constraints applied throughout package construction, downstream layers derived strictly from corridor-limited evidence, and surface assignment remains none.

Structural exclusions

The change-log records explicit structural exclusions: this package population does not authorize Atlas surface assignment, routing-role assignment, coordination-tier assignment, deployment-readiness assignment, jurisdiction ranking, AI compute-corridor designation, hyperscale designation, digital-asset statutory designation, or local reassignment of atlas-controlled North Carolina topology metadata.