What changed, and when.

1. 2026-09-11

   Revision 2026.09.2

   Runs of a fixed length, and a deep run with seven stages

   • Both runs are a fixed length from launch to report: three minutes for the standard run and eight for the deep run. The last stage runs to the run's deadline, so a slow shader compile shortens it instead of lengthening the run.
   • The standard CPU stage is 60 seconds, past the 56-second boost window some boards use as well as the common 28-second one. The standard GPU stage is 50 seconds.
   • Path tracing runs over a fixed time, paced to about 150 samples, instead of stopping at 150 samples. The pause before it is gone, because a pause lets the machine cool.
   • The deep run has seven stages: the screen's refresh rate, frame pacing and late frames; two and a half minutes of CPU load; memory; the GPU pass looped three times; CPU and GPU loaded together; path tracing; and a hot re-test of the CPU against the cold stage.
   • Reports from before this revision are not compared with reports from after it.
2. 2026-09-07

   The scene in the window, the reading beside it

   • Every stage shows the thing under load in the window (the fire loop with a bar per core over it, a bar per stream for memory, the raster scene, the tracer resolving) and does the reading in the side pane: trace, readout, phase markers, tiles, checkpoints, what comes next.
   • Set-up is one screen: the processor, what the browser already detected, the kind of run. The fake graphics-probe animation is gone.
   • Every content page has a plain-text twin at its address plus /llms.txt for AI readers. Landing pages for seven audiences and seven symptoms. Pricing, FAQ, security, accessibility and this page.
   • Copy tightened across the site; the homepage no longer claims a contention class the classifier does not have.
3. 2026-09-07

   The report opens in plain words

   • Is the cooling good, what the machine is good for (everyday, coding, photo, video, gaming, AI), strengths and weaknesses, before any chart.
   • Apple M-series and Qualcomm Snapdragon X parts in the processor catalogue, 1,634 entries in all.
4. 2026-09-07

   Revision 2026.09

   The deep run

   • A three-minute CPU stage that reaches thermal saturation, with the settled level taken as the median of three windows and its spread stated, and the time to saturation.
   • The GPU pass looped three times with a worst-over-best stability figure in 3DMark's form.
   • The CPU stage pauses when the tab is hidden and the report says so. A run on battery, a single-core fallback and starved workers are flagged as run quality.
   • Validated on real hardware; the saturation gate scales with the measurement's own noise. Written up in the methodology.
5. 2026-09-07

   Validated on a real machine, and fixed what lied

   • The chunk ledger attributes worker work to 250 ms windows by overlap on a shared clock. Warm-up excluded from the peak; consistency and noise floor computed on one-second means.
   • The curve classifier became noise-aware: reversal and dip gates scale with the noise floor and confidence is capped when noise is high. Twelve real runs are the fixture.
   • Contention that quietly shares a core was shown not to be detectable within one run, and the site now says so instead of claiming it.
6. 2026-09-06

   A cause, not just a decay figure

   • The CPU curve is classified as held, a single step down, a steady slide, oscillating, erratic, dipped and recovered, or insufficient, with a stated confidence.
   • The paid half of the report is built from the class: the cause, the first fix and the retest target. The invented percentile and synergy figures were removed.
   • Before/after: the last five reports stay in the browser and a run on the same processor is compared curve over curve, with anything inside the run-to-run spread called no change.
   • Email a link back to your own report, where the deployment has it configured.
7. 2026-09-05

   Security and request guards

   • Signed report tokens, per-route rate limits, size-capped and field-validated bodies, a content security policy and the full set of security headers.
   • Analytics and error reporting proxied through this origin. Dependency fixes and a green browser suite.

A revision bump means two reports either side of it are not comparable; the report carries its revision. Corrections follow the corrections policy.