Judge no longer says "No night is happening" when no module on the machine declares anything to back up: with nothing declared, no night is overdue. The stale-count check still applies.
The night's process now writes the machine's boot id (/proc/sys/kernel/random/boot_id) and CLOCK_MONOTONIC beside its count (new clock.go, stdlib syscall, no new dependency). The health tool runs in another process, so it reads both again: within the same boot the count's age is the monotonic difference, which stops while the machine sleeps. A laptop's count written before suspend therefore does not read as stale on waking. After a reboot, or with an old count that has no boot id, the wall clock judges as before.
Tests: TestNothingDeclaredHasNoOverdueNight failed on main (unhealthy, "No night is happening"). TestACountWrittenBeforeASleepIsNotStale does not compile on main (new fields); with the monotonic branch disabled it fails. TestTheMachinesClockReads checks the clock reads on Linux. go vet, go test -race ./... -count=1 and the words check pass.
Fixes novox/hq issue 489.
1. `Judge` no longer says "No night is happening" when no module on the machine declares anything to back up: with nothing declared, no night is overdue. The stale-count check still applies.
2. The night's process now writes the machine's boot id (`/proc/sys/kernel/random/boot_id`) and `CLOCK_MONOTONIC` beside its count (new `clock.go`, stdlib syscall, no new dependency). The health tool runs in another process, so it reads both again: within the same boot the count's age is the monotonic difference, which stops while the machine sleeps. A laptop's count written before suspend therefore does not read as stale on waking. After a reboot, or with an old count that has no boot id, the wall clock judges as before.
Tests: `TestNothingDeclaredHasNoOverdueNight` failed on main (unhealthy, "No night is happening"). `TestACountWrittenBeforeASleepIsNotStale` does not compile on main (new fields); with the monotonic branch disabled it fails. `TestTheMachinesClockReads` checks the clock reads on Linux. `go vet`, `go test -race ./... -count=1` and the words check pass.
A machine that backs up nothing read as missing its night after 26 hours up, and a laptop's count, last
written before it slept, read as stale on waking until the next look (novox/hq issue 489).
Deliverynovox/mesh-catalog@7f05fad58a81 — delivered since 2026-10-11T19:37:29Z
Delivery plan — builds restic → ace, g14, novox, shanks; no bus step
tier 0: restic
ace: receives restic
g14: receives restic
novox: receives restic
shanks: receives restic
restic keeps data (ADR 0233): what it holds is backed up before it moves
grants step: if this changes what the bus's user list says (a new tool, subject or user), novox is sent that list alone, every build there kept, before restic is judged on its first machine
Machines
restic on ace: passed — healthy 3 times over 3m27s
restic on the rest running it: sent
Transitions
2026-10-11 19:10 (new) → proposed (announced): novox/mesh-catalog#224's head announced
2026-10-11 19:13 proposed → checked (checked): the verdict names this commit
2026-10-11 19:13 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
2026-10-11 19:33 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move
2026-10-11 19:33 published → delivering (go): its walk started: let go by this owner in its group's order, by a person, or on the controller's own path — not a failed walk that carried a later commit for it, after which it waits for a walk of its own commit
2026-10-11 19:37 delivering → delivered (done): its walk is done, carrying its own commit: every machine of its deploy plan passed, or was left as its policy says
The commit's note under refs/notes/mesh-plan keeps every transition: git log --notes=mesh-plan.
<!-- mesh-delivery:view -->
**Delivery** `novox/mesh-catalog@7f05fad58a81` — **delivered** since 2026-10-11T19:37:29Z
**Delivery plan** — builds restic → ace, g14, novox, shanks; no bus step
- tier 0: restic
- ace: receives restic
- g14: receives restic
- novox: receives restic
- shanks: receives restic
- restic keeps data (ADR 0233): what it holds is backed up before it moves
- grants step: if this changes what the bus's user list says (a new tool, subject or user), novox is sent that list alone, every build there kept, before restic is judged on its first machine
**Machines**
- restic on ace: passed — healthy 3 times over 3m27s
- restic on the rest running it: sent
**Transitions**
- 2026-10-11 19:10 (new) → proposed (announced): novox/mesh-catalog#224's head announced
- 2026-10-11 19:13 proposed → checked (checked): the verdict names this commit
- 2026-10-11 19:13 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
- 2026-10-11 19:33 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move
- 2026-10-11 19:33 published → delivering (go): its walk started: let go by this owner in its group's order, by a person, or on the controller's own path — not a failed walk that carried a later commit for it, after which it waits for a walk of its own commit
- 2026-10-11 19:37 delivering → delivered (done): its walk is done, carrying its own commit: every machine of its deploy plan passed, or was left as its policy says
The commit's note under `refs/notes/mesh-plan` keeps every transition: `git log --notes=mesh-plan`.
mesh/merge-gate: PASS — every machine composes with the change as it did without (4 of 4 compose) (modules: restic)
mesh/repo-check: PASS — its merge-check.sh passed, each part in its toolchain: merge-check.sh (go), merge-check-typescript.sh (typescript)
Delivery plan — builds restic → ace, g14, novox, shanks; no bus step
tier 0: restic
ace: receives restic
g14: receives restic
novox: receives restic
shanks: receives restic
restic keeps data (ADR 0233): what it holds is backed up before it moves
grants step: if this changes what the bus's user list says (a new tool, subject or user), novox is sent that list alone, every build there kept, before restic is judged on its first machine
read by no module's build: modules/restic/cmd/restic-backups/health_test.go
Run by the build seat on novox as build-1791745822905900412 (builds --log build-1791745822905900412).
--- the gate: restic
restic: ok, 3 tool(s), keeps repository (rebuildable), state (cache), ready: night by its tool backup_health every 1m0s; measure by unit every 30s
long-running resources without health: 0
files asking for a setting without saying whether it is trusted: 0
1 manifest(s) checked. Judged against the seats this binary carries; a claim on one of the mesh's own seats is judged fully at registration, and a seat declared by a module not given here reads as unknown. Identities judged on a 6-character machine name, against the bounds of the providers given here
judging 0 module(s) changed against 4 machine(s), as the snapshot of 2026-10-11T19:09:35Z says they run
composing every machine as the mesh is
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
composing every machine with the change
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
merge gate: PASS — every machine composes with the change as it did without (4 of 4 compose)
judged by controller development build against the facts of 2026-10-11T19:09:35Z
machines:
- a machine (f35): composes
- holds mesh-dns-resolver (idt): composes
- holds git, holds mesh-artifact-store, holds mesh-broker, holds mesh-catalog, holds mesh-delivery, holds mesh-dns-resolver, holds mesh-store, holds mesh-vault, holds npm-package-registry, the control node, the hub (ygcyr): composes
- a machine (yvbpsm): composes
a merge would rebuild 1 module(s) in 1 tier(s): restic
notes:
- modules/restic/cmd/restic-backups/health_test.go read by no module's build, and rebuild nothing (issue 280)
--- its merge-check.sh (go toolchain)
ok git.novox.be/novox/mesh-catalog/checks/words 0.003s
words: 12 retired words and 70 daemons' lines, none in the 41945 strings of 679 files
ok git.novox.be/novox/mesh-catalog/checks/agenthome 0.012s
agent-home: no archive and no file written into under the agent's home
ok git.novox.be/novox/mesh-catalog/checks/paths 0.006s
paths: no module names another's state on its machine (3 known, listed to go)
long-running resources without health: 69, as kept
testing modules/restic
ok restic/cmd/restic-backups 1.400s
--- its merge-check-typescript.sh (typescript toolchain)
**Merge check** at `7f05fad5`
- `mesh/merge-gate`: **PASS** — every machine composes with the change as it did without (4 of 4 compose) (modules: restic)
- `mesh/repo-check`: **PASS** — its merge-check.sh passed, each part in its toolchain: merge-check.sh (go), merge-check-typescript.sh (typescript)
**Delivery plan** — builds restic → ace, g14, novox, shanks; no bus step
- tier 0: restic
- ace: receives restic
- g14: receives restic
- novox: receives restic
- shanks: receives restic
- restic keeps data (ADR 0233): what it holds is backed up before it moves
- grants step: if this changes what the bus's user list says (a new tool, subject or user), novox is sent that list alone, every build there kept, before restic is judged on its first machine
- read by no module's build: modules/restic/cmd/restic-backups/health_test.go
Run by the build seat on novox as `build-1791745822905900412` (`builds --log build-1791745822905900412`).
```
--- the gate: restic
restic: ok, 3 tool(s), keeps repository (rebuildable), state (cache), ready: night by its tool backup_health every 1m0s; measure by unit every 30s
long-running resources without health: 0
files asking for a setting without saying whether it is trusted: 0
1 manifest(s) checked. Judged against the seats this binary carries; a claim on one of the mesh's own seats is judged fully at registration, and a seat declared by a module not given here reads as unknown. Identities judged on a 6-character machine name, against the bounds of the providers given here
judging 0 module(s) changed against 4 machine(s), as the snapshot of 2026-10-11T19:09:35Z says they run
composing every machine as the mesh is
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
composing every machine with the change
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
merge gate: PASS — every machine composes with the change as it did without (4 of 4 compose)
judged by controller development build against the facts of 2026-10-11T19:09:35Z
machines:
- a machine (f35): composes
- holds mesh-dns-resolver (idt): composes
- holds git, holds mesh-artifact-store, holds mesh-broker, holds mesh-catalog, holds mesh-delivery, holds mesh-dns-resolver, holds mesh-store, holds mesh-vault, holds npm-package-registry, the control node, the hub (ygcyr): composes
- a machine (yvbpsm): composes
a merge would rebuild 1 module(s) in 1 tier(s): restic
notes:
- modules/restic/cmd/restic-backups/health_test.go read by no module's build, and rebuild nothing (issue 280)
--- its merge-check.sh (go toolchain)
ok git.novox.be/novox/mesh-catalog/checks/words 0.003s
words: 12 retired words and 70 daemons' lines, none in the 41945 strings of 679 files
ok git.novox.be/novox/mesh-catalog/checks/agenthome 0.012s
agent-home: no archive and no file written into under the agent's home
ok git.novox.be/novox/mesh-catalog/checks/paths 0.006s
paths: no module names another's state on its machine (3 known, listed to go)
long-running resources without health: 69, as kept
testing modules/restic
ok restic/cmd/restic-backups 1.400s
--- its merge-check-typescript.sh (typescript toolchain)
```
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.
Fixes novox/hq issue 489.
Judgeno longer says "No night is happening" when no module on the machine declares anything to back up: with nothing declared, no night is overdue. The stale-count check still applies./proc/sys/kernel/random/boot_id) andCLOCK_MONOTONICbeside its count (newclock.go, stdlib syscall, no new dependency). The health tool runs in another process, so it reads both again: within the same boot the count's age is the monotonic difference, which stops while the machine sleeps. A laptop's count written before suspend therefore does not read as stale on waking. After a reboot, or with an old count that has no boot id, the wall clock judges as before.Tests:
TestNothingDeclaredHasNoOverdueNightfailed on main (unhealthy, "No night is happening").TestACountWrittenBeforeASleepIsNotStaledoes not compile on main (new fields); with the monotonic branch disabled it fails.TestTheMachinesClockReadschecks the clock reads on Linux.go vet,go test -race ./... -count=1and the words check pass.Delivery
novox/mesh-catalog@7f05fad58a81— delivered since 2026-10-11T19:37:29ZDelivery plan — builds restic → ace, g14, novox, shanks; no bus step
Machines
Transitions
The commit's note under
refs/notes/mesh-plankeeps every transition:git log --notes=mesh-plan.Merge check at
7f05fad5mesh/merge-gate: PASS — every machine composes with the change as it did without (4 of 4 compose) (modules: restic)mesh/repo-check: PASS — its merge-check.sh passed, each part in its toolchain: merge-check.sh (go), merge-check-typescript.sh (typescript)Delivery plan — builds restic → ace, g14, novox, shanks; no bus step
Run by the build seat on novox as
build-1791745822905900412(builds --log build-1791745822905900412).