ADR 0244 (2026-10-07) left the code renames of the node-engine and the tool runner for later, with no issue, owner or date; on 2026-10-09 the operator believed them live. They are not: the repository, module, binary, units, launcher and paths are still mesh-host / nox-mesh-host, the tool runner is still node-tools, and the node verb and an open condition say so.
Issue 354 holds the symptom with its evidence, the inventory of what carries the old names (this repository and the four code repositories), the risk (renaming the paths of a self-updating daemon on live nodes needs one release in which both names are accepted) and a staged plan. Acceptance: mesh-cli node show <node> and every condition say node-engine; no file, unit or package on a node is named mesh-host; the tool runner likewise.
The rule, from 2026-10-09: a decision that defers work names the issue that tracks it, with an owner, or the deferral is not accepted. Said in playbooks 02 and 04, as a dated progressive insight on ADR 0244, and checked by cycle.py (an accepted record dated from 2026-10-09, or an older one corrected under the rule, whose text puts work off names an issue in that paragraph or in a dated insight). Measured from ADR 0244's date the check found the same gap in ADR 0241, 0244 and 0270; ADR 0270 is dated 2026-10-09 and now carries an insight naming issue 355 (a held delivery of a module on one machine only is never covered); ADR 0241 is before the rule's start and stands.
ADR 0244 (2026-10-07) left the code renames of the node-engine and the tool runner for later, with no issue, owner or date; on 2026-10-09 the operator believed them live. They are not: the repository, module, binary, units, launcher and paths are still `mesh-host` / `nox-mesh-host`, the tool runner is still `node-tools`, and the `node` verb and an open condition say so.
**Issue 354** holds the symptom with its evidence, the inventory of what carries the old names (this repository and the four code repositories), the risk (renaming the paths of a self-updating daemon on live nodes needs one release in which both names are accepted) and a staged plan. Acceptance: `mesh-cli node show <node>` and every condition say node-engine; no file, unit or package on a node is named `mesh-host`; the tool runner likewise.
**The rule**, from 2026-10-09: a decision that defers work names the issue that tracks it, with an owner, or the deferral is not accepted. Said in playbooks 02 and 04, as a dated progressive insight on ADR 0244, and checked by `cycle.py` (an accepted record dated from 2026-10-09, or an older one corrected under the rule, whose text puts work off names an issue in that paragraph or in a dated insight). Measured from ADR 0244's date the check found the same gap in ADR 0241, 0244 and 0270; ADR 0270 is dated 2026-10-09 and now carries an insight naming **issue 355** (a held delivery of a module on one machine only is never covered); ADR 0241 is before the rule's start and stands.
`merge-check.sh` passes: records, index, cycle (717 documents), words.
Deliverynovox/hq@2349f4bb632d — delivered since 2026-10-09T17:32:13Z
Delivery plan — builds nothing: the change touches no module of the mesh's graph
Transitions
2026-10-09 17:29 (new) → proposed (announced): novox/hq#255's head announced
2026-10-09 17:30 proposed → checked (checked): the verdict names this commit
2026-10-09 17:30 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
2026-10-09 17:32 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move
2026-10-09 17:32 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@2349f4bb632d` — **delivered** since 2026-10-09T17:32:13Z
**Delivery plan** — builds nothing: the change touches no module of the mesh's graph
**Transitions**
- 2026-10-09 17:29 (new) → proposed (announced): novox/hq#255's head announced
- 2026-10-09 17:30 proposed → checked (checked): the verdict names this commit
- 2026-10-09 17:30 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
- 2026-10-09 17:32 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move
- 2026-10-09 17:32 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`.
ADR 0244 left the code renames of the node-engine and the tool runner for later with no issue, owner or
date, and two days on the operator believed them live. Open the issue with the inventory, the risk and a
staged plan; add the rule to playbooks 02 and 04, as a dated insight on ADR 0244, and as a cycle.py check
that found the same gap in ADR 0270 (issue 355).
A review found the check too lenient: an issue cited as context beside a deferral passed it, and one
insight excused every deferral in a record. The tracking issue is now named as tracking it, an insight
covers only its section or what it quotes, and the phrases include "not decided here", "postponed" and
"future work". ADR 0273's four undecided items get issue 357.
jschoubben
force-pushed issues/354-a-decided-rename-was-never-scheduled-and-the-operator-believed-it-live from c9934724a3 to 2349f4bb632026-10-09 17:29:20 +00:00Compare
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.
ADR 0244 (2026-10-07) left the code renames of the node-engine and the tool runner for later, with no issue, owner or date; on 2026-10-09 the operator believed them live. They are not: the repository, module, binary, units, launcher and paths are still
mesh-host/nox-mesh-host, the tool runner is stillnode-tools, and thenodeverb and an open condition say so.Issue 354 holds the symptom with its evidence, the inventory of what carries the old names (this repository and the four code repositories), the risk (renaming the paths of a self-updating daemon on live nodes needs one release in which both names are accepted) and a staged plan. Acceptance:
mesh-cli node show <node>and every condition say node-engine; no file, unit or package on a node is namedmesh-host; the tool runner likewise.The rule, from 2026-10-09: a decision that defers work names the issue that tracks it, with an owner, or the deferral is not accepted. Said in playbooks 02 and 04, as a dated progressive insight on ADR 0244, and checked by
cycle.py(an accepted record dated from 2026-10-09, or an older one corrected under the rule, whose text puts work off names an issue in that paragraph or in a dated insight). Measured from ADR 0244's date the check found the same gap in ADR 0241, 0244 and 0270; ADR 0270 is dated 2026-10-09 and now carries an insight naming issue 355 (a held delivery of a module on one machine only is never covered); ADR 0241 is before the rule's start and stands.merge-check.shpasses: records, index, cycle (717 documents), words.Delivery
novox/hq@2349f4bb632d— delivered since 2026-10-09T17:32:13ZDelivery 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.c9934724a3to2349f4bb63