- ✅ JWT authentication system implemented
- ✅ django-ninja API setup completed
- ✅ Enhanced testing infrastructure established
- ✅ Caddy ingress proxy and development configuration finalized
- ✅ Custom User model with invitation system
- ✅ Base models with UUID primary keys and timestamps
-
Create Room model and app structure
- Create
deputy/apps/rooms/Django app - Implement Room model with:
- UUID primary key
slug(URL-friendly unique identifier)topic(CharField)start_date,completion_date(DateTimeField)summary(TextField)user_participants(M2M with User)agent_participants(M2M - for future agent entities)
- Add model methods:
is_active(),mark_completed() - Acceptance Criteria: Room model created with migrations, admin interface configured
- Create
-
Message model implementation
- Create Message model linking to Room
- Support user and agent message types
- Implement message ordering and timestamps
- Add support for @mentions detection
- Acceptance Criteria: Messages can be created and retrieved for rooms
-
Implement InquiryTriageWorkflow
- Create workflow class for inquiry evaluation
- Design structured output:
InquiryTriageResponse - Implement room suggestion logic
- Add methods:
evaluate_inquiry(),suggest_rooms(),create_new_room() - Acceptance Criteria: Workflow can determine room assignment strategy
-
Create begin-new-inquiry endpoint
- django-ninja endpoint at
/api/begin-new-inquiry - Input validation for inquiry data
- Integration with InquiryTriageWorkflow
- Return structured response with room suggestions
- Handle uncertainty with multiple suggestions
- Acceptance Criteria: Endpoint creates or suggests rooms based on inquiry
- django-ninja endpoint at
-
Implement send-message endpoint
- Create
/api/rooms/{room_slug}/send-message - Add message to room without necessarily waking agents
- Handle @agent mentions for wake triggers
- Support different message types (text, code, files)
- Acceptance Criteria: Messages can be sent to rooms with proper handling
- Create
-
Implement trigger_completion endpoint
- Create
/api/rooms/{room_slug}/trigger-completion - Explicitly wake specified agent
- Track agent activation state
- Queue agent processing tasks
- Acceptance Criteria: Agents can be explicitly triggered for room processing
- Create
-
Research django-ergo agent assignment
- Analyze how ergo assigns agents/workflows to conversations
- Map ergo's conversation model to our Room model
- Design integration adapters
- Document agent lifecycle management
- Acceptance Criteria: Clear integration strategy documented
-
Implement ergo-room adapter
- Create adapter classes for ergo integration
- Map Room to ergo conversation context
- Implement agent assignment logic
- Add workflow persistence
- Acceptance Criteria: Rooms can use ergo workflows and agents
-
WebSocket support for rooms
- Implement Django Channels for WebSocket
- Real-time message delivery
- Typing indicators
- Agent status updates
- Acceptance Criteria: Real-time updates work in rooms
-
Room participant management
- Add/remove participants APIs
- Participant permissions (viewer, contributor, admin)
- Notification system for participant events
- Acceptance Criteria: Multi-user room collaboration works
-
Room search and filtering
- Full-text search on topics and messages
- Filter by participants, date, status
- Room archival system
- Acceptance Criteria: Users can find rooms efficiently
-
Room templates and presets
- Create room templates for common workflows
- Quick-start room creation
- Template sharing between users
- Acceptance Criteria: Users can create rooms from templates
-
Design agent container architecture
- Define agent container specifications
- Create Dockerfile templates for agents
- Design container networking for room communication
- Plan security isolation between containers
- Acceptance Criteria: Agent architecture documented
-
Implement Docker agent spawning
- Docker client integration service
- Agent lifecycle management (create, monitor, destroy)
- Container health checks
- Container-to-room communication channels
- Acceptance Criteria: Agents spawn in containers and connect to rooms
-
MCP tooling for agents
- Research Model Context Protocol spec
- Design Deputy-specific MCP implementation
- Create MCP message handling for rooms
- Build tool registration system
- Acceptance Criteria: Agents can use MCP tools in rooms
-
Agent capability discovery
- Agent capability registration
- Dynamic tool discovery
- Capability-based agent selection
- Acceptance Criteria: System knows agent capabilities
-
Complete frontend migration to Vite+React
- Set up Vite+React+TypeScript structure
- Migrate authentication components
- Remove Next.js completely
- Acceptance Criteria: New frontend stack operational
-
Room chat interface
- Chat message components with markdown
- Room participant list
- Message history and scrolling
- File upload and sharing
- Acceptance Criteria: Full-featured room chat UI
-
Room management UI
- Room creation wizard
- Room list and search
- Room settings and participant management
- Agent activation controls
- Acceptance Criteria: Users can manage rooms through UI
- Rich message formatting
- Code syntax highlighting
- File previews
- Agent response formatting
- Copy/download functionality
- Acceptance Criteria: Professional message display
-
Hierarchical room structures
- Parent-child room relationships
- Room inheritance and templates
- Cross-room agent coordination
- Acceptance Criteria: Complex multi-room workflows
-
Workflow automation
- Scheduled room actions
- Trigger-based agent activation
- Workflow templates and sharing
- Acceptance Criteria: Automated room workflows
- Agent discovery and installation
- Agent registry and marketplace
- Agent rating and reviews
- Custom agent development SDK
- Acceptance Criteria: Users can discover and use community agents
- Room analytics dashboard
- Message volume and patterns
- Agent performance metrics
- User engagement tracking
- Cost and resource usage
- Acceptance Criteria: Comprehensive room analytics
-
Organization-wide room management
- Organization room templates
- Compliance and audit logging
- Advanced permission systems
- SSO and enterprise auth
- Acceptance Criteria: Enterprise-ready room system
-
AI-powered room optimization
- Automatic agent selection
- Predictive room suggestions
- Smart routing and load balancing
- ML-based workflow optimization
- Acceptance Criteria: AI enhances room efficiency
-
Public API and SDK
- Comprehensive room management API
- Client SDKs for multiple languages
- Webhook system for integrations
- Plugin architecture
- Acceptance Criteria: Third-party room integrations
-
Cross-platform clients
- Mobile apps (iOS/Android)
- Desktop apps (Electron)
- CLI tools for rooms
- IDE integrations
- Acceptance Criteria: Rooms accessible everywhere
- Room templates marketplace
- Voice/video in rooms (WebRTC)
- Room analytics and insights
- Scheduled room events
- Room-based billing and quotas
- Room export/import functionality
- Room version control and history
- Collaborative editing in rooms
- Room-specific agent training
- Cross-organization room sharing
- Agent skill trees and specialization
- Multi-agent coordination protocols
- Agent performance benchmarking
- Custom agent development framework
- Agent cost optimization
- Agent fallback and redundancy
- Agent security sandboxing
- Agent marketplace and monetization
- Agent fine-tuning per room
- Agent collaboration patterns
- GraphQL API alongside REST
- Real-time collaboration cursors
- Advanced search with Elasticsearch
- Message encryption (E2E)
- Federated room networks
- Blockchain-based audit trails
- AR/VR room interfaces
- Natural language room commands
- Predictive text and autocomplete
- Smart notifications and digests
- Test Coverage: Maintain > 90% test coverage
- Type Safety: Full TypeScript/Python typing
- Documentation: OpenAPI specs for all endpoints
- Performance: < 100ms API response times
- Room Isolation: Strict data separation
- Agent Sandboxing: Container security
- Input Validation: All inputs sanitized
- Audit Logging: All room actions logged
- Domain-Driven Design: Clear bounded contexts
- Event-Driven: Room events for extensibility
- API-First: All features via API
- Progressive Enhancement: Graceful degradation
- Core room functionality
- Basic agent integration
- Security and authentication
- Enhanced user experience
- Performance optimization
- Developer tools
- Advanced features
- Third-party integrations
- Analytics and insights
- Experimental features
- Nice-to-have improvements
- Long-term research
- Room creation: < 1 second
- Message delivery: < 100ms
- Agent spawn time: < 5 seconds
- System uptime: > 99.9%
- Daily active rooms: > 100
- Messages per room: > 50/day
- Agent utilization: > 60%
- User retention: > 70% (7-day)
- Room completion rate: > 80%
- Agent efficiency: > 10x human
- Cost per room: < $0.10
- Revenue per user: > $50/month