vinzenz/hyperhive
vinzenz/hyperhive
Watch
0
0
Fork
You've already forked hyperhive
 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions 1

rename(162): drop HIVE_PORT fallback; sweep remaining hm1nd in docs

Browse source
This commit is contained in:
damocles 2026-06-01 17:35:19 +02:00 • committed by mara
commit 008609d0e7
7 changed files with 26 additions and 31 deletions
Download patch file Download diff file Expand all files Collapse all files

4
docs/damocles-migration.md
View file

@ -38,7 +38,7 @@ other sub-agents but is not managed by hive-c0re.
Pros: low blast radius. damocles keeps its bind-mounts + its own restart policy.
Manager can route messages to it (it's just another inbox key on the broker).
Cons: two lifecycle mechanisms coexist forever; "damocles" doesn't appear in the
dashboard's container list (it filters `hive-` and `hm1nd`).
dashboard's container list (it filters `hive-` and `root`).
### C. Don't migrate
damocles stays out of hyperhive. The two systems coexist; the user's day-job
@ -52,7 +52,7 @@ Cons: no message routing between damocles and the swarm.
**C for now, B once cross-pollination is wanted.** Hyperhive's invariants
(11-char container names, manager-driven lifecycle, sealed `applied/` config)
fit poorly with damocles's role as the user's working Claude. Wait until there's
a concrete reason to wire them together (e.g. "I want to ask hm1nd from inside
a concrete reason to wire them together (e.g. "I want to ask root from inside
damocles") and then do B — extend the broker socket bind into damocles and
install `hive-ag3nt` there. No need to subsume damocles under hive-c0re.