One-sentence brief
A large ledger becomes useful only when record type, status, source origin, coordinate precision, and unresolved verification remain visible.
WORLD EVENT LITERACY
How to use a 100-record-per-year event ledger without converting a supplied dataset into an authoritative historical database.
ORIENTATION
A large ledger becomes useful only when record type, status, source origin, coordinate precision, and unresolved verification remain visible.
WORKING BRIEF
The workbook covers 1999 through 2026 with exactly 100 records per year. A small group of specific-event rows sits beside a much larger recurring set of annual strategic-development rows. That design supports broad thematic comparison, but it also creates a risk that repeated annual themes will be mistaken for hundreds of separate incidents.
The site preserves the workbook and reports exactly, then adds an evidence-state label. It does not infer independent corroboration from a populated row, a source URL, a priority value, or agreement among the accompanying reports.
Each year has a durable Markdown anchor and a protected UAI record. Public filters use the same stable record IDs, so a correction can propagate from source map to route, timeline, glossary, and memory without renumbering the source row.
The workbook calls its URLs start-point references. Public presentation preserves that rule. One URL may be secondary, incomplete, stale, or itself based on another origin chain.
Filters may compare record type, focus bucket, status, impact scope, and year. They do not rank countries, populations, victims, ideologies, or historical worth.
The historical record ends before any branch control. A branch appears only for a specific historical dataset claim and is labeled FICTIONAL WHAT-IF — NOT A FORECAST.
Use the fixed branch controls to ask how a changed warning, coordination, or escalation condition might alter the questions an analyst would investigate.
COMPLETE DOSSIER
Terms are defined for this site’s evidence method, not as universal legal or clinical definitions.
| State | What the site may say | What it must not imply |
|---|---|---|
| Historical dataset claim | The supplied ledger represents the row as historical. | Independent verification, complete causation, or universal agreement. |
| Annual analytic series | A recurring theme is summarized for one year. | That the row is one isolated incident. |
| Contemporary or ongoing claim | The source records an unresolved or current claim. | That history has closed or the claim is settled. |
| Fictional what-if | One named condition is changed for educational comparison. | That the branch happened or will happen. |
| Illustrative projection | Possible second-order questions are shown. | A probability, prediction, forecast, or policy recommendation. |
Is the evidence state visible before the title or claim?
Pass condition: Historical, annual, contemporary, fictional, and projection states are named exactly.
Does fiction begin only after a visible boundary?
Pass condition: No scenario text appears inside the historical record block.
Are source URLs described as starting points?
Pass condition: No link count is treated as independent corroboration.
Are ongoing claims kept out of settled-history language?
Pass condition: The contemporary label and review cutoff remain visible.
Does the branch avoid targeting, cyber procedure, casualty optimization, and predictive certainty?
Pass condition: Output remains fixed, educational, non-identifying, and non-operational.
RESEARCH EDITION
This page follows the public method for provenance, confidence, source independence, alternative accounts, limitations, review state, and visible correction.
CONTINUE