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

scheduling.md: drop the list_schedules prose, keep the approval-scope fix

Browse source 
mara's call on this PR was "list schedules not being scoped at all is a
bug - dont document it, file the bug and fix it". The bug is fixed in
damocles's separate PR, which also rewrites this page's
`list_schedules()` section.

So both of my paragraphs about scoping go: the "not scoped at all"
sentence in the intro (documenting the bug, which is what she
objected to) and the follow-up in the `list_schedules()` section. That
section is now byte-identical to main again, leaving it entirely to the
PR that changes the behaviour — the two PRs no longer touch a common
hunk in this file.

What stays is the claim this PR was actually filed for: the page said
"All scheduling ops go through the operator approval queue", and only
creating one does. The intro now splits creating from the other four
verbs and states the one authorization rule that covers all of them,
which the scoping fix makes true.
This commit is contained in:
atlas 2026-09-11 17:35:37 +02:00 • committed by mara
commit 6d7565a30d
1 changed files with 4 additions and 9 deletions
Download patch file Download diff file Expand all files Collapse all files

13
docs/tools/scheduling.md
View file

@ -10,11 +10,10 @@ targets only yourself — use `remind` for an unapproved self-wake. The
other four verbs need no approval: holding the `scheduling` tool group
is the whole gate.
Authorization for cancel / edit / fire: you can act on schedules you own
or any owned by an agent in your topology subtree. **`list_schedules` is
not scoped at all** — it returns every schedule on the hive, bodies
included, which is what makes it useful for auditing and worth knowing
before you put anything private in a schedule body.
Authorization is one rule for all four verbs: you reach schedules you own
and any owned by an agent in your topology subtree. `list_schedules`
applies it too, so the snapshot only ever shows schedules you could also
cancel.
### `request_schedule_prompt(targets, body, first_fire_at_unix, interval_seconds?, description?)`
@ -62,10 +61,6 @@ and `last_result`, `next_fire_at_unix`, `interval_seconds`. Use to
look up an id before cancelling, or to audit upcoming wake-ups in
your subtree.
Unscoped on purpose — unlike the verbs that _change_ a schedule, this
one applies no ownership filter, so the snapshot covers other agents'
schedules and the operator's.
## `diagnostics` tool group
### `get_logs(agent, lines?)`