a8106e24ee
- Deleted outdated files related to repository audit and deployment status, including AUDIT_COMPLETE.md, AUDIT_FIXES_APPLIED.md, FINAL_DEPLOYMENT_STATUS.md, and others. - Cleaned up documentation to streamline the repository and improve clarity for future maintenance. - Updated README and other relevant documentation to reflect the removal of these files.
32 lines
1.0 KiB
Markdown
32 lines
1.0 KiB
Markdown
# Status Documentation
|
|
|
|
This directory contains current status reports organized by category.
|
|
|
|
## Categories
|
|
|
|
### [Builds](./builds/)
|
|
Build and test results, CI/CD status, and build-related reports.
|
|
|
|
### [Deployments](./deployments/)
|
|
Deployment status, execution reports, and deployment-related status information.
|
|
|
|
### [VMs](./vms/)
|
|
Virtual machine status reports, configuration reviews, template analysis, and VM-related status.
|
|
|
|
### [Tasks](./tasks/)
|
|
Task tracking, remaining work, and task-related status reports.
|
|
|
|
## Status File Lifecycle
|
|
|
|
1. **Active**: Files remain in appropriate category directory while actively being updated
|
|
2. **Archive**: Files older than 90 days are moved to [docs/archive/status/](../archive/status/)
|
|
3. **Reference**: Archived files are kept for historical reference
|
|
|
|
## Adding Status Reports
|
|
|
|
When creating new status reports:
|
|
- Place in the appropriate category subdirectory
|
|
- Include "Last Updated" date in the file
|
|
- Update this README if adding a new category
|
|
- Archive old reports after 90 days
|