THE SCOPE
File provenance, build environments, historical interpretation, digital preservation and uncertainty.
This starting dossier establishes a research remit and reference points for the section. It does not claim to be a comprehensive historical survey. Future articles will identify primary evidence, publication or artifact dates, competing accounts and the limits of verification.
A surviving file is not the whole system
Documentation, dependency versions, operating-system assumptions and peripheral devices can be essential to interpreting old source.
Reconstruction needs a disclosure
Emulation, patching and modernization are useful research techniques when every intervention is identified and preserved.
Absence of evidence is not evidence of absence
Incomplete archives cannot prove that a contribution never existed; the public record should state its gaps.
OPEN QUESTIONS / NOT ASSUMPTIONS
Questions that guide the reporting.
- 01Which files are authentic and which are reconstructed?
- 02How was the recovered material obtained and validated?
- 03What missing evidence could change the interpretation?
PRIMARY & TECHNICAL REFERENCES
Starting sources
The references below are paths into the evidence, not a claim that every historical question is settled. Each future article will provide its own direct citations and version-specific evidence.
- 01Software Heritage — documentation docs.softwareheritage.org
- 02Computer History Museum — software collections computerhistory.org
VERSION RECORD / 1.0
This dossier is revisable.
2026-10-08 — Initial edition. Research scope, evidence lenses, questions and reference starting points published. No external submissions have been reviewed for this initial edition. Future substantive changes should be documented with supporting evidence.
Submit source evidence or a correction →