REAL-WORLD INTERPRETIVE

NUCLEAR TESTING HISTORY AND EVIDENCE

Event-Level Records, Device-Level Counts, and Grouped Detonations

How to compare national test totals without confusing a catalog row, a test event, a salvo, an operation, a device, or a wartime detonation.

Read the working brief Choose a learning path

REAL-WORLD INTERPRETIVE Editorial synthesis or explanation derived from sources and explicitly open to correction.

Confidence: Source-bounded
Sources: 3
Independent corroboration: 0
Jurisdiction: Global / varies by state, site, workplace, community, and public-health system
Date range: Nuclear records 1945–2017; pandemic examples and methods chiefly 21st century; source review current only to the supplied reports
Review: Repository-authored WIP.33 transformation — source identity verified; historical, scientific, numerical, legal, health, affected-community, accessibility, privacy, and specialist review remain pending

Estimated reading: 15 minutes
Review date: 2026-07-25
Stable route: /international/nuclear-testing/event-level-device-level-and-counting-conventions

Source boundary · evidence boundary

HISTORICAL DATASET CLAIM — SOURCE REVIEW REQUIRED. Exact source bytes and event rows are preserved, but preservation is not authentication. Event counts are event-level, grouped detonations may include multiple devices, exact CSV and companion narrative contain an open Soviet/Vela discrepancy, and public routes omit coordinates, device-design fields, burst/burial parameters, delivery details, raw source rows, blast modeling, targeting, and fictional nuclear branches. No participant data, no upload, no free-text case ingestion, no network request, no persistence, no analytics, and no model call. No output grants approval, accessibility certification, publication, operational, production, activation, or tuning authority.

LEVEL 1

ORIENTATION

Why this matters

REAL-WORLD INTERPRETIVE

One-sentence brief

Different institutions count nuclear history differently. Without a declared unit, apparently precise totals can disagree while each is internally consistent.

REAL-WORLD INTERPRETIVE

Three key points

State whether a total counts event rows, tests, devices, explosions, operations, safety experiments, peaceful-use events, or combat detonations.
Some South Asian tests and other salvos contain several devices but appear as one event row for a date. Device metadata must not be inferred when the source does not establish it.
Combat use, zero-yield safety experiments, peaceful nuclear explosions, joint tests, and unconfirmed events can move a total. A comparison must declare its rule set and source revision.

LEVEL 2

WORKING BRIEF

Evidence, context, and limits

REAL-WORLD INTERPRETIVE

Name the unit before the number

State whether a total counts event rows, tests, devices, explosions, operations, safety experiments, peaceful-use events, or combat detonations.

REAL-WORLD INTERPRETIVE

Grouped same-day detonations

Some South Asian tests and other salvos contain several devices but appear as one event row for a date. Device metadata must not be inferred when the source does not establish it.

REAL-WORLD INTERPRETIVE

Inclusion and exclusion rules

Combat use, zero-yield safety experiments, peaceful nuclear explosions, joint tests, and unconfirmed events can move a total. A comparison must declare its rule set and source revision.

REAL-WORLD INTERPRETIVE

Correct without erasing lineage

When a row or total changes, preserve the old revision, identify affected summaries and charts, explain the counting change, and revalidate dependent routes.

LEVEL 3

COMPLETE DOSSIER

Limitations, game links, and review context

DISPUTED / MULTIPLE ACCOUNTS

Known limitations and gaps

The supplied reports and dataset are preserved research inputs, not independently authenticated institutional publications or complete historical/public-health authority.
Repeated or byte-identical files are one evidence origin, not independent corroboration.
Numerical precision, equations, coordinates, institutional names, and extensive citations can create false authority and remain subject to claim-specific review.
The public transformation is educational and non-operational; it does not authorize weapons, surveillance, forecasting, diagnosis, border, workplace, clinical, publication, production, or tuning action.
Health, exposure, casualty, remedy, attribution, and legal claims require domain and affected-community review before stronger conclusions.

REAL-WORLD INTERPRETIVE

Evidence, systems, and review connections

REAL-WORLD INTERPRETIVE

Glossary cross-reference

Terms are defined for this site’s evidence method, not as universal legal or clinical definitions.

event-level record device-level count grouped detonation source-count discrepancy

REAL-WORLD INTERPRETIVE

Decision matrix

Source-bounded treatment matrix
Record state	Acceptable treatment	Prohibited implication
Source observation	Describe the dated record and source scope.	Treat preservation or repetition as independent authentication.
Analytical interpretation	Label assumptions, uncertainty, and alternative explanations.	Present interpretation as settled causal fact.
Review output	Produce a stable local-only finding and next action.	Grant legal, specialist, publication, operational, production, or tuning authority.
Correction and reopening	Map dependent routes, expiration, correction, and retest triggers.	Silently revise a source state or imply that review is closed.

REAL-WORLD INTERPRETIVE

Publication audit checklist

State label

Is the historical, model, projection, or proposal state visible?

Pass condition: The exact boundary label appears before the relevant material.

Origin

Are duplicate files and shared source chains counted correctly?

Pass condition: Evidence origins are distinct from article or file count.

Human impact

Are affected people, rights, access, and remedy represented?

Pass condition: Technical records do not erase communities or shift blame onto them.

Authority

Does the result avoid implied operational or approval authority?

Pass condition: No source or tool grants specialist, publication, operational, production, activation, or tuning authority.

LEVEL 4

RESEARCH EDITION

Sources, methods, and stable links

REAL-WORLD INTERPRETIVE

Linked reports

REAL-WORLD VERIFIED

Method and corrections

This page follows the public method for provenance, confidence, source independence, alternative accounts, limitations, review state, and visible correction.

Read the method View corrections

CONTINUE

Related learning

Nuclear Testing History and EvidenceDisputed Detonations, Monitoring, and Attribution Under UncertaintyHow to distinguish detected signals, official assessments, disputed incidents, state attribution, design claims, and adjudicated findings.Nuclear Testing History and EvidenceFallout, Downwinders, Displacement, and RemedyA human-centered framework for connecting test chronology with exposure evidence, secrecy, displacement, health care, acknowledgement, compensation, restoration, and appeal.Nuclear Testing History and EvidenceNuclear Testing: Records, Human Consequences, and Evidence LimitsA source-bounded guide to the global nuclear testing record, counting conventions, environmental pathways, affected communities, disputed events, monitoring, and remedy.Nuclear Testing History and EvidenceTest Environments, Yield Ranges, and Measurement UncertaintyRead atmospheric, underground, underwater, surface, and high-altitude labels and source yield ranges without converting estimates into exact facts or spectacle. Learning pathNuclear Testing: History, Evidence, and Human ConsequencesMove from counting convention and public-safe event ledger to environment, yield uncertainty, human consequences, remedy, disputed attribution, and correction.