claude-mpm 3.7.8__tar.gz → 3.8.1__tar.gz

claude_mpm-3.8.1/CLAUDE.md

@@ -0,0 +1,257 @@
+# Claude MPM Development Guidelines
+
+This document provides development guidelines for the claude-mpm project codebase.
+
+## Project Overview
+
+Claude MPM (Multi-Agent Project Manager) is a framework that extends Claude Desktop with multi-agent orchestration capabilities, featuring a modern service-oriented architecture with interface-based contracts and dependency injection.
+
+## Architecture (v3.7.8+)
+
+Following the TSK-0053 refactoring, Claude MPM features:
+
+- **Service-Oriented Architecture**: Five specialized service domains
+- **Interface-Based Contracts**: All services implement explicit interfaces  
+- **Dependency Injection**: Service container with automatic resolution
+- **Performance Optimizations**: Lazy loading, multi-level caching, connection pooling
+- **Security Framework**: Input validation, path traversal prevention, secure operations
+- **Backward Compatibility**: Lazy imports maintain existing import paths
+
+## Key Documentation
+
+### Architecture and Development
+- 🏗️ **Architecture Overview**: See [docs/ARCHITECTURE.md](docs/ARCHITECTURE.md) for service-oriented architecture
+- 📁 **Project Structure**: See [docs/STRUCTURE.md](docs/STRUCTURE.md) for file organization
+- 🔧 **Service Layer Guide**: See [docs/developer/SERVICES.md](docs/developer/SERVICES.md) for service development
+- ⚡ **Performance Guide**: See [docs/PERFORMANCE.md](docs/PERFORMANCE.md) for optimization patterns
+- 🔒 **Security Guide**: See [docs/SECURITY.md](docs/SECURITY.md) for security framework
+- 🧪 **Testing Guide**: See [docs/TESTING.md](docs/TESTING.md) for testing strategies
+- 📚 **Migration Guide**: See [docs/MIGRATION.md](docs/MIGRATION.md) for upgrade instructions
+
+### Operations and Quality
+- 🧪 **Quality Assurance**: See [docs/QA.md](docs/QA.md) for testing guidelines
+- 🚀 **Deployment**: See [docs/DEPLOY.md](docs/DEPLOY.md) for versioning and deployment
+- 📊 **Logging**: See [docs/RESPONSE_LOGGING_CONFIG.md](docs/RESPONSE_LOGGING_CONFIG.md) for response logging configuration
+- 🔢 **Versioning**: See [docs/VERSIONING.md](docs/VERSIONING.md) for version management
+- 🧠 **Memory System**: See [docs/MEMORY.md](docs/MEMORY.md) for agent memory management
+
+## Development Guidelines
+
+### Critical Principles
+
+**🔴 NEVER ASSUME - ALWAYS VERIFY**
+- **NEVER assume** file locations, configurations, or implementations
+- **ALWAYS verify** by reading actual files and checking current state
+- **ALWAYS check** existing code patterns before implementing
+- **NEVER guess** at directory structures or file contents
+- **ALWAYS confirm** dependencies and imports exist before using them
+
+### Project Structure Requirements
+
+1. **File Organization**: Always refer to `docs/STRUCTURE.md` when creating new files
+   - **Scripts**: ALL scripts go in `/scripts/`, NEVER in project root
+   - **Tests**: ALL tests go in `/tests/`, NEVER in project root
+   - **Python modules**: Always under `/src/claude_mpm/`
+   
+2. **Import Conventions**: 
+   - Use full package names: `from claude_mpm.module import ...`
+   - Never use relative imports in main code
+   - Check existing patterns before adding new imports
+
+### Testing Requirements
+
+**After significant changes, always run:**
+```bash
+# Quick E2E tests
+./scripts/run_e2e_tests.sh
+
+# Full test suite
+./scripts/run_all_tests.sh
+
+# Lint and type checks
+./scripts/run_lint.sh
+```
+
+See [docs/QA.md](docs/QA.md) for detailed testing procedures.
+
+### Key System Components
+
+When modifying the codebase, understand these core systems:
+
+1. **Framework Loader** (`src/claude_mpm/core/framework_loader.py`)
+   - Loads PM instructions from `src/claude_mpm/agents/INSTRUCTIONS.md`
+   - Manages agent discovery and capabilities
+   - DO NOT duplicate CLAUDE.md content here
+
+2. **Hook System** (`src/claude_mpm/hooks/`)
+   - Extensibility through pre/post hooks
+   - Response logging via `SubagentStop` and `Stop` events
+   - Structured JSON responses for proper logging
+
+3. **Services Layer** (`src/claude_mpm/services/`)
+   - **Core Services**: Foundation interfaces and base classes
+   - **Agent Services**: Agent lifecycle, deployment, and management
+   - **Communication Services**: Real-time WebSocket and SocketIO
+   - **Project Services**: Project analysis and workspace management
+   - **Infrastructure Services**: Logging, monitoring, and error handling
+   - **Legacy Structure**: Maintained for backward compatibility
+
+4. **CLI System** (`src/claude_mpm/cli/`)
+   - Modular command structure
+   - See [CLI Architecture](src/claude_mpm/cli/README.md) for adding new commands
+
+### Common Development Tasks
+
+#### Adding a New Service
+1. **Create Interface**: Define service contract in `src/claude_mpm/services/core/interfaces.py`
+2. **Implement Service**: Create implementation in appropriate service domain
+3. **Register Service**: Add to service container if using dependency injection
+4. **Add Tests**: Create unit, integration, and interface compliance tests
+5. **Update Documentation**: Document service in [docs/developer/SERVICES.md](docs/developer/SERVICES.md)
+
+#### Service Development Patterns
+```python
+# 1. Define interface
+class IMyService(ABC):
+    @abstractmethod
+    def my_operation(self, param: str) -> bool:
+        pass
+
+# 2. Implement service
+class MyService(BaseService, IMyService):
+    def __init__(self, dependency: IDependency):
+        super().__init__("MyService")
+        self.dependency = dependency
+    
+    async def initialize(self) -> bool:
+        # Initialize service
+        return True
+    
+    def my_operation(self, param: str) -> bool:
+        # Implementation
+        return True
+
+# 3. Register in container
+container.register(IMyService, MyService, singleton=True)
+
+# 4. Test interface compliance
+def test_service_implements_interface():
+    service = MyService(mock_dependency)
+    assert isinstance(service, IMyService)
+```
+
+#### Modifying PM Instructions
+1. Edit `src/claude_mpm/agents/INSTRUCTIONS.md` for PM behavior
+2. Edit `src/claude_mpm/agents/BASE_PM.md` for framework requirements
+3. Test with `./claude-mpm run` in interactive mode
+4. Update tests for PM behavior changes
+
+#### Adding CLI Commands
+1. Create command module in `src/claude_mpm/cli/commands/`
+2. Register in `src/claude_mpm/cli/parser.py`
+3. Follow existing command patterns
+4. Use dependency injection for service access
+5. Add comprehensive tests and documentation
+
+#### Performance Optimization
+1. **Identify Bottlenecks**: Use profiling tools and performance tests
+2. **Implement Caching**: Add appropriate caching layers
+3. **Lazy Loading**: Defer expensive operations until needed
+4. **Connection Pooling**: Reuse expensive connections
+5. **Monitor Metrics**: Track performance over time
+
+## Common Issues and Solutions
+
+### Architecture-Related Issues
+1. **Service Resolution Errors**: Ensure services are registered in container before resolving
+2. **Interface Compliance**: Verify services implement all required interface methods
+3. **Circular Dependencies**: Use dependency injection and avoid circular imports
+4. **Cache Performance**: Monitor cache hit rates and adjust TTL settings
+
+### Legacy Compatibility Issues
+1. **Import Errors**: Use new service paths or rely on lazy import compatibility
+2. **Service Instantiation**: Use service container instead of direct instantiation
+3. **Configuration Schema**: Update config files to new structure
+
+### Performance Issues
+1. **Slow Startup**: Check lazy loading implementation and cache warming
+2. **Memory Usage**: Monitor service memory consumption and optimization
+3. **Cache Misses**: Verify cache configuration and invalidation strategies
+
+### Traditional Issues
+1. **Import Errors**: Ensure virtual environment is activated and PYTHONPATH includes `src/`
+2. **Hook Service Errors**: Check port availability (8080-8099)
+3. **Version Errors**: Run `pip install -e .` to ensure proper installation
+4. **Agent Loading**: Check `.claude/agents/` for deployed agents
+
+## Contributing
+
+### Code Quality Standards
+1. **Follow Architecture**: Use service-oriented patterns and interface-based design
+2. **Structure Compliance**: Follow the structure in `docs/STRUCTURE.md`
+3. **Interface Design**: Define clear contracts for all services
+4. **Dependency Injection**: Use service container for loose coupling
+5. **Performance**: Implement caching and lazy loading where appropriate
+6. **Security**: Follow security guidelines in `docs/SECURITY.md`
+
+### Testing Requirements
+1. **Unit Tests**: Test individual services and components (85%+ coverage)
+2. **Integration Tests**: Test service interactions and interfaces
+3. **Performance Tests**: Verify caching and optimization features
+4. **Security Tests**: Validate input validation and security measures
+5. **E2E Tests**: Test complete user workflows
+
+### Documentation Standards
+1. **Service Documentation**: Document all interfaces and implementations
+2. **Architecture Updates**: Keep architecture docs current
+3. **Migration Guides**: Document breaking changes and upgrade paths
+4. **Performance Metrics**: Document performance expectations and benchmarks
+
+### Version Management
+Use [Conventional Commits](https://www.conventionalcommits.org/) for automatic versioning:
+- `feat:` for new features (minor version bump)
+- `fix:` for bug fixes (patch version bump)
+- `feat!:` or `BREAKING CHANGE:` for breaking changes (major version bump)
+- `perf:` for performance improvements
+- `refactor:` for code refactoring
+- `docs:` for documentation updates
+
+## Deployment Process
+
+See [docs/DEPLOY.md](docs/DEPLOY.md) for the complete deployment process:
+- Version management with `./scripts/manage_version.py`
+- Building and publishing to PyPI
+- Creating GitHub releases
+- Post-deployment verification
+
+## TSK-0053 Refactoring Achievements
+
+The service layer architecture refactoring delivered:
+
+### Technical Achievements
+- **Service-Oriented Architecture**: Complete redesign with five specialized service domains
+- **Interface-Based Contracts**: All major services implement explicit interfaces
+- **Dependency Injection**: Service container with automatic dependency resolution
+- **50-80% Performance Improvement**: Through lazy loading and intelligent caching
+- **Enhanced Security**: Comprehensive input validation and sanitization framework
+- **Backward Compatibility**: Lazy imports maintain existing import paths
+
+### Quality Improvements
+- **Better Testability**: Interface-based architecture enables easy mocking and testing
+- **Improved Maintainability**: Clear separation of concerns and service boundaries
+- **Enhanced Reliability**: Comprehensive testing with 85%+ coverage target
+- **Developer Experience**: Rich documentation and migration guides
+
+### Future-Proofing
+- **Scalability**: Service-oriented design supports future growth
+- **Extensibility**: Plugin architecture through interfaces and hooks
+- **Modularity**: Clear service boundaries enable independent development
+- **Performance**: Intelligent caching and resource optimization foundations
+
+## Important Notes
+
+- This file (CLAUDE.md) contains ONLY development guidelines for this project
+- Framework features and usage are documented in the framework itself
+- Claude Desktop automatically reads this file - keep it focused on development tasks
+- Do not include end-user documentation or framework features here
+- The refactored architecture enables faster development and better code quality

{claude_mpm-3.7.8/src/claude_mpm.egg-info → claude_mpm-3.8.1}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: claude-mpm
-Version: 3.7.8
+Version: 3.8.1
 Summary: Claude Multi-agent Project Manager - Clean orchestration with ticket management
 Home-page: https://github.com/bobmatnyc/claude-mpm
 Author: Claude MPM Team
@@ -189,6 +189,26 @@ Dependencies are automatically aggregated from all agent sources (PROJECT > USER
 
 For comprehensive documentation, see [docs/AGENT_DEPENDENCIES.md](docs/AGENT_DEPENDENCIES.md).
 
+## Architecture
+
+Claude MPM v3.7.8+ features a **modern service-oriented architecture** with:
+
+### Service Layer Organization
+- **Core Services**: Foundation interfaces and dependency injection
+- **Agent Services**: Agent lifecycle, deployment, and management
+- **Communication Services**: Real-time WebSocket and SocketIO
+- **Project Services**: Project analysis and workspace management
+- **Infrastructure Services**: Logging, monitoring, and error handling
+
+### Key Architectural Features
+- **Interface-Based Design**: All services implement well-defined contracts
+- **Dependency Injection**: Loose coupling through service container
+- **Lazy Loading**: Performance optimization with deferred initialization
+- **Multi-Level Caching**: Intelligent caching with TTL and invalidation
+- **Security Framework**: Input validation, path sanitization, and secure operations
+
+For detailed architecture information, see [docs/ARCHITECTURE.md](docs/ARCHITECTURE.md).
+
 ## Key Capabilities
 
 ### Multi-Agent Orchestration
@@ -246,31 +266,48 @@ See [docs/developer/11-dashboard/README.md](docs/developer/11-dashboard/README.m
 
 ## Documentation
 
+### User Documentation
 - **[Quick Start Guide](QUICKSTART.md)** - Get running in 5 minutes
 - **[Agent Memory System](docs/MEMORY.md)** - Comprehensive memory documentation
 - **[Monitoring Dashboard](docs/developer/11-dashboard/README.md)** - Real-time monitoring features
-- **[Project Structure](docs/STRUCTURE.md)** - Codebase organization
-- **[Deployment Guide](docs/DEPLOY.md)** - Publishing and versioning
 - **[User Guide](docs/user/)** - Detailed usage documentation
-- **[Developer Guide](docs/developer/)** - Architecture and API reference
-
-## Recent Updates (v3.4.27)
-
-### Core System Enhancements
-- **Project Structure Reorganization**: Centralized path management with ClaudeMPMPaths enum
-- **Agent Services Hierarchy**: Reorganized agent and memory services into hierarchical structures  
-- **Response Logging Improvements**: Flat structure logging without session_ prefix
-- **Memory System Expansion**: Added data_engineer and test_integration agents with specialized keywords
-- **Path Management System**: Implemented centralized configuration path handling
 
-### Project Cleanup & Organization
-- **Test File Migration**: Moved 66 test files from scripts/ to tests/ directory
-- **Documentation Archives**: Archived 35+ QA reports to docs/archive/
-- **Obsolete Directory Removal**: Cleaned up orchestration, docker, security, and terminal_wrapper directories
-- **Agent Registry Caching**: Enhanced performance with intelligent caching mechanisms
-- **Improved TodoWrite Integration**: Enhanced agent prefix guidelines across all agent templates
-
-See [CHANGELOG.md](CHANGELOG.md) for full history.
+### Developer Documentation
+- **[Architecture Overview](docs/ARCHITECTURE.md)** - Service-oriented architecture and design
+- **[Service Layer Guide](docs/developer/SERVICES.md)** - Service interfaces and implementations
+- **[Performance Guide](docs/PERFORMANCE.md)** - Optimization and caching strategies
+- **[Security Guide](docs/SECURITY.md)** - Security framework and best practices
+- **[Testing Guide](docs/TESTING.md)** - Testing patterns and strategies
+- **[Migration Guide](docs/MIGRATION.md)** - Upgrading from previous versions
+- **[Project Structure](docs/STRUCTURE.md)** - Codebase organization
+- **[Deployment Guide](docs/DEPLOY.md)** - Publishing and versioning
+- **[Developer Guide](docs/developer/)** - API reference and internals
+
+## Recent Updates (v3.7.8)
+
+### TSK-0053: Service Layer Architecture Refactoring
+- **Service-Oriented Architecture**: Complete redesign with five service domains
+- **Interface-Based Contracts**: All services implement explicit interfaces
+- **Dependency Injection System**: Service container with automatic dependency resolution
+- **Performance Optimizations**: Lazy loading, multi-level caching, connection pooling
+- **Security Framework**: Input validation, path traversal prevention, secure operations
+- **Backward Compatibility**: Lazy imports maintain existing import paths
+
+### Key Improvements
+- **50-80% Performance Improvement**: Optimized caching and lazy loading
+- **Enhanced Security**: Comprehensive input validation and sanitization
+- **Better Testability**: Interface-based architecture enables easy mocking
+- **Improved Maintainability**: Clear separation of concerns and service boundaries
+- **Developer Experience**: Rich documentation and migration guides
+
+### Architecture Benefits
+- **Scalability**: Service-oriented design supports future growth
+- **Extensibility**: Plugin architecture through interfaces and hooks
+- **Reliability**: Comprehensive testing with 85%+ coverage
+- **Security**: Defense-in-depth security architecture
+- **Performance**: Intelligent caching and resource optimization
+
+See [CHANGELOG.md](CHANGELOG.md) for full history and [docs/MIGRATION.md](docs/MIGRATION.md) for upgrade instructions.
 
 ## Development
 

{claude_mpm-3.7.8 → claude_mpm-3.8.1}/README.md

@@ -94,6 +94,26 @@ Dependencies are automatically aggregated from all agent sources (PROJECT > USER
 
 For comprehensive documentation, see [docs/AGENT_DEPENDENCIES.md](docs/AGENT_DEPENDENCIES.md).
 
+## Architecture
+
+Claude MPM v3.7.8+ features a **modern service-oriented architecture** with:
+
+### Service Layer Organization
+- **Core Services**: Foundation interfaces and dependency injection
+- **Agent Services**: Agent lifecycle, deployment, and management
+- **Communication Services**: Real-time WebSocket and SocketIO
+- **Project Services**: Project analysis and workspace management
+- **Infrastructure Services**: Logging, monitoring, and error handling
+
+### Key Architectural Features
+- **Interface-Based Design**: All services implement well-defined contracts
+- **Dependency Injection**: Loose coupling through service container
+- **Lazy Loading**: Performance optimization with deferred initialization
+- **Multi-Level Caching**: Intelligent caching with TTL and invalidation
+- **Security Framework**: Input validation, path sanitization, and secure operations
+
+For detailed architecture information, see [docs/ARCHITECTURE.md](docs/ARCHITECTURE.md).
+
 ## Key Capabilities
 
 ### Multi-Agent Orchestration
@@ -151,31 +171,48 @@ See [docs/developer/11-dashboard/README.md](docs/developer/11-dashboard/README.m
 
 ## Documentation
 
+### User Documentation
 - **[Quick Start Guide](QUICKSTART.md)** - Get running in 5 minutes
 - **[Agent Memory System](docs/MEMORY.md)** - Comprehensive memory documentation
 - **[Monitoring Dashboard](docs/developer/11-dashboard/README.md)** - Real-time monitoring features
-- **[Project Structure](docs/STRUCTURE.md)** - Codebase organization
-- **[Deployment Guide](docs/DEPLOY.md)** - Publishing and versioning
 - **[User Guide](docs/user/)** - Detailed usage documentation
-- **[Developer Guide](docs/developer/)** - Architecture and API reference
-
-## Recent Updates (v3.4.27)
-
-### Core System Enhancements
-- **Project Structure Reorganization**: Centralized path management with ClaudeMPMPaths enum
-- **Agent Services Hierarchy**: Reorganized agent and memory services into hierarchical structures  
-- **Response Logging Improvements**: Flat structure logging without session_ prefix
-- **Memory System Expansion**: Added data_engineer and test_integration agents with specialized keywords
-- **Path Management System**: Implemented centralized configuration path handling
 
-### Project Cleanup & Organization
-- **Test File Migration**: Moved 66 test files from scripts/ to tests/ directory
-- **Documentation Archives**: Archived 35+ QA reports to docs/archive/
-- **Obsolete Directory Removal**: Cleaned up orchestration, docker, security, and terminal_wrapper directories
-- **Agent Registry Caching**: Enhanced performance with intelligent caching mechanisms
-- **Improved TodoWrite Integration**: Enhanced agent prefix guidelines across all agent templates
-
-See [CHANGELOG.md](CHANGELOG.md) for full history.
+### Developer Documentation
+- **[Architecture Overview](docs/ARCHITECTURE.md)** - Service-oriented architecture and design
+- **[Service Layer Guide](docs/developer/SERVICES.md)** - Service interfaces and implementations
+- **[Performance Guide](docs/PERFORMANCE.md)** - Optimization and caching strategies
+- **[Security Guide](docs/SECURITY.md)** - Security framework and best practices
+- **[Testing Guide](docs/TESTING.md)** - Testing patterns and strategies
+- **[Migration Guide](docs/MIGRATION.md)** - Upgrading from previous versions
+- **[Project Structure](docs/STRUCTURE.md)** - Codebase organization
+- **[Deployment Guide](docs/DEPLOY.md)** - Publishing and versioning
+- **[Developer Guide](docs/developer/)** - API reference and internals
+
+## Recent Updates (v3.7.8)
+
+### TSK-0053: Service Layer Architecture Refactoring
+- **Service-Oriented Architecture**: Complete redesign with five service domains
+- **Interface-Based Contracts**: All services implement explicit interfaces
+- **Dependency Injection System**: Service container with automatic dependency resolution
+- **Performance Optimizations**: Lazy loading, multi-level caching, connection pooling
+- **Security Framework**: Input validation, path traversal prevention, secure operations
+- **Backward Compatibility**: Lazy imports maintain existing import paths
+
+### Key Improvements
+- **50-80% Performance Improvement**: Optimized caching and lazy loading
+- **Enhanced Security**: Comprehensive input validation and sanitization
+- **Better Testability**: Interface-based architecture enables easy mocking
+- **Improved Maintainability**: Clear separation of concerns and service boundaries
+- **Developer Experience**: Rich documentation and migration guides
+
+### Architecture Benefits
+- **Scalability**: Service-oriented design supports future growth
+- **Extensibility**: Plugin architecture through interfaces and hooks
+- **Reliability**: Comprehensive testing with 85%+ coverage
+- **Security**: Defense-in-depth security architecture
+- **Performance**: Intelligent caching and resource optimization
+
+See [CHANGELOG.md](CHANGELOG.md) for full history and [docs/MIGRATION.md](docs/MIGRATION.md) for upgrade instructions.
 
 ## Development
 

claude_mpm-3.8.1/VERSION

@@ -0,0 +1 @@
+3.8.1

claude_mpm-3.8.1/scripts/ticket

@@ -0,0 +1,38 @@
+#!/usr/bin/env bash
+# Ticket Management Shell Wrapper for claude-mpm
+#
+# WHY: This shell script provides backward compatibility for users who use the
+# 'ticket' command directly from the shell. It delegates all operations to the
+# integrated claude-mpm tickets command.
+#
+# DESIGN DECISION: This thin wrapper maintains the existing shell interface while
+# delegating to the new claude-mpm tickets subcommands for consistency.
+
+# Find the project root
+SCRIPT_DIR="$( cd "$( dirname "${BASH_SOURCE[0]}" )" && pwd )"
+PROJECT_ROOT="$( cd "$SCRIPT_DIR/.." && pwd )"
+
+# Check if we should use local claude-mpm or installed version
+if [ -f "$PROJECT_ROOT/claude-mpm" ] && [ -d "$PROJECT_ROOT/src/claude_mpm" ]; then
+    # Use local development version
+    CLAUDE_MPM="$PROJECT_ROOT/claude-mpm"
+else
+    # Use installed version
+    CLAUDE_MPM="claude-mpm"
+fi
+
+# Check if claude-mpm is available
+if ! command -v "$CLAUDE_MPM" &> /dev/null && [ "$CLAUDE_MPM" = "claude-mpm" ]; then
+    echo "Error: claude-mpm not found. Please ensure it's installed and in your PATH."
+    echo "Install with: pip install claude-mpm"
+    exit 1
+fi
+
+# Delegate to claude-mpm tickets command
+# If no arguments or help requested, show help
+if [ $# -eq 0 ] || [ "$1" = "help" ] || [ "$1" = "--help" ] || [ "$1" = "-h" ]; then
+    exec "$CLAUDE_MPM" tickets --help
+else
+    # Pass all arguments to claude-mpm tickets
+    exec "$CLAUDE_MPM" tickets "$@"
+fi

claude_mpm-3.8.1/src/claude_mpm/VERSION

@@ -0,0 +1 @@
+3.8.1

{claude_mpm-3.7.8 → claude_mpm-3.8.1}/src/claude_mpm/agents/BASE_PM.md

@@ -2,12 +2,6 @@
 
 **CRITICAL**: These are non-negotiable framework requirements that apply to ALL PM configurations.
 
-## Temporal Context
-**Today's Date**: {{current-date}}
-Apply date awareness to all time-sensitive tasks and decisions.
-
-{{agent-capabilities}}
-
 ## TodoWrite Framework Requirements
 
 ### Mandatory [Agent] Prefix Rules
@@ -62,95 +56,6 @@ Apply date awareness to all time-sensitive tasks and decisions.
 - Include acceptance criteria where helpful
 - Reference relevant files or context
 
-## Memory Management Protocol
-
-### Memory Evaluation (MANDATORY for ALL user prompts)
-
-**Memory Trigger Words/Phrases**:
-- "remember", "don't forget", "keep in mind", "note that"
-- "make sure to", "always", "never", "important"
-- "going forward", "in the future", "from now on"
-- "this pattern", "this approach", "this way"
-- Project-specific standards or requirements
-
-**When Memory Indicators Detected**:
-1. **Extract Key Information**: Identify facts, patterns, or guidelines to preserve
-2. **Determine Agent & Type**:
-   - Code patterns/standards → Engineer Agent (type: pattern)
-   - Architecture decisions → Research Agent (type: architecture)
-   - Testing requirements → QA Agent (type: guideline)
-   - Security policies → Security Agent (type: guideline)
-   - Documentation standards → Documentation Agent (type: guideline)
-   - Deployment patterns → Ops Agent (type: strategy)
-   - Data schemas → Data Engineer Agent (type: architecture)
-3. **Delegate Storage**: Use memory task format with appropriate agent
-4. **Confirm to User**: "Storing this information: [brief summary] for [agent]"
-
-### Memory Storage Task Format
-
-```
-Task: Store project-specific memory
-Agent: <appropriate agent based on content>
-Context:
-  Goal: Preserve important project knowledge for future reference
-  Memory Request: <user's original request>
-  Suggested Format:
-    # Add To Memory:
-    Type: <pattern|architecture|guideline|mistake|strategy|integration|performance|context>
-    Content: <concise summary under 100 chars>
-    #
-```
-
-### Agent Memory Routing Matrix
-
-**Engineering Agent Memory**:
-- Implementation patterns and anti-patterns
-- Code architecture and design decisions
-- Performance optimizations and bottlenecks
-- Technology stack choices and constraints
-
-**Research Agent Memory**:
-- Analysis findings and investigation results
-- Domain knowledge and business logic
-- Architectural decisions and trade-offs
-- Codebase patterns and conventions
-
-**QA Agent Memory**:
-- Testing strategies and coverage requirements
-- Quality standards and acceptance criteria
-- Bug patterns and regression risks
-- Test infrastructure and tooling
-
-**Security Agent Memory**:
-- Security patterns and vulnerabilities
-- Threat models and attack vectors
-- Compliance requirements and policies
-- Authentication/authorization patterns
-
-**Documentation Agent Memory**:
-- Writing standards and style guides
-- Content organization patterns
-- API documentation conventions
-- User guide templates
-
-**Data Engineer Agent Memory**:
-- Data pipeline patterns and ETL strategies
-- Schema designs and migrations
-- Performance tuning techniques
-- Data quality requirements
-
-**Ops Agent Memory**:
-- Deployment patterns and rollback procedures
-- Infrastructure configurations
-- Monitoring and alerting strategies
-- CI/CD pipeline requirements
-
-**Version Control Agent Memory**:
-- Branching strategies and conventions
-- Commit message standards
-- Code review processes
-- Release management patterns
-
 ## PM Response Format
 
 **CRITICAL**: As the PM, you must also provide structured responses for logging and tracking.
@@ -260,14 +165,3 @@ The authentication system is now complete with support for Google, GitHub, and M
   ]
 }
 ```
-
-## Framework Integration Notes
-
-**IMPORTANT**: These framework requirements are injected AFTER custom INSTRUCTIONS.md to ensure:
-1. Core framework behaviors are always preserved
-2. TodoWrite prefix rules are consistently enforced
-3. Memory management protocols are standardized
-4. Response formats enable proper logging
-5. Custom instructions cannot override framework requirements
-
-This separation ensures the PM system maintains architectural integrity while allowing project-specific customization through INSTRUCTIONS.md.