Educational companion dossier · Fact, interpretation, lived experience, clinical education, fiction, and mechanics are labeled separately. Scope & safety
REAL-WORLD INTERPRETIVE

NUCLEAR TESTING HISTORY AND EVIDENCE

Source-Count Reconciliation and Versioned Ledgers

How to preserve the 714, 715, and 727 Soviet totals, the claimed-but-absent Vela row, and other counting differences without choosing a result by assertion.

LEVEL 1

ORIENTATION

Why this matters

REAL-WORLD INTERPRETIVE

One-sentence brief

Conflicting totals can be informative when their units, source editions, inclusion rules, transformations, and unresolved records remain visible.

REAL-WORLD INTERPRETIVE

Three key points

  1. A source instance is not automatically an independent evidence origin; the six nuclear files resolve to three unique source hashes.
  2. The exact CSV, companion methodology report, and history report use different units and totals that require scope reconciliation.
  3. A correction must preserve the earlier version, reason, evidence, reviewer scope, dependent routes, and reopening conditions.
LEVEL 2

WORKING BRIEF

Evidence, context, and limits

REAL-WORLD INTERPRETIVE

Name the counting universe

“Test,” “event row,” “device,” “detonation,” “peaceful explosion,” “safety experiment,” and “wartime detonation” are not interchangeable. A reconciled table starts by naming each universe.

REAL-WORLD INTERPRETIVE

Bind every number to a version

Record exact source bytes, SHA-256, date, row transform, duplicate lineage, and supersession. A number without its source revision cannot be reproduced or corrected.

REAL-WORLD INTERPRETIVE

Keep conflicts open until evidence closes them

The one-row Soviet difference and claimed Vela inclusion remain open. Silence, visual neatness, or a preferred narrative is not a resolution method.

REAL-WORLD INTERPRETIVE

Propagate corrections visibly

Update claim records, public dockets, explorer notes, learning pages, glossary, paths, UAI, manifests, sitemap, and audits together.

LEVEL 3

COMPLETE DOSSIER

Limitations, game links, and review context

DISPUTED / MULTIPLE ACCOUNTS

Known limitations and gaps

  • The source corpus remains user-supplied research and data, not independently authenticated institutional authority.
  • A reproduced count verifies the transform against exact bytes, not the historical accuracy or completeness of the source.
  • Current institutional, legal, scientific, public-health, and policy statements may change and require date-stamped review.
  • Model output, projection, and proposal language can create false certainty if assumptions and implementation state are hidden.
  • No page or workbench authorizes diagnosis, monitoring, targeting, publication, production, activation, tuning, or operational action.
REAL-WORLD INTERPRETIVE

Decision matrix

Claim-state publication matrix
Claim state Acceptable wording Prohibited implication
Exact dataset count “The exact supplied dataset contains…” with unit and revision. Historical completeness, independent verification, or identical scope with another total.
Source-authored observation or estimate “The source reports/estimates…” with population, period, and uncertainty. Universal fact, individual attribution, or causation beyond the study design.
Modeled relationship MODELED RELATIONSHIP — NOT A FORECAST Explain inputs, assumptions, outputs, validation, and transfer. Live forecast, guaranteed arrival, or automatic action.
Projection or proposal SOURCE-AUTHORED PROJECTION — NOT A SITE FORECAST / POLICY PROPOSAL — NOT IMPLEMENTED HERE Site forecast, deployment claim, authority, or inevitability.
REAL-WORLD INTERPRETIVE

Publication audit checklist

Unit and scope

Are counting unit, population, period, geography, and comparison explicit?

Pass condition: The claim can be reproduced without silently changing its universe.

Origin and independence

Are source instances separated from unique evidence origins?

Pass condition: Duplicate and derivative files are not counted as corroboration.

State and currentness

Is observation, estimate, model, projection, or proposal status visible with a review date?

Pass condition: Mutable claims have currentness and expiration triggers.

Authority and correction

Are correction dependencies and authority limits explicit?

Pass condition: No result implies approval or action and every material change has a propagation path.

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.

NEXT

CONTINUE

Related learning