Editorial Policy

Evidence, attribution, updates and corrections on ALCPU.org.

Evidence and scope

Use the original developer documentation for software behavior, processor documentation for model-specific specifications and system-maker guidance for cooling or hardware service. Separate observed data from explanations and recommendations. A temperature screenshot without sensor and workload context cannot support a broad safety claim.

Honest claims

Do not invent benchmark results, authors, credentials, affiliations, reviews or hardware tests. A planned test protocol must be labeled as a protocol. Documentation review is not the same as installing the application or checking the delivered binary. This edition corrects unsupported earlier claims of Windows testing.

Dates and corrections

Preserve publication dates. Change modification dates when substantive material changes and identify the review scope. Do not update dates merely to appear fresh. Operator contact details should be verified before enabling a corrections form. Until supplied, the contact page clearly explains this limitation.

Independent recommendations

Recommend actions according to the actual question and available evidence. Do not imply guaranteed safety, search ranking, AI citations or endorsement. Commercial licenses, warranty decisions and developer support remain with the relevant provider.