Archive Overview
The archive does not answer “what pages are here?” It answers “which materials have left the main path, why they left, and where the current facts live now.”
Why there is an archive layer
As the project adopted OpenSpec and the new documentation information architecture, some older documents, historical notes, and migration notices no longer belonged on the main reading path but still kept background value. The archive therefore has two jobs:
- preserve historical context so readers can understand how the project evolved;
- clearly state which materials are no longer current sources of truth.
Where the current facts live
- Current specification baseline:
openspec/baseline/ - Active proposals:
openspec/changes/ - Landed history:
openspec/archive/ - Project history surfaces: Root
CHANGELOG.mdand GitHub Releases
How to read archive material
If all you need is “what should I do now?”, you usually do not need to stay in the archive. Go directly to Algorithms, Reference, or the Developer Guide instead. Return to archive material only when you need to explain a historical decision, a migration path, or whether information from an old link is outdated.