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

docs/jobq.md: drop the core-specific node table, keep only the abstract engine explanation

Browse source 
mara: "only the abstract jobq part was asked for in the first place" —
the previous revision still carried the full hive-c0re step-kind table
under a "core-specific nodes" heading; that catalogue belongs in
coordinator.md (where it already lived) alongside the rest of
hive-c0re's job-queue internals, not duplicated here.

jobq.md is now just the domain-agnostic model (graph of steps + shared
resource slots) plus the generic row/step/glyph framing for watching it
in the dashboard — no hive-c0re-specific step names anywhere.
Coordinator.md's job-queue section, docs/README.md, and the root
CLAUDE.md reading-paths index are updated to match.
This commit is contained in:
iris 2026-08-26 22:48:17 +02:00 • committed by mara
commit 8363a459bf
4 changed files with 43 additions and 92 deletions
Download patch file Download diff file Expand all files Collapse all files

7
docs/coordinator.md
View file

@ -8,9 +8,10 @@ and `docs/persistence.md`.
## Job queue
**For what each step means to someone watching the dashboard, without the
implementation detail below, see [`jobq.md`](jobq.md) instead** — this
section stays at the internals level (module layout, scheduler mechanics,
**For the job queue as a general idea — graph of steps, shared resource
slots, no hive-c0re specifics — see [`jobq.md`](jobq.md) instead.** This
section covers the concrete node inventory hive-c0re builds on top of that
engine, plus the internals (module layout, scheduler mechanics,
resource/lease semantics).
Every container/meta operation (rebuild, meta-update, first-spawn, power