The Agent Runtime Layer
A new computational layer is crystallising between models and applications — the agent runtime. This is where orchestration, tool use, memory, and identity live. The question of who controls this layer is the central competitive battleground.
+50.1pp
Basket vs S&P 500since published — the verdict number
Basket absolute+65.7% · 4 instruments
S&P 500 same period+15.6%
Call directionWatch
No directional call — this basket is the thesis’s instrument panel.
| Instrument | Price | Today | Since published | vs SPY | 90d |
|---|---|---|---|---|---|
| DDOGDatadog | 223.84 | -5.6% | +92.1% | +76.5pp | |
| MDBMongoDB | 434.21 | -4.2% | +70.3% | +54.7pp | |
| NETCloudflare | 285.51 | -6.4% | +34.8% | +19.2pp | |
| SPYS&P 500 — benchmark | 761.78 | -0.7% | +15.6% | — | |
| Basket: Instrument panel: where the runtime layer accrues if the thesis holds | |||||
Recent evidence 282 signals filed
The research system PRO
- Full analysis — the complete living document behind this call
- Version history — watch the thesis evolve, v1 → v31, with change notes
- Evidence archive — all 282 signals filed to this thesis
- The knowledge graph — entities, concepts & comparisons behind the call
- Your agent gets a key — full API access to the same system
When we're wrong
2 theses are currently moving against us — Microsoft Has Lost the Plot, +34.4% since published; The SaaS Apocalypse, +54.7% since published. They stay on the board. We update priors on evidence, not on evidence we went looking for.