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

docs(persistence): correct the root-container destroy claim (imperative, not declarative)

Browse source 
The 'non-destroyable (declarative; would fight with host NixOS config)'
claim was stale: the root/bootstrap container is imperative
infrastructure, managed end-to-end by hive-c0re (auto_update::
ensure_root_agent recreates it on startup if absent). The actions::
destroy bail is a soft policy guard, and destroying the container is
transient anyway — it's recreated on the next hive-c0re startup.
This commit is contained in:
iris 2026-06-23 13:55:25 +02:00 • committed by mara
commit 20e26ad28d
1 changed files with 7 additions and 2 deletions
Download patch file Download diff file Expand all files Collapse all files

9
docs/persistence.md
View file

@ -285,8 +285,13 @@ step would re-fire).
claude creds, /state/ notes, and the harness dir are all gone. claude creds, /state/ notes, and the harness dir are all gone.
No undo. No undo.
The root/bootstrap container is non-destroyable from both paths The root/bootstrap container is **imperative** infrastructure — managed
(declarative container; would fight with the host's NixOS config). end-to-end by hive-c0re, not declared in the host's NixOS config.
`auto_update::ensure_root_agent` recreates it on the next hive-c0re
startup if it's absent (bypassing the approval queue, as required
infrastructure). A soft policy guard in `actions::destroy` currently
refuses to destroy it; even without that guard, destroying it would only
be transient — hive-c0re brings it back on the next startup.
### btrfs subvolumes for `/var/lib/hyperhive/agents/<name>` ### btrfs subvolumes for `/var/lib/hyperhive/agents/<name>`