Status: Active
Last Updated: 2025-11-13
Maintenance Mode: Enabled
This document tracks legacy systems, components, and patterns that are being maintained for backward compatibility or gradual deprecation. Legacy code is preserved under the legacy feature flag to isolate it from modern codebase patterns.
Cargo Feature: legacy
Default: Disabled
Usage: cargo build --features legacy
- Status: Migration pending
- Location:
agents/src/implementations/_backup/ - Count: 902 agents pending restoration
- Scope: Original agent implementations that need refactoring
- Status: Under review
- Items: [To be cataloged]
- Migration Path: [To be defined]
- Status: Documentation in progress
- Items: [To be listed]
- Replacement Patterns: [To be linked]
- Inventory all legacy components
- Assess restoration effort for each
- Establish priority ranking
- Document replacement patterns
- Select high-priority agents for restoration
- Implement modern trait-based patterns
- Add comprehensive tests
- Update documentation
- Move to
legacyfeature flag - Issue deprecation notices
- Guide migration path
- Set sunset date
Components that currently depend on legacy systems:
- [To be filled as dependencies are discovered]
- Unit Tests: [Status]
- Integration Tests: [Status]
- Feature Tests: [Status]
Metrics for legacy components before optimization:
- [To be established]
- All legacy restoration follows the agent trait pattern defined in
agents/src/trait.rs - No new code should be added to legacy implementations
- Restoration follows the workflow patterns in
WORKSPACE_MEMORY.md - Archive references maintained in
crc/archive/forks/
WORKSPACE_MEMORY.md- Restoration workflowagents/README.md- Agent architecturecrc/FORK_PROCESSING_SYSTEM.md- Archive systemCONTRIBUTING.md- Code standards