33 lines
1.3 KiB
Markdown
33 lines
1.3 KiB
Markdown
# Archive Directory
|
|
|
|
This directory contains archived files that are no longer actively used but are kept for reference.
|
|
|
|
## Structure
|
|
|
|
- `status-reports/phase1/` - Archived status reports from Phase 1 deployment
|
|
- `status-reports/phase1-old/` - Additional historical status reports
|
|
- `status-reports/operations-legacy/` - Former contents of `docs/operations/status-reports/`
|
|
- `status-reports/docs-root-legacy/` - Historical report-style files formerly in `docs/`
|
|
- `status-reports/repo-root-legacy/` - Historical report-style files formerly in the repository root
|
|
- `bridge-trustless-milestones/` - Archived trustless bridge completion and status-report stack
|
|
- `old-configs/ibft2/` - Old IBFT2-based configuration files (migrated to QBFT)
|
|
|
|
## Scripts Archive
|
|
|
|
- `scripts/archive/duplicate-ccip/` - Duplicate CCIP scripts that were consolidated
|
|
|
|
## Purpose
|
|
|
|
Files are archived rather than deleted to:
|
|
- Maintain historical context
|
|
- Enable rollback if needed
|
|
- Provide reference for similar future work
|
|
- Keep the active docs surface focused on current runbooks, deployment state,
|
|
and reference material
|
|
|
|
## Cleanup Policy
|
|
|
|
- Files older than 6 months may be considered for permanent deletion
|
|
- Critical configuration backups are retained indefinitely
|
|
- Status reports can be removed after 1 year if not referenced
|