Skip to main content

Thesis sourcebook

Research worth keeping

A durable reading list for the AI trade. Submitted sources are preserved first; sector mapping, analysis, and thesis takeaways appear only after editorial review and an explicit publication decision.

Submitted
2
Published notes
2

Source inbox

Submitted research

Approved notes pair original-source provenance with a compact, thesis-linked read-through.

X POSTPublished note

SemiAnalysis X thread on Kimi K3 and linear attention

SemiAnalysis · SemiAnalysis

Published Jul 17, 2026 · submitted Jul 18, 2026

gpumemorynetworkingThesis MIXED

TL;DR

Reviewed: Full eight-post X thread

SemiAnalysis argues that Kimi K3 is not bearish for AI infrastructure despite using less KV-cache capacity. The thread's case is that K3's 2.8-trillion-plus parameter footprint favors rack-scale accelerators, distributing its weights raises interconnect demand, and limited HBM headroom pushes cache storage into DDR5 and NVMe. The bullish conclusion still depends on efficiency expanding total AI usage enough to offset lower cache intensity.

Summary points

  • K3's parameter count requires a large scale-up domain to hold its weights; SemiAnalysis presents that as a favorable workload for NVL72-class systems.
  • The thread says KDA can reduce networking needed for KV-cache transfers, while WideEP weight distribution can increase traffic across GPUs.
  • WideEP spreads 896 experts across accelerators. SemiAnalysis argues rack-scale copper fabrics are better suited to that pattern than lower-bandwidth multi-node systems.
  • Because the weights reportedly occupy more than 1.5 TB of HBM, the thread expects some KV-cache storage to spill into CPU DDR5 and NVMe even at relatively low concurrency.
  • The author says optimal K3 inference needs a rack with a scale-up domain of at least 64 chips, reinforcing the rack-scale rather than single-server read-through.
  • Investment read-through: constructive for GPU systems and networking, with demand shifting across HBM, DDR5, and NVMe rather than disappearing. It remains mixed evidence until real deployments validate utilization and aggregate infrastructure spending.
  • Watch: production node counts, network throughput, the HBM-to-DDR5/NVMe memory mix, accelerator utilization, and tokens served. The thesis weakens if per-workload savings outpace usage growth.

Editorially published Jul 18, 2026.

PDFPublished note

Situational Awareness: The Decade Ahead

Leopold Aschenbrenner · Situational Awareness

Published Jun 6, 2024 · submitted Jul 18, 2026

power coolingsuppliersadvanced packagingmemorygpunetworkingThesis CONTEXT

TL;DR

Reviewed: Full PDF; infrastructure and supply-constraint sections emphasized

Aschenbrenner's report is a scenario map for a multi-year AI infrastructure buildout: power, data-center construction, HBM, advanced packaging, and networking can become binding constraints. For the equity thesis, those projections are useful as a checklist—not evidence that the buildout or its returns have already materialized.

Summary points

  • The report frames the AI buildout as a full-stack capital cycle rather than a GPU-only story.
  • Power delivery, sites, and data-center construction can set the physical ceiling on how quickly compute is deployed.
  • HBM, advanced packaging, and networking translate the high-level compute thesis into measurable supply-chain bottlenecks.
  • Its forecasts are author scenarios from 2024. They should be tested against realized capital spending, power procurement, project starts, lead times, and capacity additions.
  • Investment read-through: infrastructure scarcity can support suppliers across several layers, but utilization and monetization must justify the capital intensity before constraints ease.
  • Watch: capex, grid interconnections, HBM and packaging lead times, deployment utilization, and financing. The scenario weakens if efficiency or weak demand reduces infrastructure needs faster than new workloads expand.

Editorially published Jul 18, 2026.

Editorial contract

From link to thesis evidence

This is a thesis tracker, not a social feed. A source earns a published note only when the interpretation is attributable, falsifiable, and useful for a specific layer of the AI stack.

  1. 01

    Preserve

    Store the canonical source and provenance without reproducing the full work.

  2. 02

    Categorize

    Map the source to relevant sectors and five-layer thesis facets.

  3. 03

    Analyze

    Separate the author's argument from our interpretation and testable read-through.

  4. 04

    Publish

    Release only after an administrator approves both the source and the exact note.