Mapping the Convergence
AustinIO Architecture
The companion page to Austin as the Model 5IR City articulates what Austin is. This page articulates how AustinIO covers it, and why the site is organized the way it is.
AustinIO is the geographically-converged nexus of three other SiliconPlans Network properties: ElectronsX (electrification supply chains), SemiconductorX (semiconductor supply chains), and DatacentersX (datacenter supply chains). Where those properties cover supply chains by category at national and global scale, AustinIO covers the same supply chains through a geographic lens — what physically converges in Texas, what concentrations form, and why.
The Four-Question Core
Every entity covered on AustinIO is rendered through four core questions. These questions hold across page types, entity types, and navigation paths. They are the consistent analytical frame.
| Question | What it surfaces |
|---|---|
| What is it? | Identity and category — the entity's role in the AI-Industrial-defense complex |
| Who owns or operates it? | Operator, anchor relationships, captive arrangements, vertical integration patterns |
| Where is it made? | Geographic location at city, county, corridor, and metroplex resolution |
| How is it made? | Process, technology, supply chain, supplier ring, equipment, materials |
The four questions are not asked in isolation. A spotlight page on Samsung Taylor answers all four in coordinated fashion: what (the largest semiconductor capital commitment in Texas history), who (Samsung Foundry, with Tesla as captive-equivalent customer), where (Taylor, Texas, in the U.S. Highway 79 industrial corridor in Williamson County in the Austin-San Antonio metroplex), how (the EUV-equipped 2nm GAA process supplied through a Williamson County-concentrated co-located supplier ring including Linde Taylor, Valex Round Rock, and Tekscend Round Rock, plus the broader Big-5 WFE network).
What Makes AustinIO's Coverage Distinctive
AustinIO covers two kinds of entities — standard and geographic — that together form a denser knowledge graph than either alone produces.
Most supply-chain coverage focuses on standard entities: products, suppliers, OEMs, facilities, processes, and technologies. These entities flow through the four-question core and appear across the SiliconPlans Network. AustinIO covers them too, with the same analytical depth.
What AustinIO adds is explicit, first-class coverage of geographic entities: cities, counties, industrial clusters, named corridors, and metroplexes. Each geographic entity has its own attributes, its own relationships to standard entities, and its own page or section. A city page lists what facilities sit in it. A corridor page lists what cities and anchors compose it, and what cluster-level patterns the corridor exhibits. A county page connects to its industrial clusters, its supplier rings, and its workforce substrate.
The result is a knowledge graph in which standard and geographic entities cross-link densely. A user looking at the Linde Taylor on-site air separation unit and electrolyzer plant can follow the city link to Taylor, the county link to Williamson County, the corridor link to U.S. Highway 79, the anchor link to Samsung Taylor, and the operator link to Linde plc — each path surfacing a different facet of the same supply-chain phenomenon. The geographic axis is what gives AustinIO editorial real estate that single-axis supply-chain coverage cannot occupy.
The Four Architectural Layers
AustinIO's coverage is organized as four nested layers. Pages in the site are entry points into the architecture from different starting positions. Every page links upward to the layers that contain it and downward to the layers it contains.
| Layer | What it contains | Resolution |
|---|---|---|
| Geography | Texas Triangle outermost frame; Austin-San Antonio metroplex inside it; named corridors inside the metroplex; counties inside corridors; cities inside counties | Region down to city block |
| Anchors | Strategically distinctive facilities and programs sited at specific points within the geography layer; Tier 1 spotlight entries plus Tier 2 directory entries | Single facility or campus |
| Supply Chains | Supplier-facility networks orbiting each anchor — Tier 1A production inputs, Tier 1B co-located infrastructure, Tier 2 construction and equipment | Per-supplier facility, with operator and geographic attributes |
| Standard Entities | Products, processes, technologies, and OEMs that flow through the supply chains and end at anchors for production or deployment | Detail-tier component, technology, or process |
The layers are nested. A standard entity (a sintered NdFeB magnet, for example) flows through a supply chain (MP Materials Fort Worth Magnet Plant produces it; Tesla Giga TX consumes it), terminates at an anchor (Tesla's vehicle assembly line), and is sited within a geography (Tarrant County to Travis County along the Texas Triangle's north-south spine). Reading the entity through the layers surfaces the convergence pattern that the entity participates in.
The Five Page Types
AustinIO renders the four-layer architecture through five distinct page types. Each page type serves a different reader entry point and answers the four-question core at a different resolution.
| Page Type | What it covers | When to read it |
|---|---|---|
| Nexus pages | Thematic-geographic lenses on the convergence — Giga Austin, UT Austin, Austin Startups, Austin CapEx, Texas Triangle, Texas Energy | Reader wants to understand a thematic concentration (for example, what coordinates around Tesla's Austin operations, or what the strategic capital flows look like across the cluster) |
| Spotlight pages | Tier 1 anchor facilities and programs — Samsung Taylor, Tesla Megapack Brookshire, Meta Temple, Lockheed Fort Worth, Permian Basin, and others | Reader wants deep treatment of a single strategically distinctive anchor, including what makes it first or largest in its category and why it matters in the convergence |
| Anchor supplier-network pages | Spotlight pages augmented with dataset-backed supplier-facility tables for the anchors with the deepest supplier-network distinctiveness | Reader wants the anchor's strategic position plus the supply chain that surrounds it, with operator, geographic, and tier attributes for each supplier facility |
| Corridor pages | Named regional corridors — U.S. Highway 79, Georgetown-Hutto-Taylor datacenter cluster, Austin-Waco I-35/I-14 defense-industrial spine, U.S. 183 space corridor, Austin-Taylor manufacturing axis | Reader wants to understand a regional cluster phenomenon — what cities compose it, what anchors sit in it, what category specialization it exhibits, and how it connects to adjacent corridors |
| Directory pages | Comprehensive catalogs of companies and facilities by category — semiconductor B2B, aerospace and defense, HQ companies, and others | Reader wants to see the full set of companies operating in a category in the Austin metro, regardless of anchor relationship or strategic distinctiveness |
Each page type cross-links to the others. A nexus page lists the spotlight entries that compose its lens. A spotlight page links upward to its corridor and downward to its supplier dataset where one exists. A corridor page lists its constituent cities, anchors, and connecting supplier facilities. A directory page links each entry to its anchor or supplier role where applicable.
How the Cross-Linking Works
The architecture's value compounds at the cross-links. Reading a single page is informative; following the links across the four layers is what surfaces the convergence patterns.
The connection types AustinIO surfaces explicitly:
Anchor to suppliers and back. Every Tier 1 anchor with a supplier-network page links to its supplier-facility dataset. Every supplier facility row links back to the anchor it serves. Suppliers that serve multiple anchors (Linde, Air Liquide, Schneider Electric, Hitachi Energy, ASML, NVIDIA) appear with different facility identifiers under each anchor, surfacing the multi-anchor relationship structure when the dataset is queried by operator.
Anchor to geography and back. Every spotlight page identifies the city, county, corridor, and metroplex its anchor sits in. Every geographic page lists the anchors it contains. The mutual links surface the geographic concentration patterns — Williamson County contains a dense supplier ring across multiple anchor relationships; the Austin-Waco I-35/I-14 corridor contains Fort Cavazos plus Bastrop SpaceX plus McGregor SpaceX plus Cedar Park Firefly across a single 130-mile spine.
Anchor to anchor. Cross-anchor relationships are surfaced explicitly. Samsung Taylor as Tesla's captive-equivalent foundry. Tesla Megapack as on-site behind-the-meter storage at Starbase. Tesla Robstown lithium feeding Tesla Giga TX cell production. Apple Austin's silicon design relationship to TSMC and the broader on-device AI ecosystem. These cross-anchor links are the convergence thesis made visible at the page level.
Anchor to thematic nexus. Each anchor sits in one or more thematic-geographic lenses. Tesla Giga TX in the Giga Austin Nexus. Apple Austin in the Austin Startup Nexus and the broader on-device AI silicon design hub coverage. TIE NGMM in the UT Austin Nexus. Samsung Taylor in the Austin CapEx Nexus alongside the federal CHIPS allocation that anchored its commitment.
Geography to geography. Cities sit in counties; counties in corridors; corridors in the metroplex; the metroplex in the Texas Triangle. The nesting surfaces the multi-scale geography that the convergence operates at.
Across SiliconPlans properties. AustinIO's coverage of any entity that also appears on EX, SX, or DX includes cross-property links to the broader supply-chain treatment on the network's other properties. The cross-property marker (↗) signals when a link leads outside AustinIO to the broader category coverage. AustinIO covers the geographic concentration of the convergence; EX, SX, and DX cover the supply chains that converge in it.
How to Navigate AustinIO
The right entry point depends on what the reader is looking for. Four common navigation paths through the architecture:
| If you are looking for... | Start here | Then follow links to... |
|---|---|---|
| Strategic understanding of the cluster as a whole | Austin as the Model 5IR City — the thesis page | Six pillar nexus pages, then anchor spotlights within each |
| A specific anchor facility | Spotlights Hub — the curated Tier 1 index | The anchor's supplier dataset (where one exists), its corridor context, and adjacent anchor relationships |
| A regional cluster or geographic pattern | The relevant corridor or county page | Anchors within the corridor; supplier facilities concentrated in the corridor; adjacent corridors with overlapping coverage |
| A specific supplier, OEM, or company | The directory pages for the relevant category, or a search by company name | The anchors the company serves; the geographic locations where its facilities sit; the cross-property coverage on EX, SX, or DX |
Every navigation path eventually surfaces the convergence thesis from a different angle. A reader entering through the corridor pages sees the geographic concentration first, then the anchors, then the supplier rings. A reader entering through the spotlight pages sees the strategic distinctiveness first, then the supplier networks, then the corridor context. A reader entering through the nexus pages sees the thematic concentration first, then the constituent anchors, then the supply chains. The architecture lets each reader build the convergence picture from whichever entry point matches their starting question.
What the Architecture is Trying to Capture
The convergence thesis is that a specific geographic region is becoming the densest concentration of frontier AI-Industrial-defense activity in the United States. The thesis is articulated on the Austin as the Model 5IR City page. The architecture described above is what renders the thesis as a navigable empirical structure.
Three dynamics make the geographic-and-entity dual coverage important:
Multi-anchor supplier rings make geographic concentration visible at the dataset level. When the same operator (Linde, ASML, Vertiv, Schneider Electric) appears across multiple anchor supplier datasets with different facility identifiers, the cross-anchor pattern surfaces only because the geographic and operator attributes are first-class fields. Single-anchor coverage misses the cross-anchor pattern. AustinIO's structure makes it queryable.
Captive arrangements connect anchors to anchors in ways that change the supply-chain analysis. Samsung Taylor is not a generic foundry that happens to be near Tesla. It is Tesla's captive-equivalent foundry under multi-year arrangements covering AI silicon across vehicle, humanoid, training compute, and research silicon. The captive relationship is itself a structural feature of the convergence. Surfacing it requires explicit anchor-to-anchor links rather than just operator-level coverage.
Federal strategic-infrastructure designations overlay on geographic concentration in ways that compound. Project Matador (DOE-coordinated), TIE NGMM (DARPA-coordinated), Golden Dome SBI silicon supply chain (Space Force-coordinated), F-35 production (USAF), Fort Cavazos (Army), and prospective Trusted Foundry positioning (DMEA / intelligence community) all anchor in or pass through the same Texas geography. The federal-anchor overlay is its own pattern that the architecture surfaces by tagging anchors with their federal program relationships.
Each layer of the architecture exists to make a different facet of the convergence queryable. The full convergence is what emerges when all layers are read together.
What This Architecture is Not
AustinIO is not a comprehensive directory of every company in Austin or Texas. The directory pages cover meaningful categories at meaningful depth; they do not aim for exhaustive coverage of every entity. Coverage is deliberate, not algorithmic.
AustinIO is not a forecasting service. The site documents the convergence as it forms and as it has formed. Forward-looking framing is articulated where it grounds in observable structural pressures, not as prediction.
AustinIO is not a substitute for the broader supply-chain coverage on EX, SX, and DX. Where AustinIO covers a supply chain, it does so through the geographic lens — what physically converges in Texas. The broader category-level coverage of the same supply chains lives on the network's other properties. Cross-property links surface the relationship.
AustinIO is not editorially neutral about the convergence thesis. The site argues, through the structure of its coverage, that the geographic concentration described on the Model 5IR City page is structurally real and analytically distinctive. The architecture exists to render that argument as a navigable knowledge structure rather than to leave it implicit.
Related Coverage
Austin as the Model 5IR City | Spotlights Hub | Giga Austin Nexus | UT Austin Nexus | Austin Startup Nexus | Austin CapEx Nexus | Texas Triangle Cluster | Texas Energy Nexus | Industrial Triad Buildout | Workforce & Talent | Glossary