# Status Reports Index **Last Updated**: 2026-04-12 **Status**: Active index, legacy reports archived This directory now acts as a small routing layer between the active status docs we still use and the large historical report sets that were moved into `docs/archive/status-reports/`. ## Active Status Entry Points - [../../STATUS_AND_TOKEN_ROUTING.md](../../STATUS_AND_TOKEN_ROUTING.md) - Current contract, token-routing, and service status. - [../../MASTER_CONTRACTS_AND_INFRASTRUCTURE_LIST.md](../../MASTER_CONTRACTS_AND_INFRASTRUCTURE_LIST.md) - Current active contract and infrastructure inventory. - [../../DEPLOYMENT_STATUS_AND_NEXT_STEPS.md](../../DEPLOYMENT_STATUS_AND_NEXT_STEPS.md) - Current deployment posture and next actions. - [../../deployment/COMPILATION_STATUS.md](../../deployment/COMPILATION_STATUS.md) - Current contract compilation notes and exceptions. - [../../architecture/FOUNDRY_MONOREPO_SCOPES.md](../../architecture/FOUNDRY_MONOREPO_SCOPES.md) - Current Forge scoping and compile-surface policy. - [../tasks/TODO.md](../tasks/TODO.md) - Active task backlog. ## Archived Report Collections - [../../archive/status-reports/README.md](../../archive/status-reports/README.md) - Archive overview. - [../../archive/status-reports/operations-legacy/README.md](../../archive/status-reports/operations-legacy/README.md) - Historical files formerly in `docs/operations/status-reports/`. - [../../archive/status-reports/docs-root-legacy/README.md](../../archive/status-reports/docs-root-legacy/README.md) - Historical report-style files formerly in `docs/`. - [../../archive/status-reports/repo-root-legacy/README.md](../../archive/status-reports/repo-root-legacy/README.md) - Historical report-style files formerly in the repository root. - [../../archive/status-reports/phase1/](../../archive/status-reports/phase1/) - Older phase-1 archives retained from previous cleanup passes. - [../../archive/status-reports/phase1-old/](../../archive/status-reports/phase1-old/) - Additional early legacy reports. ## Usage Notes - Treat files under `docs/archive/status-reports/` as historical context, not live runbooks. - Some archived docs intentionally preserve old paths, assumptions, or stale links. - New operational state should land in runbooks, deployment docs, or explicit reference pages instead of creating another large status-report pile. ## Related Documentation - [Master Documentation Index](../../MASTER_DOCUMENTATION_INDEX.md) - [Archive README](../../archive/README.md) - [Archive Policy](../../archive/ARCHIVE_POLICY.md)