From 20e26ad28dbbc441d7a07c60d1dbe90377724d6b Mon Sep 17 00:00:00 2001 From: iris Date: Tue, 23 Jun 2026 13:55:25 +0200 Subject: [PATCH] docs(persistence): correct the root-container destroy claim (imperative, not declarative) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit 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. --- docs/persistence.md | 9 +++++++-- 1 file changed, 7 insertions(+), 2 deletions(-) diff --git a/docs/persistence.md b/docs/persistence.md index 7cbc4f31..c958220d 100644 --- a/docs/persistence.md +++ b/docs/persistence.md @@ -285,8 +285,13 @@ step would re-fire). claude creds, /state/ notes, and the harness dir are all gone. No undo. -The root/bootstrap container is non-destroyable from both paths -(declarative container; would fight with the host's NixOS config). +The root/bootstrap container is **imperative** infrastructure — managed +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/`