The all-well sentence says what it is not a claim about #152

2026-09-30T07:00:20Z

jschoubben commented

2026-09-30 07:00:20 +00:00

novox/hq issue 145. "N machine(s), all doing what they were told …" was true for eleven hours of a mesh in which no module could reach another. Every question it answers is about the mesh and a machine agreeing; none dials a provision, and the mesh composes every one of those grants itself.

It now says so, immediately below itself. This checks nothing and does not pretend to — ADR 0146 decides the check and is deliberately not built. It closes the distance between "the machines are as the mesh described them" and "it works" by naming it, which is where the eleven hours went.

Also: printStatus is separated from the asking, so its exact words can be read by a test with no store, bus or machine. Those words have been acted on and been misleading twice.

make check: only the pre-existing failure.

novox/hq issue 145. "N machine(s), all doing what they were told …" was true for eleven hours of a mesh in which no module could reach another. Every question it answers is about the mesh and a machine agreeing; none dials a provision, and the mesh composes every one of those grants itself. It now says so, immediately below itself. This checks nothing and does not pretend to — ADR 0146 decides the check and is deliberately not built. It closes the distance between "the machines are as the mesh described them" and "it works" by naming it, which is where the eleven hours went. Also: `printStatus` is separated from the asking, so its exact words can be read by a test with no store, bus or machine. Those words have been acted on and been misleading twice. `make check`: only the pre-existing failure.

jschoubben added 1 commit 2026-09-30 07:00:20 +00:00

The all-well sentence says what it is not a claim about 1da96e8803

novox/hq 04-ISSUES/145. "N machine(s), all doing what they were told, all
heard from, running what the mesh would send them, and every module
current with its source" was true for eleven hours of a mesh in which no
module could reach another. An operator read it, and every routine check
they made afterwards — ports from outside, routed services, egress —
passed, because the broken path was module-to-module over the machine's
own name and nothing exercises that.

Every question the sentence answers is about the mesh and a machine
agreeing: applied what it was sent, matches what would be sent, built from
what the source has. None dials a provision, and the mesh composes every
one of those grants itself. So the sentence now says so, in the reader's
way, immediately below it.

This is not the check ADR 0146 describes and does not pretend to be. It
closes the distance between "the machines are as the mesh described them"
and "it works" by naming it, which is where the eleven hours went.

Also: printStatus is separated from the asking, so its exact words can be
read by a test with no store, bus or machine. Those words have been acted
on and been misleading twice — here, and a held module reading as a
machine doing what it was told (04-ISSUES/125) — which makes them the
thing worth holding still.

jschoubben merged commit 2542aa67b0 into main

2026-09-30 07:00:26 +00:00

jschoubben deleted branch fix/145-the-mesh-says-what-its-report-does-not-cover

2026-09-30 07:00:27 +00:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: novox/mesh-controller#152