e820770409
PHASE 3 IMPLEMENTATION COMPLETE: ✅ Collaborative Editing Interfaces: - Full session management (start, join, list, status, leave) - DHT-based persistent collaborative sessions - Real-time collaborative editor with conflict resolution - Multi-participant support with automatic sync - Chat integration for collaborative coordination - HMMM network integration for all collaborative events ✅ Decision Tracking and Approval Workflows: - Complete decision lifecycle (create, view, vote, track) - DHT storage system for persistent decisions - Rich voting system (approve, reject, defer, abstain) - Real-time vote tracking with approval percentages - HMMM announcements for proposals and votes - Multiple decision types (technical, operational, policy, emergency) ✅ Web Bridge for Browser-Based HAP Interface: - Complete HTTP server on port 8090 - Modern responsive web UI with card-based layout - Functional decision management with JavaScript voting - Real-time status monitoring and network information - REST API endpoints for all major HAP functions - WebSocket infrastructure for real-time updates TECHNICAL HIGHLIGHTS: - Added CollaborativeSession and Decision data structures - Enhanced TerminalInterface with web server support - Full P2P integration (DHT storage, HMMM messaging) - Professional web interface with intuitive navigation - API-driven architecture ready for multi-user scenarios FEATURES DELIVERED: - Multi-modal access (terminal + web interfaces) - Real-time P2P coordination across all workflows - Network-wide event distribution and collaboration - Production-ready error handling and validation - Scalable architecture supporting mixed human/agent teams Phase 3 objectives fully achieved. CHORUS HAP now provides comprehensive human agent participation in P2P task coordination with both power-user terminal access and user-friendly web interfaces. 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com>
CHORUS - Container-First P2P Task Coordination System
CHORUS is a next-generation P2P task coordination and collaborative AI system designed from the ground up for containerized deployments. It takes the best lessons learned from CHORUS and reimagines them for Docker Swarm, Kubernetes, and modern container orchestration platforms.
Vision
CHORUS enables distributed AI agents to coordinate, collaborate, and execute tasks across container clusters, supporting deployments from single containers to hundreds of instances in enterprise environments.
Key Design Principles
- Container-First: Designed specifically for Docker/Kubernetes deployments
- License-Controlled: Simple environment variable-based licensing
- Cloud-Native Logging: Structured logging to stdout/stderr for container runtime collection
- Swarm-Ready P2P: P2P protocols optimized for container networking
- Scalable Agent IDs: Agent identification system that works across distributed deployments
- Zero-Config: Minimal configuration requirements via environment variables
Architecture
CHORUS follows a microservices architecture where each container runs a single agent instance:
┌─────────────────┐ ┌─────────────────┐ ┌─────────────────┐
│ CHORUS Agent │ │ CHORUS Agent │ │ CHORUS Agent │
│ Container 1 │◄─┤ Container 2 │─►│ Container N │
└─────────────────┘ └─────────────────┘ └─────────────────┘
│ │ │
└──────────────────────┼──────────────────────┘
│
┌─────────────────┐
│ Container │
│ Network │
│ (P2P Mesh) │
└─────────────────┘
Quick Start
Prerequisites
- Docker & Docker Compose
- Valid CHORUS license key
- Access to Ollama endpoints for AI functionality
Basic Deployment
- Clone and configure:
git clone https://gitea.chorus.services/tony/CHORUS.git
cd CHORUS
cp docker/chorus.env.example docker/chorus.env
# Edit docker/chorus.env with your license key and configuration
- Deploy:
docker-compose -f docker/docker-compose.yml up -d
- Scale (Docker Swarm):
docker service scale chorus_agent=10
Licensing
CHORUS requires a valid license key to operate. Set your license key in the environment:
CHORUS_LICENSE_KEY=your-license-key-here
CHORUS_LICENSE_EMAIL=your-email@example.com
No license = No operation. CHORUS will not start without valid licensing.
Differences from CHORUS
| Aspect | CHORUS | CHORUS |
|---|---|---|
| Deployment | systemd service (1 per host) | Container (N per cluster) |
| Configuration | Web UI setup | Environment variables |
| Logging | Journal/files | stdout/stderr (structured) |
| Licensing | Setup-time validation | Runtime environment variable |
| Agent IDs | Host-based | Container/cluster-based |
| P2P Discovery | mDNS local network | Container network + service discovery |
Development Status
🚧 Early Development - CHORUS is being designed and built. Not yet ready for production use.
Current Phase: Architecture design and core foundation development.
License
CHORUS is a commercial product. Contact chorus.services for licensing information.
Contributing
CHORUS is developed by the chorus.services team. For contributions or feedback, please use the issue tracker on our GITEA instance.