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

docs: drop dead-claim narration for the retired loose-ends override

Browse source 
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.
This commit is contained in:
atlas 2026-09-23 17:11:45 +02:00 • committed by mara
commit d2c4c8d4a3
2 changed files with 4 additions and 9 deletions
Download patch file Download diff file Expand all files Collapse all files

5
docs/agent-lifecycle/agent-hierarchy.md
View file

@ -139,10 +139,7 @@ the crash-watch loop). Each is planned to become a capability
check instead of a manager-name check — see the check instead of a manager-name check — see the
module docs for `stores/broker.rs`, `actions.rs`, module docs for `stores/broker.rs`, `actions.rs`,
and `workers/crash_watch.rs` for the current owner-check logic in 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 each. (The harness handles reminder cancellation fully in-agent — see
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
the note on `CancelLooseEndKind::Reminder` in the note on `CancelLooseEndKind::Reminder` in
`hive-c0re/src/socket_server/mod.rs`.) `hive-c0re/src/socket_server/mod.rs`.)
<!-- vale write-good.Passive = YES --> <!-- vale write-good.Passive = YES -->

8
hive-c0re/src/socket_server/mod.rs
View file

@ -4,11 +4,9 @@
//! you are `foo`; the manager socket simply serves as `ruth`. There is no //! you are `foo`; the manager socket simply serves as `ruth`. There is no
//! privilege flag — both transports run the same [`serve`] / [`dispatch`] //! privilege flag — both transports run the same [`serve`] / [`dispatch`]
//! code, and authority derives uniformly from the caller's identity: //! code, and authority derives uniformly from the caller's identity:
//! tool-group membership for the orchestration verbs, and nothing else — //! tool-group membership for the orchestration verbs. An agent-targeting
//! the queries are all self-scoped, so no capability is consulted here at //! verb may name any agent, so `ruth` reaches every agent exactly the way
//! all. An agent-targeting verb may name any agent, so `ruth` //! every other agent does, not via any hardcoded name match.
//! reaches every agent exactly the way every other agent does, not via any
//! hardcoded name match.
use std::path::{Path, PathBuf}; use std::path::{Path, PathBuf};
use std::sync::Arc; use std::sync::Arc;