Issue Type
Documentation Organization
Severity
Low - Reference organization
Problem Statement
Historical investigation documents exist in both docs/ root and docs/archive/ directories, making it difficult to distinguish current architecture from historical analysis.
Current State
In docs/archive/ (good - properly archived):
- BUFFER_STARVATION_ANALYSIS.md
- CLEANUP_COMPLETE_2026-02-17.md
- CLI_RESTRUCTURING_PLAN.md
- CLI_THINNING_PLAN.md
- COMPREHENSIVE_FIX_PLAN.md
- DEBUGGING_HISTORY.md
- DROPOUT_FIX_PLAN_2026-02-14.md
- DRY_REFACTORING_COMPLETE.md
- ENGINE_SEGFAULT_AND_SINE_LAG_FIXES.md
- INTERACTIVE_CONTROLS_FIX_SUMMARY.md
- LIBRARY_LOADING_FIX.md
- PERFORMANCE_FINDINGS.md
- UPDATE_SUMMARY_2026-02-17.md
- V8_DROPOUT_FIX_PLAN.md
In docs/investigation/ (also contains historical docs):
- Various investigation documents that should be archived
Impact:
- Developers may confuse historical analysis with current architecture
- Docs root is cluttered with historical documents
- Difficult to find current authoritative architecture docs
Recommended Actions
- Move all docs/investigation/ documents to
docs/archive/investigation/
- Keep only current architecture docs in docs/ root:
- ARCHITECTURE_TODO.md
- AUDIO_MODULE_ARCHITECTURE.md
- BRIDGE_INTEGRATION_ARCHITECTURE.md
- TEST_ARCHITECTURE.md
- TELEMETRY_ARCHITECTURE.md
- QUICK_START.md
- PLATFORM_AUDIO_RESEARCH.md
- DETERMINISTIC_AUDIO_TESTS.md
- DIAGNOSTICS_GUIDE.md
- STARTER_SOUND_DESIGN.md
- TESTING_GUIDE.md
- VERIFICATION_README.md
- Add README.md to docs/archive/ with brief description of each archived document
- Update docs/README.md to list current architecture docs only
Acceptance Criteria
Related Issues
Notes
This is a low-priority organization issue. The historical documents contain valuable information for understanding past issues, but should be clearly separated from current architecture.
Issue Type
Documentation Organization
Severity
Low - Reference organization
Problem Statement
Historical investigation documents exist in both
docs/root anddocs/archive/directories, making it difficult to distinguish current architecture from historical analysis.Current State
In docs/archive/ (good - properly archived):
In docs/investigation/ (also contains historical docs):
Impact:
Recommended Actions
docs/archive/investigation/Acceptance Criteria
Related Issues
Notes
This is a low-priority organization issue. The historical documents contain valuable information for understanding past issues, but should be clearly separated from current architecture.