The counter that showed 2 instead of 19

What the mismatch exposed#

At a documented September 30, 2026 checkpoint, the security figure fell as records expired. A displayed value of 2 contrasted with 19 qualifying published events. Those are historical case-study values, not today’s figures.

The original query counted the current public projection. When events became stale and left that projection, the count decreased even though WOUT had already published them.

The corrected definition#

The implementation records the first publication of an event separately from its presence in the current feed. The rolling metric counts security events that have been published and whose first report falls within the preceding 24 hours.

Merged duplicates and events later marked Disputed are excluded. Resolved or stale events can still qualify because this metric is historical. The initial recovery of older publication history used inference; that backfill should not be described as a perfect original publication log.

Current public signals

Unexpired records available in the present public view.

Published security events, 24h

Ever-published security events first reported within the rolling window, excluding merged and disputed events.

What the figure does not establish#

The figure is a count of qualifying WOUT events. It is not a count of every security incident in Haiti, a police statistic, a severity index, or proof of coverage.

The live analysis requests this existing public aggregate separately from its current-event sample. The two numbers can differ for legitimate reasons; an expired event can remain part of the historical metric.