Files
bakery-ia/docs/archive/README.md
2025-11-05 13:34:56 +01:00

95 lines
3.8 KiB
Markdown

# Documentation Archive
This folder contains historical documentation, progress reports, and implementation summaries that have been superseded by the consolidated documentation in the main `docs/` folder structure.
## Purpose
These documents are preserved for:
- **Historical Reference**: Understanding project evolution
- **Audit Trail**: Tracking implementation decisions
- **Detailed Analysis**: In-depth reports behind consolidated guides
## What's Archived
### Deletion System Implementation (Historical)
- `DELETION_SYSTEM_COMPLETE.md` - Initial completion report
- `DELETION_SYSTEM_100_PERCENT_COMPLETE.md` - Final completion status
- `DELETION_IMPLEMENTATION_PROGRESS.md` - Progress tracking
- `DELETION_REFACTORING_SUMMARY.md` - Technical summary
- `COMPLETION_CHECKLIST.md` - Implementation checklist
- `README_DELETION_SYSTEM.md` - Original README
- `QUICK_START_REMAINING_SERVICES.md` - Service templates
**See Instead**: [docs/03-features/tenant-management/deletion-system.md](../03-features/tenant-management/deletion-system.md)
### Security Implementation (Analysis Reports)
- `DATABASE_SECURITY_ANALYSIS_REPORT.md` - Original security analysis
- `SECURITY_IMPLEMENTATION_COMPLETE.md` - Implementation summary
- `RBAC_ANALYSIS_REPORT.md` - Access control analysis
- `TLS_IMPLEMENTATION_COMPLETE.md` - TLS setup details
**See Instead**: [docs/06-security/](../06-security/)
### Implementation Summaries (Session Reports)
- `IMPLEMENTATION_SUMMARY.md` - General implementation
- `IMPLEMENTATION_COMPLETE.md` - Completion status
- `PHASE_1_2_IMPLEMENTATION_COMPLETE.md` - Phase summaries
- `FINAL_IMPLEMENTATION_SUMMARY.md` - Final summary
- `SESSION_COMPLETE_FUNCTIONAL_TESTING.md` - Testing session
- `FIXES_COMPLETE_SUMMARY.md` - Bug fixes summary
- `EVENT_REG_IMPLEMENTATION_COMPLETE.md` - Event registry
- `SUSTAINABILITY_IMPLEMENTATION.md` - Sustainability features
**See Instead**: [docs/10-reference/changelog.md](../10-reference/changelog.md)
### Service Configuration (Historical)
- `SESSION_SUMMARY_SERVICE_TOKENS.md` - Service token session
- `QUICK_START_SERVICE_TOKENS.md` - Quick start guide
**See Instead**: [docs/10-reference/service-tokens.md](../10-reference/service-tokens.md)
## Current Documentation Structure
For up-to-date documentation, see:
```
docs/
├── README.md # Master index
├── 01-getting-started/ # Quick start guides
├── 02-architecture/ # System architecture
├── 03-features/ # Feature documentation
│ ├── ai-insights/
│ ├── tenant-management/ # Includes deletion system
│ ├── orchestration/
│ ├── sustainability/
│ └── calendar/
├── 04-development/ # Development guides
├── 05-deployment/ # Deployment procedures
├── 06-security/ # Security documentation
├── 07-compliance/ # GDPR, audit logging
├── 08-api-reference/ # API documentation
├── 09-operations/ # Operations guides
└── 10-reference/ # Reference materials
└── changelog.md # Project history
```
## When to Use Archived Docs
Use archived documentation when you need:
1. **Detailed technical analysis** that led to current implementation
2. **Historical context** for understanding why decisions were made
3. **Audit trail** for compliance or review purposes
4. **Granular implementation details** not in consolidated guides
For all other purposes, use the current documentation structure.
## Document Retention
These documents are kept indefinitely for historical purposes. They are not updated and represent snapshots of specific implementation phases.
---
**Archive Created**: 2025-11-04
**Content**: Historical implementation reports and analysis documents
**Status**: Read-only reference material