The Investable AI Stack, Part I: The Great Split and Who Captures the Value

A DeltaSignal river. Published by DeltaSignal (AITrailblazer).

River code TF-RIVER-AI-STACK-1 · Key K-77a04a89104b1b70 · Page address https://atlas7.app/rivers/ai-stack-1

Thesis

Structural map of who captures value in the AI stack

The river at a glance

Founding article, July 17, 2026October 30, 202677 of 96 flagged items are reviewed members (7%); the rest are candidates no reviewer has read in.7 members, reviewed89 candidates flagged, unreviewed

Founding article

The Investable AI Stack, Part I: The Great Split and Who Captures the Value, July 17, 2026. The founding article is the river's source: its claims below are extracted from it, and its break conditions supply the falsifier they are graded against.

Members

Articles read into this river by a reviewer, in article-date order. The founding article is first. Membership is reviewed by hand under the river's protocol; machine-flagged candidates are counted at the bottom of this page and are not members.

Claims

Claims extracted from the founding article and approved for publication. Each carries the condition that would break it.

Claim 1 · empirical
Local models, often under 10 billion parameters, now account for more than 90% of open-source downloads.

What would break it: Open-source download statistics show models under 10 billion parameters accounting for 90% or less of downloads.

Claim 2 · mechanism
Value shifts away from undifferentiated model access and toward the surrounding stack: chips and advanced packaging, networking and memory, enterprise servers and private infrastructure, data preparation and governance, orchestration and workflow control, and security, permissions, and observability.

What would break it: Undifferentiated model-access providers capture the dominant share of AI value-chain profit while the surrounding stack layers commoditize and lose pricing power.

Claim 3 · mechanism
Alphabet's advantage is structural integration, not model quality alone: proprietary frontier models, DeepMind research, custom TPUs, Google Cloud, search distribution, consumer applications, proprietary data, and advertising monetization connect directly, reducing its dependence on third-party accelerators.

What would break it: Alphabet's AI deployment remains materially dependent on third-party accelerators, or its distribution and advertising surfaces fail to convert AI capability into cloud and ad revenue while its infrastructure spending produces no new revenue or profit-pool protection.

Claim 4 · empirical
Palantir's supplied figures show first-quarter 2026 revenue growth of 85% and a 112% increase in U.S. commercial remaining deal value.

What would break it: Palantir's reported first-quarter 2026 results show revenue growth other than 85% or a U.S. commercial remaining deal value increase other than 112%.

Claim 5 · empirical-forecast
Undifferentiated standalone frontier-model startups and mid-tier proprietary model vendors are the likely frontier-layer losers: they face enormous capital requirements, rising certification costs, and limited distribution versus the hyperscalers, while remaining too expensive for narrow tasks that can move to smaller local models.

What would break it: Standalone or mid-tier proprietary model vendors secure distribution and capital on terms comparable to hyperscalers and hold premium pricing and share in both frontier and narrow-task workloads.

Claim 6 · mechanism
AI increases the importance of data gravity: for many companies, moving a model closer to protected enterprise data is easier and safer than repeatedly sending sensitive data to an outside model, which favors Oracle's installed base of databases, regulated workloads, and systems of record.

What would break it: Enterprises predominantly migrate regulated data and systems of record off incumbent platforms like Oracle's toward external model providers, and Oracle's position in enterprise AI workloads shrinks.

Claim 7 · empirical-forecast
The market will segment: the largest models become premium reasoning utilities, while smaller models increasingly operate as embedded machinery, specialized and closer to the workflow.

What would break it: Frontier models absorb routine narrow tasks (invoice reading, document classification, ticket routing) at prices that make local embedded deployment stagnate or shrink.

Claim 8 · thesis
The AI market is forming a barbell: capital-intensive frontier platforms run by hyperscalers at one end and compact local models at the other, with the middle (general-purpose model vendors without frontier-level performance, proprietary hardware, enterprise distribution, or a defensible path to deployment) vulnerable.

What would break it: Mid-tier general-purpose model vendors without frontier performance, proprietary hardware, or enterprise distribution durably gain enterprise share and sustain premium pricing against both hyperscalers and local models.

Claim 9 · mechanism
Meta's open-weight models can weaken the pricing power of closed-model providers while improving Meta's own advertising, recommendation, content, and engagement systems; Meta's largest benefit is internal value capture, not direct model licensing revenue.

What would break it: Closed-model providers' pricing power is unaffected or rises as Meta's open-weight models spread, or Meta's AI value shows up primarily as standalone model licensing revenue rather than improved core-platform economics.

Claim 10 · mechanism
Microsoft is less dependent on the long-term dominance of any single model provider than is often assumed, because enterprises consume AI through its existing software contracts, identity, permissions, security controls, and workflows (Azure, Microsoft 365, GitHub); the model can change while the surrounding control system remains in place.

What would break it: Microsoft's AI revenue and margins prove tightly coupled to one model provider's dominance, or enterprises predominantly bypass Microsoft's stack to consume standalone models directly.

Claim 11 · mechanism
The durable enterprise product is the control plane, not the model: the systems that connect models to corporate data, permissions, applications, and auditable workflows (Microsoft's agent-control environment, Palantir's governed orchestration, ServiceNow's workflow ownership) are harder to dislodge than models, which become cheaper and easier to replace.

What would break it: Enterprises routinely replace their workflow, permissions, and orchestration platforms when switching models, and durable profit accrues to model providers rather than to the owners of workflow and systems of record.

Candidates

The archive linker currently flags 89 items (0 articles, 89 notes) as candidates for this river. Candidates are machine-flagged by keyword, reviewed under the protocol below, and are not members. Measured on October 23, 2026, 29.7 percent of the linker's article edges were confirmed substantive membership on blind review, 41.5 percent counting borderline calls.

How this river is kept

Cadence: weekly scan with the flywheel run; validation events recorded as they occur.
Incorporation: linker candidate edges reviewed by Atlas at the weekly scan; founding and curated edges are human-asserted; candidate edges are never presented as membership until reviewed.
Grade rule: framework validations graded 1-3 on primary sources with a named falsifier, per standing framework practice.
Retirement: no new member and no validation for 12 months, or the thesis falsified on its own named falsifier, marks the river lapsed; the record is kept and labeled lapsed, never deleted.
Owners: surveillance, Atlas; editorial, Rada. Protocol adopted 2026-10-23. Status: living.