AGmind Request a scope

Policy

Errata

Corrections are part of the record. This page defines when a published result is corrected, superseded or retracted, and keeps the full history visible.

What triggers a correction

A correction is opened when any of the following is confirmed against the raw evidence:

  • a factual error in a published card or report — a wrong version identifier, a wrong SKU, a documented feature described incorrectly;
  • a defect in the harness, workload revision or measurement path that affects a published result;
  • an error report from a reader, vendor or client that is verified against the stored evidence bundle.

A later change in a critical layer — BIOS, kernel, driver, runtime, image or model artifact — is not a correction: the result was valid for the tested cell. The affected card is instead marked as requiring revalidation until it is re-run.

Every correction is dated, listed in the log below and linked from the affected page. The original text remains available.

Superseded and retracted

A corrected result never disappears. It carries one of three statuses:

Status Meaning
active The current, valid revision of a result.
superseded A newer revision replaces this result. The old page stays published, marked, and links to its replacement. Its conclusions are historical, not withdrawn.
retracted The result itself was invalid — for example a measurement defect or a wrong configuration record. The claim is withdrawn; the page and its evidence remain visible with the reason stated.

Run identifiers are preserved permanently: run IDs are never reused and never deleted. Invalid runs stay in the evidence bundle, marked invalid with the reason recorded — deleting them would hide exactly the failure history the lab exists to record.

Correction log

No corrections yet

The lab has not published results yet, so there is nothing to correct. This log begins with the first published card or report and will record every correction after it.