Correction: the Issue 43 and Issue 44 board snapshots were declared from engine state artifacts in the wrong schema
PENDING · analyst declared 2026-10-27, ratification owed at the publisher
A record shown as PENDING has not been ratified by the publisher and publishes as pending. Do not render a pending correction as in force.
- id
- CHQ-CORR-2026-017
- class
- CORRECTION
- subtype
- provenance
- status
- PENDING
- authority
- analyst declared 2026-10-27, ratification owed at the publisher
- effective
- Not recorded
- published
- 2026-10-27
- title
- Correction: the Issue 43 and Issue 44 board snapshots were declared from engine state artifacts in the wrong schema
- what was wrong
- The files declared as the Issue 43 and Issue 44 board snapshots were outputs of the trigger engine. They carried engine fields instead of the published board fields used by the Issue 41 and 42 snapshots, and their watch field recorded whether a candidate row existed on the record rather than the published Watch state. Read as a board snapshot, Issue 43 appeared to add Watch up on four conditions and Issue 44 a fifth. Neither occurred.
- what is true
- Ratings and Outlooks in the engine artifacts were correct and are carried over unchanged. The published Watch state at both cutoffs is Watch up on SC-2026-004 and SC-2026-011 only.
- what changed
- Both snapshots are regenerated in the published board schema, in the Issue 42 field order and serialization, with the Pre-Disclosure Exploitation display name from Issue 43 onward. New digests: Issue 43 b5b98806732f64b729769623cd2c1286be5cfe632f457953c26dd82760838e6f; Issue 44 ef4d234cd5296f47137a793e1a9c420c050df555c8b5e910a30642c0173bcf77. The superseded digests, which belonged to the engine artifacts and were never published, are 157cde4a655e0e2b112e9679f5076188d506f7b32e7772e165757a5467904dd4 and f42cc50ee6fd1a8c7a14d8ea40eaa407016eb729089ad12903a061940d71a2b1. The engine artifacts are retained internally as engine state and are not served.
- what did not change
- No rating, Outlook, Watch, count or evidence status changed. Nothing was published under the defective artifacts, so this is a pre-publication correction.
- control analysis
- An engine state artifact and a published board projection are different objects with different schemas, and the snapshot register did not record which it held. A check requiring every file declared in the snapshot register to validate against the published board schema before its digest is recorded is proposed as a candidate, not an implemented control.
- verified after
- The Issue 42 to 43 difference is the condition name change alone. The Issue 43 to 44 difference is the two Outlook changes alone.
- found by
- The site build agent, on comparing the supplied snapshots against the sync instructions. It declined to edit the snapshots and asked for reconciliation, which was the correct response.