Indiana

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 derived from Indiana's corridor-layer evidence, signal, and trust review.

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

2. Scope Boundary Statement

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

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

3. Evidence Summary

The evidence layer records 9 evidence subsections documenting Indiana's corridor-relevant structural anchors across inland freight, logistics hub, river transport, rail intermodal, interstate convergence, manufacturing continuity, research visibility, energy transmission, and broadband expansion.

Midwest inland freight continuity

• The evidence layer records that INDOT states Indiana is a global center of transportation and logistics and that 724 million tons of freight travel through Indiana each year, making it the fifth busiest state for commercial freight traffic.
• The evidence layer records that INDOT states that as much as one-third of the freight on Indiana's transportation network passes through the state without stopping.
• The evidence layer records that INDOT states that freight mobility in Indiana depends on integration across highways, air, rail, pipeline, and water.

Indianapolis logistics hub structure

• The evidence layer records that Indianapolis Airport Authority states IND is home to the second-largest FedEx Express operation.
• The evidence layer records that Indianapolis Airport Authority states IND is the nation's eighth-largest cargo facility.
• The evidence layer records that IEDC states Indiana offers major airports and the world's second-largest FedEx hub to provide global air reach.

Ohio River transport adjacency

• The evidence layer records that Ports of Indiana-Jeffersonville documents that it is on the Ohio/Mississippi river system, with 3,200 feet of Ohio River frontage and year-round access to America's Inland Waterways System and the Gulf of Mexico.
• The evidence layer records that Ports of Indiana-Mount Vernon documents close proximity to the confluence of the Ohio and Mississippi rivers and describes itself as a gateway for agricultural, energy, and manufacturing industries.
• The evidence layer records that Mount Vernon documents year-round access to the Inland Waterways System and the Gulf of Mexico.

Rail intermodal corridor density

• The evidence layer records that Burns Harbor documents rail connections to all Class I railroads and a 12-mile intra-port rail network.
• The evidence layer records that Jeffersonville documents on-dock rail and truck transloads, connections to CSX, Norfolk Southern, and Louisville & Indiana Railroad, and a 350-car near-dock rail yard.
• The evidence layer records that Mount Vernon documents direct interchanges to five Class I railroads and eight miles of railroad on port property.

Interstate freight convergence

• The evidence layer records that INDOT's interchange-book listing documents Indiana interstate corridors including I-65, I-69, I-70, and I-74.
• The evidence layer records that Jeffersonville documents direct access to I-64, I-65, and I-71 via I-265.
• The evidence layer records that Mount Vernon documents access to I-64 and I-69.

Manufacturing belt continuity

• The evidence layer records that IEDC states Indiana's central location provides access to the steel belt and agricultural heartland through a dense and strategically connected highway and rail network.
• The evidence layer records that Burns Harbor documents more than 30 companies at the port, including 15 steel-related companies and three steel mills.
• The evidence layer records that Jeffersonville documents 27 companies at the port, including 15 steel-related businesses, and describes a manufacturing and agricultural ecosystem with warehousing and distribution facilities.

Purdue engineering research visibility

• The evidence layer records that Purdue Engineering states few colleges can match the depth and breadth of Purdue Engineering's research capabilities and talent.

Regional energy transmission infrastructure

• The evidence layer records that OUCC states the regional transmission organization serving most Indiana electric utilities is the Midwest Independent Transmission System Operator, based in Carmel, Indiana, managing portions of 15 states and a portion of Canada.
• The evidence layer records that OUCC states Indiana-Michigan Power is served by PJM Interconnection.

Documented broadband expansion initiatives

• The evidence layer records that the Indiana Broadband Office states NTIA has approved Indiana's BEAD Final Proposal.
• The evidence layer records that the Indiana Broadband Office states the Connecting Indiana map shows broadband serviceable locations across Indiana as served, unserved, or underserved, along with other program funding visibility.
• The evidence layer records that the Indiana Connectivity Program states it aims to connect residents and businesses that lack broadband access with service providers and support the cost of extending service.

4. Signals Summary

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

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

Midwest inland freight continuity signal

The signals layer records that Indiana shows a Midwest-inland-freight-continuity signal through documented statewide freight volume, documented through-freight dependence, and documented multimodal integration across highway, air, rail, pipeline, and water.

Indianapolis logistics hub signal

The signals layer records that Indiana shows an Indianapolis-logistics-hub signal through documented FedEx scale at IND and documented national cargo-facility ranking.

Ohio River transport adjacency signal

The signals layer records that Indiana shows an Ohio-River-transport-adjacency signal through documented Jeffersonville and Mount Vernon continuity on the Ohio / Mississippi system and documented year-round inland-waterway access.

Rail intermodal corridor density signal

The signals layer records that Indiana shows a rail-intermodal-corridor-density signal through documented Class I rail access at Burns Harbor, documented on-dock and yard rail capacity at Jeffersonville, and documented multi-Class-I interchange visibility at Mount Vernon.

Interstate freight convergence signal

The signals layer records that Indiana shows an interstate-freight-convergence signal through documented visibility of I-65, I-69, I-70, and I-74 and directly documented port access to I-65 and I-69-linked freight paths.

Manufacturing belt continuity signal

The signals layer records that Indiana shows a manufacturing-belt-continuity signal through documented steel-belt and agricultural-heartland adjacency together with documented steel-heavy industrial continuity at Burns Harbor and Jeffersonville.

Purdue engineering research visibility signal

The signals layer records that Indiana shows a Purdue-engineering-research-visibility signal through directly documented research-capability visibility at Purdue Engineering.

Regional energy transmission signal

The signals layer records that Indiana shows a regional-energy-transmission signal through documented MISO visibility for most Indiana electric utilities and documented PJM visibility for Indiana-Michigan Power.

Broadband expansion initiative signal

The signals layer records that Indiana shows a broadband-expansion-initiative signal through documented BEAD approval, documented statewide served / unserved / underserved mapping activity, and documented Indiana Connectivity Program expansion activity.

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

Trust interpretation summary

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

• durable inland coordination density across freight, interstate, rail, river, and air-cargo structure
• durable infrastructure continuity through Midwest inland freight movement, Indianapolis cargo operations, Ohio River adjacency, and rail-served port assets
• visible institutional adjacency through Purdue engineering research plus state-level transmission and broadband coordination structures
• durable industrial persistence through steel-belt-linked manufacturing continuity
• partial but sufficient support-layer visibility through documented energy-transmission participation and broadband-expansion initiatives

Coordination density

Durable inland coordination density.

• Midwest inland freight continuity signal
• Indianapolis logistics hub signal
• rail intermodal corridor density signal
• interstate freight convergence signal

• the current signal layer does not provide a statewide node-ranking model
• the current package does not support corridor hierarchy or routing-authority assignment

Indiana shows corridor-relevant coordination density where freight continuity, interstates, rail-served port assets, and Indianapolis cargo structure are explicitly documented.

Infrastructure continuity

Durable inland logistics continuity.

• Midwest inland freight continuity signal
• Ohio River transport adjacency signal
• rail intermodal corridor density signal
• interstate freight convergence signal
• regional energy transmission signal
• broadband expansion initiative signal

• the current package does not establish a full statewide asset map beyond the corridor-layer anchors
• the current evidence does not support broader compute-corridor or digital-asset interpretation

Indiana shows durable continuity across inland freight, Ohio River adjacency, rail-served port infrastructure, interstate convergence, and visible utility / broadband support layers.

Institutional adjacency

Visible but narrow institutional adjacency.

• Purdue engineering research visibility signal
• regional energy transmission signal
• broadband expansion initiative signal

• the current package intentionally avoids a full university or institutional inventory
• the current trust reading does not compare institutions by rank or scale

Indiana shows corridor-relevant institutional adjacency through Purdue engineering visibility and state-level coordination structures for energy transmission and broadband expansion.

Industrial persistence

Durable manufacturing continuity.

• manufacturing belt continuity signal
• rail intermodal corridor density signal
• Ohio River transport adjacency signal

• the current package does not provide a plant-by-plant statewide industrial map

Indiana shows industrial persistence where manufacturing continuity remains directly coupled to rail, river, and freight infrastructure.

Research participation

Visible research participation.

• Purdue engineering research visibility signal

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

Indiana shows research participation sufficient for corridor interpretation through Purdue engineering visibility, without expanding into a broader statewide research-hierarchy claim.

6. Profile Summary

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

Jurisdiction summary

The profile layer records that Indiana currently reads within Atlas as a Midwest inland freight and manufacturing continuity environment organized around through-freight density, Indianapolis logistics capacity, Ohio River adjacency, rail-served corridor assets, and interstate convergence, with visible Purdue engineering research, regional transmission participation, and broadband-expansion activity.

Profile synthesis

The profile layer records that the current package shows:

• Midwest inland freight continuity anchored in INDOT freight volume and through-freight visibility
• Indianapolis logistics hub structure anchored in IND cargo and FedEx scale
• Ohio River adjacency anchored in Jeffersonville and Mount Vernon inland-waterway continuity
• rail intermodal corridor density anchored in Burns Harbor, Jeffersonville, and Mount Vernon rail access
• interstate convergence anchored in documented I-65, I-69, I-70, and I-74 visibility
• manufacturing belt continuity anchored in steel-belt adjacency and steel-heavy port environments
• Purdue engineering research visibility as the package's research anchor
• regional transmission and broadband-expansion visibility as support-layer anchors

The profile layer records that, taken together, these conditions support a structural characterization of Indiana as an inland logistics + industrial continuity corridor.

Profile synthesis statement

The profile layer records that Indiana currently reads within Atlas as an inland logistics + industrial continuity corridor linking Midwest freight continuity, Indianapolis cargo structure, Ohio River transport adjacency, rail-served manufacturing assets, and interstate convergence.

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

Builder mode role summary

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

• a Midwest inland freight-continuity environment
• an Indianapolis logistics-node environment
• an Ohio River and rail-served manufacturing continuity environment
• an interstate convergence environment around I-65, I-69, I-70, and I-74
• a Purdue-anchored research visibility environment with energy-transmission and broadband support layers

Inland freight interpretation

The builder-mode layer records that for builder interpretation, Indiana reads as a continuity environment where freight movement is structured by through-freight density, multimodal integration, interstate coverage, and Indianapolis cargo visibility.

River and rail interpretation

The builder-mode layer records that for builder interpretation, Indiana reads as an inland transfer environment where Ohio River adjacency and rail-served port infrastructure reinforce manufacturing continuity.

Manufacturing interpretation

The builder-mode layer records that for builder interpretation, Indiana reads as an industrial environment where steel-belt-linked manufacturing continuity remains coupled to freight and port assets.

Research and support-layer interpretation

The builder-mode layer records that for builder interpretation, Indiana reads as a corridor environment with visible Purdue engineering research participation and narrow but explicit support-layer continuity through regional transmission participation and broadband-expansion initiatives.

8. Structural Exclusions

The canonical package records structural exclusions across the evidence, signals, trust-dimensions, profile, and builder-mode layers. Each layer records non-assignment constraints rooted in the corridor-layer scope preserved in the current package.

Evidence-layer structural exclusions

The evidence layer records that based on the evidence collected there, this file does not support characterizing Indiana as any of the following:

• a custody-regime jurisdiction
• a DAO-wrapper jurisdiction
• a digital-asset statutory jurisdiction
• 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 deployment-tier classification

The evidence layer records that this file also does not support assigning trust posture, routing role, coordination tier, or Atlas surfaces.

Signals-layer structural exclusions

The signals layer records that based on the currently derived signals, this file does not support characterizing Indiana as any of the following: a custody-regime jurisdiction, a DAO-wrapper jurisdiction, a digital-asset statutory jurisdiction, 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 deployment-tier classification, or a surface-eligibility determination. The signals layer records that this file also does not assign routing authority, readiness tier, or Atlas surfaces.

Trust-dimensions structural exclusions

The trust-dimensions layer records that this file does not support interpreting Indiana as any of the following: a custody-regime jurisdiction, a DAO-wrapper jurisdiction, a digital-asset statutory jurisdiction, 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 deployment readiness classification, or an Atlas surface-eligibility determination. The trust-dimensions layer records that it should be read as trust interpretation of Indiana's current structural posture within the normalized Atlas package only.

Profile-layer structural exclusions

The profile layer records that Indiana's profile should not be read as: a routing-authority assignment, a deployment-tier classification, an Atlas surface-eligibility determination, a jurisdiction ranking claim, a coordination-hierarchy inference, a custody-regime jurisdiction claim, a DAO-wrapper jurisdiction claim, a digital-asset statutory jurisdiction claim, an AI compute corridor claim, a hyperscale anchor corridor claim, a federal governance corridor claim, or a primary Internet-exchange concentration claim.

Builder-mode structural exclusions

The builder-mode layer records that this file does not support interpreting Indiana as any of the following: a custody-regime jurisdiction, a DAO-wrapper jurisdiction, a digital-asset statutory jurisdiction, 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 deployment readiness classification, an Atlas surface-eligibility determination, or a coordination-hierarchy inference. The builder-mode layer records that it should be read as builder-facing interpretation of Indiana's current structural posture within the normalized Atlas package only.

9. Scope Boundaries & Canonical Narrowing

The canonical Indiana package does not record an "Evidence gaps" section in the AR/IL style. Instead, the change-log records the canonical scope-refinement decision that narrowed the package to corridor-layer anchors and explicitly removed scope categories from downstream interpretation.

Scope retained (corridor-relevant)

Scope removed from downstream interpretation

The change-log records the current status: evidence layer narrowed to corridor sufficiency, downstream layers re-derived from the narrowed evidence set, 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, and Topology Completion Layer. The change-log records that this sync is structural only and does not alter evidence, signals, trust interpretation, profile, builder-mode, or surface neutrality.

2026-04-15 evidence-first package population

The change-log records that the Indiana state package was populated in topology-normalized order: evidence.md, signals.md, trust-dimensions.md, metadata.md, profile.md, builder-mode.md.

2026-04-15 corridor-scope refinement

The change-log records that the Indiana package was refined to corridor-layer anchors only. The change-log records that the evidence layer was narrowed to corridor sufficiency, downstream layers were re-derived from the narrowed evidence set, and surface assignment remains none. The scope-retained and scope-removed lists are rendered in Section 9 (Scope Boundaries & Canonical Narrowing) above.