Separate the two years when first reading a 2026 threat report
Preserve publication edition and actual incident-observation period as different metadata.
The cover year is not the observation year
A report titled 2026 does not necessarily describe incidents occurring in 2026. Confusing publication and observation years also undermines comparisons. Truthound can check a table preserving their different meanings.
The period in the 2026 edition
ENISA published Threat Landscape 2026 on September 22, 2026. Its introduction states that the analysed observations run from January 1, 2025 to December 31, 2025. Related content on the page includes the separate 2025 edition with another period.
Build a first report register
Keep edition, publication date, observation start/end, region and source scope separately. Do not extract the title's year into an observation-year field automatically. Content sharing a page is not necessarily part of the report.
Do not import a related card's total
A total copied from the related 2025 edition would become false when labelled a 2026-edition figure, even if every digit was copied correctly. Preserve which document and passage each number belongs to.
The dates Truthound can check
Truthound Core Python SDK 3.3.4, operating on a prepared Polars table, provides DateOrderValidator for defined observation dates and InSetValidator for supplied edition categories. Operators verify the original definitions. The validator does not interpret the difference between author text and related cards automatically.
Compare the existing predicate
An existing Pandera 0.35.0 pandas predicate can remain. Compare a missing start date, another edition's period and mixed date types. A valid date format does not establish the right report scope.
Different periods can still be shown
Reports with different periods can be displayed together. Before calling their count difference a growth rate, compare duration, collection scope and classification. Comparable coverage matters more than a larger headline number.
Include a legitimate mismatch in the fixture
Include a valid fixture whose publication year differs from its observation year. Rejecting every such difference would reject correct metadata. Test source correspondence and internal period consistency instead.
Reuse the distinction next time
Reuse that distinction for the next report while checking its definitions again. Separating the two years is a small step that supports an evidence-based trend explanation.
Conditions
Separate the official author body from related cards and verify edition and period meanings.
Alternatives
Keep existing Pandera 0.35.0 pandas edition/date predicates where suitable.
Limitations
Metadata checks do not measure the overall threat or predict future attacks.
Evidence
- Event checked
- Subject checked
- Modified
