Methodology
How the figures in this publication come together, how bands are built, and when we mark a regime break. This document is public, numbered, and changes only through a registered revision.
Effective 2026-09-12 · version 1.0
Article 1 — Source tiers and as-of dates
- Every data point carries a source tier: T1 primary analyst or industry press with its own data collection (TrendForce/DRAMeXchange, earnings calls, company newsrooms), T2 major press with secondary reporting, T3 derived or aggregated (news wires, aggregator boards).
- Every data point carries an as-of date and a confidence label (high/medium/low). Missing as-of dates are marked as such; no date is invented.
- Conflicting sources stay side by side. We do not average and do not pick after the fact; a conflict is a finding, not noise.
Article 2 — Forecast pipeline (Q+1 to Q+3)
- Forward series run through a Holt damped exponential smoothing pipeline (damping factor φ = 0.8; smoothing parameter α selected per series by backtest on enforcement of the 80% band).
- Bands are built constructively from the backtest residuals: 80% and 95% bands, symmetric on the QoQ scale. Bands are not adjusted to outcomes after publication.
- Where a primary analyst (TrendForce) publishes its own quarterly estimate, that is taken as the consensus point; the model runs alongside it, not through it.
- Output is machine-readable:
forecast/forecast-output.json, generated byforecast/forecast.py(public in source).
Article 3 — Horizon: no levels beyond Q+3
- Beyond Q+3 this editorial team publishes no numeric levels. The reason is measured, not principled: WSTS revised its own 2026 growth from $975 bn (Nov 2025 edition) to $1.51 tn (Jun 2026 edition) — a more-than-doubling revision within seven months.
- For 2027–2029 we publish named, anchor-bound scenarios (Outlook): per year a direction (tight / easing / loose) forced by dated, capital-committed events. A scenario without an anchor per year is not shown.
Article 4 — Regime flags
- A regime break is marked when the consensus itself reclassifies its outcome by more than 50% within two publication cycles, or when a primary source changes a structural premise (export restrictions, EOL announcements, capex-guidance changes).
- A regime flag does not suppress existing data; it marks that the validity of existing bands has widened.
Article 5 — Publication cycle and revisions
- The edition appears monthly (next: 2026-10-10) and is revised in between on a material event (earnings, contract rounds, cleanroom openings).
- Revisions are additive: a revised value does not replace the previous one in the public series but gets a revision step. TrendForce’s revision ladder (+90–98% → +58–63% → +13–18% → +8–13%) is visible on these pages as an example of the method.
Article 6 — Revision table of this document
| Version | Effective | Change |
|---|---|---|
| 1.0 | 2026-09-12 | First public version. The method described here has been in use in this form since 2026-08-28 (introduction of Holt damped ETS after a backtest scan); earlier editions followed the same source-tier discipline. |
| 1.1 | 2026-09-18 | Full English text; publication made company-neutral (white label). |