Skip to main content
CybersecurityHQ Structural Conditions Board
Primary navigation
Issue 46 · as of Issue No. 46, 12 November 2026 (observation cutoff 9 November 2026; collection closed 9 November, 16:28 UTC) · Snapshot ea7de8184295

Correction: nine pattern counters were arithmetically impossible

Every record in this file was ratified by the publisher on 2026-11-12 and is in force. The declared field gives the date the correction was first recorded.

id
CHQ-CORR-2026-025
class
CORRECTION
subtype
control
status
IN FORCE
authority
DM ratified 2026-11-12
effective
2026-11-12
published
2026-11-12
title
Correction: nine pattern counters were arithmetically impossible
what was wrong
In an internal pattern summary, nine rows carried a 30-day reinforcement count larger than the 90-day count. The fields were maintained by hand and nothing recomputed them; several values were cumulative totals entered in the 30-day column. The summary also held one duplicate row and one misplaced cell.
what is true
These counters feed no condition count, rating or Outlook. The trigger engine computes its own windows from the evidence rows.
what changed
Every counter was recomputed from typed fields under a stated rule: 30 and 90 calendar days ending on the run date, counting reinforcing and counted entries by catalog date, or by signal date where no catalog date exists. Sub-class counters were cleared because sub-class attribution is not held in a field. The duplicate row was marked and the misplaced text moved. Prior values are preserved in every earlier artifact.
what did not change
Every condition count, rating and Outlook.
control analysis
A gate check was added the same day so that an impossible counter cannot recur silently. The first application of this correction failed to clear some cells it logged as cleared; a negative test added with the new check caught that on its first run, and the cells were then cleared.
found by
An external adversarial review.