INDEPENDENT TECHNICAL HISTORY / VOL. 01
Read the source.
Question the story.
An evidence-led record of the code, languages, algorithms and systems that built computing. We start with artifacts—not legends—and revise claims when the evidence changes.
VERIFIABLE SYSTEMRECORD → REVIEW → REVISE
Not a hall of heroes.
A chain of evidence.
Computing history is complicated by lost files, competing recollections and the distance between an idea and its implementation. We distinguish what a document proves, what an experiment demonstrates and what remains interpretation.
02 / THE INDEX
Ten disciplines.
One verifiable record.
Browse focused research areas. Each starting dossier explains the questions, methods and source types that will shape future investigations.
10 research dossiers
Source Code Archive
Read source code as dated, attributable evidence rather than treating reconstructed examples as originals.
OPEN DOSSIER →02 / 10↗Language Lineages
Trace languages through specifications, compilers, runtime behavior and documented influences.
OPEN DOSSIER →03 / 10↗Algorithms
Separate an algorithmic idea from a particular program, theoretical result or benchmark claim.
OPEN DOSSIER →04 / 10↗Data Structures
Investigate the representations that let programs retrieve, update and reason about data.
OPEN DOSSIER →05 / 10↗Compilers & Runtimes
Examine compilation stages, intermediate representations, optimization and program execution.
OPEN DOSSIER →06 / 10↗Operating Systems
Report on how kernels and systems mediate hardware, processes, storage and security.
OPEN DOSSIER →07 / 10↗Developer Toolchains
Trace editors, debuggers, build systems, package management and automated testing through their own documentation and source.
OPEN DOSSIER →08 / 10↗Version Control
Explore how software projects store revisions, branches, authorship and collaboration.
OPEN DOSSIER →09 / 10↗Software Archaeology
Use verifiable artifacts to reconstruct how old software was built, used and changed.
OPEN DOSSIER →10 / 10↗Code Lab
Present small, reproducible technical demonstrations with inputs, versions, expected observations and known limitations.
OPEN DOSSIER →03 / RESEARCH FIELD NOTE
SOURCE-LED / READABLE / REVISABLEFrom RCS to Git: what changes when history becomes a graph?
A guided comparison of file-oriented revision records and Git's content-addressed object model—with original technical documentation, clear limits and a public revision record.
Read the field note04 / HOW THE RECORD CHANGES
Publish the evidence.
Keep the correction.
Readers can challenge a claim with a dated source, alternate interpretation or reproducible counterexample. Accepted changes are documented in the revision record; submissions are never silently treated as published facts.
How to improve the recordLocate the claim.
Give the exact passage, artifact, version and context.
Provide the source.
Link a primary document, original code or reproducible result.
Review and revise.
Accepted material changes update the public version record.