1  # Active Context: keepSync
  2  
  3  ## Current Development Focus
  4  
  5  We are currently in the early development phase, focusing on establishing the core infrastructure and implementing key components:
  6  
  7  1. **Security Module**: Setting up TPM integration and key management framework
  8     - Implementing secure key storage interfaces
  9     - Creating adapters for TPM and file-based key storage
 10     - Ensuring proper memory handling for sensitive data
 11  
 12  2. **File Monitoring**: Building robust file change detection
 13     - Developing debouncing mechanisms to prevent excessive backups
 14     - Implementing platform-specific optimizations
 15     - Creating clean interfaces for change notification
 16  
 17  3. **Backup System**: Implementing encrypted backup functionality
 18     - Creating a simple backup service with encryption for multiple file types
 19     - Implementing backup rotation and retention policies
 20     - Adding metadata to make backups identifiable
 21  
 22  4. **Cloud Integration**: Implementing cloud sync functionality
 23     - Integrating file monitoring with cloud backup services
 24     - Creating robust error handling for network operations
 25     - Implementing retry logic for upload failures
 26  
 27  ## Recent Changes
 28  
 29  1. **Core Security Components**:
 30     - Implemented key provider interfaces
 31     - Added TPM key provider implementation as exclusive security provider
 32     - Created factory methods for TPM provider instantiation
 33  
 34  2. **Cloud Integration**:
 35     - Implemented ProtonMail Drive cloud provider with API integration
 36     - Created fully functional dummy provider for local testing
 37     - **COMPLETED:** Fully implemented S3-compatible storage provider
 38     - Established cloud provider interface with error handling
 39     - Completed CloudSyncService to coordinate between file monitoring and cloud uploads
 40  
 41  3. **Backup Infrastructure**:
 42     - Defined BackupService interface for cleaner component integration
 43     - Upgraded SimpleBackupService to standardized interface
 44     - Improved error handling in backup-related components
 45     - Added proper return values for backup operations
 46     - Implemented enhanced backup retention policies for both local and cloud storage
 47     - Added configurable age-based and count-based retention options
 48     - Separated local and cloud retention policies for better flexibility
 49     - Implemented backup restoration service with verification capabilities
 50     - Added support for backup metadata to facilitate restoration
 51  
 52  4. **Logging System**:
 53     - Implemented comprehensive structured logging system
 54     - Added support for verbosity levels (debug, info, warning, error, fatal)
 55     - Created component-based filtering for focused debugging
 56     - Added file and console logging options
 57     - Implemented caller information display (file and line numbers)
 58  
 59  5. **Configuration Management**:
 60     - Implemented centralized configuration system with validation
 61     - Created JSON serialization/deserialization for config
 62     - Added default values and runtime configuration
 63  
 64  6. **Error Handling & Testing**:
 65     - Created comprehensive error handling system with typed errors
 66     - Implemented error wrapping and context preservation
 67     - Added extensive test framework for critical components
 68  
 69  ## Next Steps
 70  
 71  1. **Short-term priorities**:
 72     - Implement Android KeyStore integration
 73     - Create Android-specific file monitoring
 74     - Design and implement Android GUI
 75     - Document Android integration approach
 76  
 77  2. **Medium-term goals**:
 78     - Implement systemd service integration
 79     - Add command-line interface improvements
 80     - Create more comprehensive documentation
 81     - Add telemetry and logging framework
 82  
 83  3. **Long-term roadmap**:
 84     - Implement Android platform support
 85     - Develop multi-device synchronization
 86     - Create user-friendly setup wizards
 87     - Add conflict resolution for multi-device scenarios
 88  
 89  ## Active Decisions and Considerations
 90  
 91  1. **Security Model**:
 92     - Using AES-256-GCM for authenticated encryption
 93     - Exploring options for key derivation and protection
 94     - Designing zero-trust architecture where possible
 95  
 96  2. **Platform Support**:
 97     - Focusing first on Linux with TPM 2.0
 98     - Planning Android support as second platform
 99     - Considering platform-specific optimizations
100  
101  3. **Cloud Integration**:
102     - Support for both ProtonMail and S3-compatible storage providers
103     - Designing interfaces for further provider extensibility
104     - Addressing sync conflicts and edge cases
105  
106  4. **Local vs. Cloud Backups**:
107     - Maintaining local backups for reliability and performance
108     - Using a staged approach (local backup → cloud upload)
109     - Considering future config options to limit local retention
110  
111  5. **User Experience**:
112     - Balancing security with usability
113     - Minimizing manual configuration requirements
114     - Planning for graceful degradation when components unavailable
115  
116  ## Current Challenges
117  
118  1. **TPM Availability**:
119     - Handling error cases where TPM is unavailable or inaccessible
120     - Supporting different TPM device paths across distributions
121     - Providing clear error messaging when hardware security requirements not met
122  
123  2. **Change Detection**:
124     - Ensuring changes are detected reliably
125     - Managing false positives without missing actual changes
126     - Optimizing debounce timing for different usage patterns
127  
128  3. **Backup Management**:
129     - Determining optimal retention policies
130     - Balancing storage usage with adequate backup history
131     - Handling large files efficiently
132  
133  4. **Testing Methodology**:
134     - Creating test fixtures for security components
135     - Developing mocks for hardware dependencies
136     - Ensuring test coverage of critical paths