One Load-Bearing Company

No single filing tells you how many critical systems run on OpenAI. That's the point. The dependency graph pulls from multiple disclosure sources, and when you filter to any one of them, most of the picture goes dark. The risk isn't in the document. The risk is the gap between documents.

Filter the OpenAI dependency graph to any single disclosure source and watch most of it disappear. The systemic risk lives in what no one filing can see.

The uncomfortable thing about OpenAI's counterparty concentration isn't any single disclosed dependency. It's that the full picture only appears when you pull from multiple disclosure sources at once. Filter to any one of them and the graph mostly goes dark. No category system renders the whole risk because no single filing contains it.

Counterparty concentration risk is usually something you can find in a filing. OpenAI's version is harder: the dependency graph has to be assembled across multiple disclosure sources, because no single one contains it. Filter to just SEC disclosures, or just vendor contracts, or just infrastructure filings, and most of the graph disappears. The risk isn't buried in a document. The risk is the white space between documents.

Filter the OpenAI dependency graph to any single disclosure source and most of it goes dark. The systemic risk isn't in any one filing. It lives in the gap between them.

No single filing shows how many critical systems run on OpenAI. The dependency graph has to be assembled across sources. Filter to any one and most of the picture disappears. The risk is the gap, not the document.

No single filing tells you how critical OpenAI has become to the broader infrastructure stack. That's the uncomfortable part. The dependency graph for 'One Load-Bearing Company' pulls from multiple disclosure sources, and when you filter to any one of them, most of the picture goes dark. The risk isn't in any document. It's in the gap between them. https://www.jakelawrence.xyz/research/one-load-bearing-company