tony/CHORUS
1
0
Fork 0
Code Issues 10 Pull Requests Actions Packages Projects Releases Wiki Activity

refactor CHORUS

Browse Source
This commit is contained in:
anthonyrawlins
2025-09-06 14:47:41 +10:00
parent 9bdcbe0447
commit b6634e4c1b
16 changed files with 225 additions and 225 deletions
Download Patch File Download Diff File Expand all files Collapse all files

10
HAP_ACTION_PLAN.md
View File

@@ -133,7 +133,7 @@ CHORUS currently implements a **comprehensive P2P autonomous agent system** with
| **HAP Interface** | ❌ Not implemented | Required | **Phase 2-3** |
### Shared Runtime Components
Both `bzzz-agent` and `bzzz-hap` will share:
Both `chorus-agent` and `chorus-hap` will share:
- **P2P networking** and peer discovery
- **Agent identity** and cryptographic signing
@@ -155,7 +155,7 @@ Both `bzzz-agent` and `bzzz-hap` will share:
4. **Gradual enhancement** - start with basic HAP, add features incrementally
### Key Principles
- **Backward compatibility**: Existing BZZZ deployments unaffected
- **Backward compatibility**: Existing CHORUS deployments unaffected
- **Shared protocols**: Human and machine agents are indistinguishable on P2P mesh
- **Common codebase**: Maximum code reuse between binaries
- **Incremental delivery**: Each phase delivers working functionality
@@ -171,7 +171,7 @@ Both `bzzz-agent` and `bzzz-hap` will share:
## 📈 Success Metrics
### Phase 1 Success
- [ ] `make build` produces both `bzzz-agent` and `bzzz-hap` binaries
- [ ] `make build` produces both `chorus-agent` and `chorus-hap` binaries
- [ ] Existing autonomous agent functionality unchanged
- [ ] Both binaries can join same P2P mesh
@@ -217,7 +217,7 @@ Both `bzzz-agent` and `bzzz-hap` will share:
## 📚 Resources & References
- **Original HAP Plan**: `archive/bzzz_hap_dev_plan.md`
- **Original HAP Plan**: `archive/chorus_hap_dev_plan.md`
- **Current Architecture**: `pkg/` directory structure
- **P2P Infrastructure**: `p2p/`, `pubsub/`, `pkg/dht/`
- **Agent Identity**: `pkg/agentid/`, `pkg/crypto/`
@@ -225,4 +225,4 @@ Both `bzzz-agent` and `bzzz-hap` will share:
- **Context System**: `pkg/ucxl/`, `pkg/ucxi/`
- **Configuration**: `pkg/config/`, role definitions
The current BZZZ implementation provides an excellent foundation for the HAP vision. The primary challenge is architectural restructuring rather than building new functionality from scratch.
The current CHORUS implementation provides an excellent foundation for the HAP vision. The primary challenge is architectural restructuring rather than building new functionality from scratch.