Registers issue 312 under playbook 03. While investigating issue 306 (checks 5–7x slower on the control node), no mesh tool could report CPU iowait, a disk's utilisation, throughput, wait or queue depth, I/O pressure, or which unit, container or process was doing the I/O. ADR 0245 rules out working around that with a login.
Status located, in mesh-catalog modules/disk-load, and fixed by novox/mesh-catalog PR #120: a new read-only module with tools disk_load, disk_top, disk_filesystems and disk_devices. The diagnosis records why this is a module and not a verb on an existing seat, a new seat (ADR 0246), memory-pressure or the container module. It also records one finding from the build: /proc/<pid>/io cannot see another account's processes, so units and containers are ranked from their cgroups' io.stat instead. This is not a core issue, so it needs no replay.
Checks: merge-check.sh (cycle, records, index, words, with MESH_CATALOG_DIR set) all pass.
Registers issue 312 under playbook 03. While investigating issue 306 (checks 5–7x slower on the control node), no mesh tool could report CPU iowait, a disk's utilisation, throughput, wait or queue depth, I/O pressure, or which unit, container or process was doing the I/O. ADR 0245 rules out working around that with a login.
Status `located`, in `mesh-catalog modules/disk-load`, and fixed by novox/mesh-catalog PR #120: a new read-only module with tools `disk_load`, `disk_top`, `disk_filesystems` and `disk_devices`. The diagnosis records why this is a module and not a verb on an existing seat, a new seat (ADR 0246), `memory-pressure` or the container module. It also records one finding from the build: `/proc/<pid>/io` cannot see another account's processes, so units and containers are ranked from their cgroups' `io.stat` instead. This is not a core issue, so it needs no replay.
Checks: `merge-check.sh` (cycle, records, index, words, with MESH_CATALOG_DIR set) all pass.
Deliverynovox/hq@7839703b608a — delivered since 2026-10-08T08:55:44Z
Delivery plan — builds nothing: the change touches no module of the mesh's graph
Transitions
2026-10-08 08:49 (new) → proposed (announced): novox/hq#195's head announced
2026-10-08 08:49 proposed → checked (checked): the verdict names this commit
2026-10-08 08:49 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
2026-10-08 08:55 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move
2026-10-08 08:55 published → delivered (done): nothing for a walk to move
The commit's note under refs/notes/mesh-plan keeps every transition: git log --notes=mesh-plan.
<!-- mesh-delivery:view -->
**Delivery** `novox/hq@7839703b608a` — **delivered** since 2026-10-08T08:55:44Z
**Delivery plan** — builds nothing: the change touches no module of the mesh's graph
**Transitions**
- 2026-10-08 08:49 (new) → proposed (announced): novox/hq#195's head announced
- 2026-10-08 08:49 proposed → checked (checked): the verdict names this commit
- 2026-10-08 08:49 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
- 2026-10-08 08:55 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move
- 2026-10-08 08:55 published → delivered (done): nothing for a walk to move
The commit's note under `refs/notes/mesh-plan` keeps every transition: `git log --notes=mesh-plan`.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Registers issue 312 under playbook 03. While investigating issue 306 (checks 5–7x slower on the control node), no mesh tool could report CPU iowait, a disk's utilisation, throughput, wait or queue depth, I/O pressure, or which unit, container or process was doing the I/O. ADR 0245 rules out working around that with a login.
Status
located, inmesh-catalog modules/disk-load, and fixed by novox/mesh-catalog PR #120: a new read-only module with toolsdisk_load,disk_top,disk_filesystemsanddisk_devices. The diagnosis records why this is a module and not a verb on an existing seat, a new seat (ADR 0246),memory-pressureor the container module. It also records one finding from the build:/proc/<pid>/iocannot see another account's processes, so units and containers are ranked from their cgroups'io.statinstead. This is not a core issue, so it needs no replay.Checks:
merge-check.sh(cycle, records, index, words, with MESH_CATALOG_DIR set) all pass.Delivery
novox/hq@7839703b608a— delivered since 2026-10-08T08:55:44ZDelivery plan — builds nothing: the change touches no module of the mesh's graph
Transitions
The commit's note under
refs/notes/mesh-plankeeps every transition:git log --notes=mesh-plan.