Home / Research / Bitemporal Threat Records
Biosecurity data

Bitemporal Threat Records

An event date and the date the organization learned about it are different facts.

2026-10-28·Biosecurity data·bitemporal-threat-records
Research note: scope, status and evidentiary limits are explicit; a methodological primer is not a completed experiment.

The problem

An event date and the date the organization learned about it are different facts. Backfilled outbreak announcements can cause a contemporary dashboard to misrepresent what was knowable earlier.

Analytical approach

Use valid time, recorded time, publication time and revision history separately. Never overwrite an old state without retaining its provenance.

Falsifiable test

Reconstruct the database as known at a past decision point; if impossible, the data model lacks historical auditability.

Operational implications

A defensible workflow should record the exact input, collection method, version, context, counter-explanation and reason for the conclusion. Reviewers should be able to disagree with the inference without losing the underlying observation. When this topic is applied to a real investigation, safety, lawful authority and domain-qualified professional guidance take precedence over a generic article.

Next research step

Publish a small case study with a documented baseline, an adversarial or failure-mode control, outcome criteria and enough data to reproduce the result. Report inconclusive findings alongside successes. This page is a research primer, not a claim that the proposed test has already been performed.

Source and revision record

Original editorial analysis and definitions. For background reference, consult the source catalog.

Published in this site build: 2026-10-28. · Editorial and correction policy