Last updated 9 September 2026

Corrections

Report a concern or read the correction record.

Reporting a concern

To report an error or raise a concern, email hello@machinecanon.com with the page link, the specific content and your reason. We review reports and may correct, restrict or remove material. Applicable legal duties still apply.

Substantive corrections are identified on the affected study. Ordinary editing does not require a correction entry. Public withdrawal and deletion of stored information are separate processes; see the Privacy notice.

Standing limitations

These are not errors, but they apply to everything on this site and are easy to lose sight of:

The log

27 August 2026 · The same favorite word · before publication

Claimed “serendipity” appeared zero times under the keep-one framing. It appeared once. The parser missed a response from Cohere’s Command-R because the word was wrapped in quotation marks. Found by searching the raw text directly rather than trusting the parsed counts. Corrected to “once in 513” before the study went up.

27 August 2026 · The same favorite word · citation

A cited DOI did not resolve, and a page range was wrong. McGregor et al. (2019) was cited with DOI 10.1215/00031283-7573156, which returns a 404, and with pages 380–403. The paper is real; the link now points to the Duke University Press article page and the range is corrected to 380–396.

26–27 August 2026 · Three runs discarded

A 720-call run was thrown out after 505 calls failed instantly to an OpenRouter in-flight spending limit. The failures were spread evenly across labs and conditions, which would have read as a symmetric finding had they been coded rather than investigated. A second run lost roughly 40% of its calls to a network outage on the collecting machine, and an earlier run was discarded because a low token limit truncated answers at the moment models named their choice. All three are recorded in the project’s incident log.

26 August 2026 · The same favorite band and butt rock · open

Two models were reported as returning nothing. They were starved, not broken. GLM-5.3 and Qwen3.5 9B produced empty responses because the token budget was consumed by their reasoning before any answer was emitted. Both pages still describe a 28-of-30 panel. This correction is outstanding: the affected runs need repeating at an adequate budget, and the pages updating.