ShovelsSale.com / Blog / Layer Intelligence
From Hype Cycle to Dependency Map
Market waves generate excitement at the surface. Durable analysis requires mapping who depends on whom — upstream, downstream, and through which bottlenecks.
Visible Hype vs Hidden Dependency
The hype cycle tracks attention: discovery, peak expectations, disillusionment, and eventual plateau. Dependency maps track structure: which layers must exist for the wave to function regardless of sentiment.
These are different objects. A wave can lose hype while dependency deepens. A wave can peak while critical layers remain unidentified.
Start With the Wave, Then Abandon the Winner
Name the wave — AI applications, creator commerce, climate infrastructure, agent platforms. Then suspend the question of who will win. Ask instead what every participant must rent, buy, route through, or comply with.
See How to Read a Market Wave Without Chasing Hype for the entry discipline.
Building a Dependency Map
A dependency map lists layers and links: miners at the visible edge, shovels that enable them, gatekeepers that constrain access, and upstream suppliers that constrain shovels.
Draw arrows for necessity, not admiration. If layer B cannot operate without layer A, A belongs beneath B on the map — even if A is less famous.
Upstream and Downstream Actors
Upstream actors supply constraints: equipment, architecture licenses, fabrication capacity, payment rails. Downstream actors consume outputs: apps, merchants, publishers, operators.
Strategic position often sits upstream of the visible downstream race because many downstream actors share the same upstream dependency.
Bottlenecks and Replacement Difficulty
Mark bottlenecks where substitution is slow, expensive, or politically constrained. Replacement difficulty turns a dependency line into a structural claim.
Not every dependency is strategic. The map must distinguish convenient tools from layers that halt the wave when removed.
Control Layers on the Map
Control layers appear where access, standards, or records are mediated. They may not supply the core product, but they shape who participates and under what rules.
See The Control Layer for how governance mechanisms appear on dependency maps.
How Dispatch Dossiers Reveal Layers
Dispatch intelligence dossiers are governed case studies of single nodes on a dependency map. They document source-backed claims about layer position, contested signals, and replacement difficulty — not headline narratives.
Reading multiple dossiers in sequence reveals stack depth: compute above fabrication above equipment; applications above payments above identity.
How to Use This Concept
- Define the market wave in one sentence.
- List miners, shovels, gatekeepers, and upstream suppliers.
- Draw dependency arrows and mark bottlenecks.
- Test layer claims in the Shovel Scanner.
- Compare your map to relevant Dispatch dossiers and revise.
Related Dispatch Cases
- Dispatch 001 — NVIDIA — Compute layer atop which many AI miners depend.
- Dispatch 009 — TSMC — Manufacturing layer beneath chip design and AI silicon.
- Dispatch 010 — ARM — Architecture specification upstream of mobile, cloud, and AI chip implementation.
- Dispatch 011 — Broadcom — Aggregation layer across data-center and enterprise dependency chains.
Request the Dispatch Briefing
Notes when new dependency-map-relevant dossiers are issued.