Skip to content

Latest commit

 

History

History

Folders and files

NameName
Last commit message
Last commit date

parent directory

..
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

README.md

Archive - Historical Documentation

Version: 1.0.0
Last Updated: December 3, 2025
Status: Published
Audience: Documentation Maintainers, Developers seeking historical context


⚠️ Important Notice

This directory contains DEPRECATED documentation.

Files in this archive should NOT be used for current development. They are preserved for:

  • Historical context and evolution tracking
  • Audit trail of refactoring decisions
  • Understanding past implementations

Warning

Always refer to current documentation in sections 1-7 for active development.


Quick Navigation

📋 Finding Current Documentation

If you're looking for up-to-date information:

🗂️ Archive Contents

For detailed information about archived files:


What's Archived Here?

This archive contains 34 deprecated files organized into:

Category Count Description
Refactoring Summaries 14 Session-specific implementation logs
README Variants 7 Legacy README versions
Legacy Guides 4 Superseded developer guides
Architecture Legacy 3 Outdated architecture docs
Execution Reports 2 Historical refactoring reports
Development Artifacts 2 Temporary files and trackers
Current Files 2 This README + ARCHIVE_INDEX

See ARCHIVE_INDEX.md for the complete catalog with replacement document links.


When Was This Archived?

Archival Date: December 3, 2025
Phase: Phase 2 - Documentation Consolidation
Details: PHASE_2_SUMMARY.md

During Phase 2, legacy files from orphaned directories (docs/architecture/, docs/development/, docs/testing/, docs/requirements/, docs/plans/) were either:

  • Merged into main documentation sections (36 files preserved)
  • 📦 Archived here when superseded by newer versions (34 files)

Archive Usage Guidelines

✅ Appropriate Uses

  • Understanding historical design decisions ("Why did we choose this approach?")
  • Tracking feature evolution over time
  • Audit and compliance purposes
  • Comparative analysis (before/after refactoring)

❌ Inappropriate Uses

  • Reference for current development (use sections 1-7 instead)
  • Copy-pasting code examples (may be outdated or incompatible)
  • Following workflows (use 4_development/ instead)
  • Linking from new documentation (link to current docs)

Retention Policy

Current Status: Indefinite retention

Rationale:

  • Git history preserves all content, but archive provides easier access
  • Disk space is not a constraint
  • Historical context is valuable for understanding project evolution
  • No significant maintenance burden

Future Review: After IoTBay v1.0.0 release, conduct archive review to identify candidates for permanent removal (e.g., test artifacts, temporary trackers).


Related Documentation


Version: 1.0.0
Status: Published
Last Updated: December 3, 2025
Maintained By: IoT Bay Documentation Team


Document Version: 1.0.0