Is the Supply Chain of Intelligence an AI stack — or a strategy framework?
It gets filed under both, and the confusion matters. A stack tells you how to build. A framework tells you where the money goes. Anand Arivukkarasu’s Supply Chain of Intelligence is one of these things pretending, briefly and deliberately, to look like the other.
Search for the Supply Chain of Intelligence and you will find it described, variously, as an AI stack, a market map, a maturity model and a strategy framework. Some of that is lazy tagging. Some of it is the framework’s own fault: it borrows the visual grammar of a stack — ten horizontal layers, resources at the bottom, the user’s screen at the top — and then uses that familiar picture to make an argument no stack diagram has ever made.
So which is it? The honest answer is that the question has a correct resolution, and getting it right changes how you use the thing. This desk covered the framework’s mechanics in a companion explainer; here we take up the narrower classification argument, because US product teams keep reaching for the SCoI with the wrong job in mind.
What an AI stack actually is
A stack is an engineering artifact. It describes how a system is assembled: silicon at the bottom, then infrastructure, then models, then orchestration, then applications. The arrows point up because that is the direction of dependency. Each layer serves the one above it, and the whole diagram exists so that builders can answer a practical question — what do we need to build, what do we buy, and what breaks when a vendor deprecates an API.
Stacks are genuinely useful for that job. What they cannot do is tell you anything about economics. A stack diagram of the spreadsheet industry in 1995 and a stack diagram of the same industry in 2005 would look nearly identical. In one of those years the value sat with the application vendor; in the other it had migrated to the platform underneath. The stack does not move when the money moves. That is not a criticism — it was never the stack’s job.
What a strategy framework is for
A strategy framework answers a different question: given how value moves through this market, where should a specific company position itself, and what will happen to that position over time? Porter’s five forces is not a diagram of how factories work. The value chain is not an org chart. They are lenses for locating power, and they are judged by whether the locations they identify turn out to be where the margin actually sat.
Measured against that standard, the SCoI is plainly a strategy framework wearing a stack’s clothes. The tell is in what the author spends his pages on. A stack documentation would specify interfaces. The paper specifies four laws about how value behaves — it commoditizes downward, accrues at bottlenecks, splits between attention and power, and forces generation apart from verification — plus three currents that move budget, attention and capital across the layers sideways. None of that is engineering. All of it is economics.
A stack is a picture of how systems are built. The SCoI is an argument about who gets paid.
Side by side
The cleanest way to settle the classification is to put the two instruments next to each other on the dimensions that matter to a US operator choosing between them.
| Dimension | An AI stack | The SCoI |
|---|---|---|
| What it shows | How systems are built — components and their dependencies | Who gets paid — where value concentrates and why |
| Unit of analysis | Technology components: chips, models, APIs, apps | Economic positions: scarce inputs, bottlenecks, gates, compounding assets |
| Direction of flow | Polite and upward — each layer serves the one above | Hostile and sideways — value migrates to scarcity, collapses at abundance |
| Question it answers | What do we need to build or buy? | What do we own that survives the next model release? |
| Shelf life | Stable — the components change slowly | Versioned — market readings are dated and re-issued as layers shift |
| Failure mode | Becomes a vendor's marketing diagram | Becomes astrology if the readings are never updated |
Why the confusion persists
Three reasons, in descending order of charity. First, the layered visual is genuinely stack-shaped, and people classify by silhouette. Second, the word “supply chain” gets misread by anyone arriving from logistics, which is why the FAQ spends a full section disclaiming freight and procurement. Third — least charitably — “stack” is the safer label for anyone selling tools, because stacks imply purchasing decisions and frameworks imply strategic ones, and nobody’s marketing department wants to tell a buyer their layer is about to be commoditized.
There is also a real boundary case worth conceding. The SCoI’s fifty sublayers are specific enough — retrieval plumbing, agent identity, eval gates — that engineering teams do use them as a build checklist, and in that narrow use it behaves like a stack. That is a legitimate borrowing. It does not change what the instrument is.
Which one to reach for, and when
Reach for a stack diagram when the question is architectural: what components exist, who supplies them, where the integration risk sits. Your platform team needs one and probably already has three.
Reach for the SCoI when the question is positional: which layer do we own, what compresses us, and on what timeline. The framework’s own test is a single sentence — name the bottleneck you own. A stack cannot ask that question because, to a stack, every layer is equally respectable.
And reach for neither when the question is forecasting. The SCoI is explicit that it is descriptive, not predictive: it will tell you which current is moving value, not which company wins. Teams that treat any framework as a crystal ball end up in the same place as teams that treat a stack diagram as a moat — surprised, roughly one model release later.
The verdict
The Supply Chain of Intelligence is a strategy framework that uses a stack as its staging diagram — deliberately, because the substitution is the argument. Where the stack says “value flows politely upward,” the framework says “value concentrates where inputs are scarce and migrates the instant a layer below commoditizes you.” Same picture, hostile annotation.
For US product and investment committees, the practical rule is this: keep your stack diagram for the architecture review, and bring the SCoI to the meeting where someone claims a moat. The full paper, glossary and dated market readings are free at supplychainofai.com, with the canonical text at supplychainofai.com/paper.