# Correction: an integrity check reported a digest that is not the delivered file's, without saying so

- **Artifact ID:** CHQ-CORR-2026-024
- **Status:** IN FORCE
- **Public record:** https://record.cybersecurityhq.com/corrections/chq-corr-2026-024
- **Machine-record SHA-256:** `55c3c53ad23652b295b5a51cc24f0d85562b176edbafcb89b8162e488eb6fc09`

## Complete structured record

```json
{
  "id": "CHQ-CORR-2026-024",
  "class": "CORRECTION",
  "subtype": "provenance",
  "status": "IN FORCE",
  "authority": "DM ratified 2026-11-12",
  "effective": "2026-11-12",
  "published": "2026-11-12",
  "title": "Correction: an integrity check reported a digest that is not the delivered file's, without saying so",
  "what_was_wrong": "On 1 November 2026 the integrity gate's store check recorded one digest for the registry artifact while the delivered file hashed to another. The check passed and did not say that the digest it recorded described the file before the gate wrote its own results into it.",
  "what_is_true": "Both digests are correct for what they describe. The first is the artifact as the gate read it; the second is the delivered file, and it is the one named in the separate attestation, which also records that the store was rebuilt from those exact bytes. A file cannot carry its own hash, so the value recorded inside the artifact can never equal the delivered digest.",
  "what_changed": "The check's detail now states that its digest is the pre-write digest and names the attestation that carries the delivered one. The artifact is no longer sent for review without its attestation.",
  "what_did_not_change": "No digest, count, rating or Outlook.",
  "control_analysis": "The control worked and its report was ambiguous. Two reviewers hashed the file independently, which is the right check, and could not complete it because the attestation did not travel with the artifact.",
  "found_by": "An external adversarial review."
}
```