Claude
aec7ddb56e
Their pointers were committed in a5ed8c3d (2026-08-01) and the objects were
never uploaded: the server answers 404 for all of them, and no copy exists
(Captain Bob, 2026-11-11: "they can be trimmed out").
Removed: 3,827 phase-1 logs (docs/working/archive/legacy/phase-1), 3 in
docs/working/archive/historical, 106 DoE CSVs in experiments/bare_metal/runs,
QEMU_BASELINE.log, docs/SYSTEM_NARRATIVE.log, docs/ontology.log.
Kept: the 5 LaTeX build logs under docs/patent (legal hold) -- excluded from
fetch instead. .lfsconfig excludes every one of these paths, so older commits
check out and LFS fetches run without 404s.
Every LFS pointer left in the tree (1,195) has its object on the server.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_017RzZgrf7V7Zk2iczBXDRbm
Archived Documentation
This directory contains historical documentation that is no longer current but preserved for reference and context.
⚠️ Important Notice
Information in this directory may be outdated, superseded, or incorrect.
Always consult current documentation in the numbered directories (../01-getting-started/, ../03-architecture/, etc.) before referencing archived materials.
Contents
phase-1/
Development artifacts from Phase 1 (initial VM + physics implementation):
Reference/- Implementation summaries, testing results, phase completion statusReference/physics_experiment/- Experimental iteration, DoE analysisReference/physics_experiment/PEER_REVIEW_SUBMISSION/- Initial peer review materials
Note: Much of Phase 1 content has been superseded by:
- Current architecture docs:
../03-architecture/ - Current experiment protocols:
../02-experiments/ - Current quality processes:
../04-quality/
Top-Level Archived Files
- START_HERE_HEARTBEAT_DOE.md - Superseded by
../02-experiments/heartbeat-doe/ - OPTIMIZATION_OPPORTUNITIES.md - Superseded by
../03-architecture/physics-engine/
Why Archive Instead of Delete?
Archived documentation provides:
- Historical context for design decisions
- Evolution of ideas over time
- Lessons learned from failed approaches
- Reference for "why we don't do X anymore"
When to Consult Archive
✅ Good reasons to check archive:
- Understanding historical design rationale
- Researching "why did we try approach X?"
- Comparing old vs. new implementation
- Finding context for git blame results
❌ Bad reasons to check archive:
- Learning how to use StarForth (use
../01-getting-started/) - Understanding current architecture (use
../03-architecture/) - Running experiments (use
../02-experiments/) - Contributing code (use
../CONTRIBUTING.md)
For Researchers
The archive provides valuable insight into:
- Development process evolution
- Experimental methodology development
- Design trade-offs and decisions
- Failed approaches and why they failed