From d2c4c8d4a3eb740f455273257225824d4ff1f4f8 Mon Sep 17 00:00:00 2001 From: atlas Date: Wed, 23 Sep 2026 17:11:45 +0200 Subject: [PATCH] docs: drop dead-claim narration for the retired loose-ends override The PR retiring loose-ends' manager-only visibility replaced the false claim with prose narrating its retirement, which still adds lines for a removal. Delete the dead claim outright instead of documenting that it used to be true: drop the three added sentences in agent-hierarchy.md, and shorten socket_server/mod.rs's authority comment to state only what's true now (tool-group membership for the orchestration verbs) rather than adding an explanatory clause for the removed capability check. --- docs/agent-lifecycle/agent-hierarchy.md | 5 +---- hive-c0re/src/socket_server/mod.rs | 8 +++----- 2 files changed, 4 insertions(+), 9 deletions(-) diff --git a/docs/agent-lifecycle/agent-hierarchy.md b/docs/agent-lifecycle/agent-hierarchy.md index 0ddc0bc5..e3b484d3 100644 --- a/docs/agent-lifecycle/agent-hierarchy.md +++ b/docs/agent-lifecycle/agent-hierarchy.md @@ -139,10 +139,7 @@ the crash-watch loop). Each is planned to become a capability check instead of a manager-name check — see the module docs for `stores/broker.rs`, `actions.rs`, and `workers/crash_watch.rs` for the current owner-check logic in -each. Loose-ends visibility used to be on this list; it isn't a -manager override any more — `GetLooseEnds` takes no target and every -agent, `ruth` included, sees only its own rows. -(The harness handles reminder cancellation fully in-agent — see +each. (The harness handles reminder cancellation fully in-agent — see the note on `CancelLooseEndKind::Reminder` in `hive-c0re/src/socket_server/mod.rs`.) diff --git a/hive-c0re/src/socket_server/mod.rs b/hive-c0re/src/socket_server/mod.rs index 158c908f..9b6c84b4 100644 --- a/hive-c0re/src/socket_server/mod.rs +++ b/hive-c0re/src/socket_server/mod.rs @@ -4,11 +4,9 @@ //! you are `foo`; the manager socket simply serves as `ruth`. There is no //! privilege flag — both transports run the same [`serve`] / [`dispatch`] //! code, and authority derives uniformly from the caller's identity: -//! tool-group membership for the orchestration verbs, and nothing else — -//! the queries are all self-scoped, so no capability is consulted here at -//! all. An agent-targeting verb may name any agent, so `ruth` -//! reaches every agent exactly the way every other agent does, not via any -//! hardcoded name match. +//! tool-group membership for the orchestration verbs. An agent-targeting +//! verb may name any agent, so `ruth` reaches every agent exactly the way +//! every other agent does, not via any hardcoded name match. use std::path::{Path, PathBuf}; use std::sync::Arc;