codinghistory.world
A LIVING WORLD ARCHIVE / 01.0

Code has more than one history.

The story of computing is not a procession of inventions from a single place. It is made across languages, laboratories, communities, classrooms, workplaces, and borders.

PLACEPEOPLEPROVENANCEREVISION
FIG. 001A distributed recordConceptual global visualization—not a map of historical importance
EDITORIAL POSITION / AN OPEN RECORD

We do not correct a narrow history by inventing a broader one. We expand the record with documents, testimony, uncertainty, and public correction.

Contribute a missing source ↗
ATLAS / EVIDENCE-FIRST GEOGRAPHY

Follow the evidence across places.

Explore four carefully scoped research windows. Markers are illustrative and are not a ranking or a census of global computing activity.

WORLD ATLAS · STARTER EDITION4 RESEARCH WINDOWS / 11 REGISTERED SOURCES
RESEARCH WINDOWS / SCHEMATIC
REGION / SOUTH ASIA · S01

Indian institutional computing

The 1960 TIFRAC naming ceremony is documented in a Computer History Museum account.

Location and source scope must not be mistaken for the full geography of contribution.

Explore regional histories ↗
THE RESEARCH DESK / TEN PATHWAYS

Ten ways to read the world.

Each pathway is a populated research brief with named questions and sources. These are opening dossiers, not completed historical surveys.

FEATURED FIELD NOTE / ISSUE 001

Whose computing history gets recorded?

What museum records, institutional histories, language policy, regional enterprise archives and oral histories reveal—and what they still cannot establish.

A PUBLISHING SYSTEM THAT CAN BE CORRECTED

No silent rewrites.

A living archive requires visible revision, not vague claims of neutrality. Evidence can change the account. Readers should be able to inspect why.

01

Document the claim

Provide dated sources, exact citations, original language, geographic scope, and any conflicting records.

02

Invite challenge

Readers may submit counterevidence, historical corrections, missing contributors, and translation disputes.

03

Publish the revision

Material accepted changes receive a public note stating what changed, when and why. Rejected leads are not presented as facts.