Issue 325 and ADR 0261: an assignment made while its module's build runs is kept pending #214

2026-10-08T13:50:37Z

mesh-admin commented

2026-10-08 13:50:37 +00:00

Issue 325 (playbook 03, status located, core: replay: R325): a minute after the merge that added sensors asked for its build (issue 300), assign g14 sensors answered "no module of that name".
ADR 0261 (new, topic what runs on it): the controller keeps every build request once asked; assign says which case a missing module is in; an assignment made while the build runs is kept pending, and the controller makes it (claimed under the machine's hold) when the build registers the module; settling is the controller's tick, never a read; an assignment not made is the condition assignment-not-made until answered.
Glossary: pending assignment (Placement), citing ADR 0261; 0261 added to the domain's Decided by.
To-be 45 §2 amended with a dated paragraph: what status lists and the new condition. No as-is document describes what status lists; to-be 45 §2 (in progress, this part live) is where it is described.
Issue 325's Fix section corrected: settling on the tick and not on reads; making a pending assignment sends nothing (the claim about the upgrade announcement is gone); the unknown answer claims only what was checked.

Code: novox/mesh-controller#150 (rebased on 056414b). Replay: novox/mesh-lab#68 (R325 at #150's head dd78357, proved).

Checks: records, index, cycle and words pass locally. Resolve the issue once #150 is live. Do not merge without the operator's approval.

- **Issue 325** (playbook 03, status `located`, core: `replay: R325`): a minute after the merge that added `sensors` asked for its build (issue 300), `assign g14 sensors` answered "no module of that name". - **ADR 0261** (new, topic *what runs on it*): the controller keeps every build request once asked; `assign` says which case a missing module is in; an assignment made while the build runs is kept pending, and the controller makes it (claimed under the machine's hold) when the build registers the module; settling is the controller's tick, never a read; an assignment not made is the condition `assignment-not-made` until answered. - **Glossary**: *pending assignment* (Placement), citing ADR 0261; 0261 added to the domain's *Decided by*. - **To-be 45 §2** amended with a dated paragraph: what `status` lists and the new condition. No as-is document describes what `status` lists; to-be 45 §2 (in progress, this part live) is where it is described. - **Issue 325's Fix section** corrected: settling on the tick and not on reads; making a pending assignment sends nothing (the claim about the upgrade announcement is gone); the unknown answer claims only what was checked. Code: novox/mesh-controller#150 (rebased on 056414b). Replay: novox/mesh-lab#68 (R325 at #150's head dd78357, proved). Checks: records, index, cycle and words pass locally. Resolve the issue once #150 is live. Do not merge without the operator's approval.

mesh-admin commented

2026-10-08 13:51:09 +00:00

Delivery novox/hq@6dda1b1d77bb — delivered since 2026-10-08T14:58:34Z

Delivery plan — builds nothing: the change touches no module of the mesh's graph

Transitions

2026-10-08 14:47 (new) → proposed (announced): novox/hq#214's head announced
2026-10-08 14:47 proposed → checked (checked): the verdict names this commit
2026-10-08 14:47 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
2026-10-08 14:58 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 14:58 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.

**Delivery** `novox/hq@6dda1b1d77bb` — **delivered** since 2026-10-08T14:58:34Z **Delivery plan** — builds nothing: the change touches no module of the mesh's graph **Transitions** - 2026-10-08 14:47 (new) → proposed (announced): novox/hq#214's head announced - 2026-10-08 14:47 proposed → checked (checked): the verdict names this commit - 2026-10-08 14:47 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail - 2026-10-08 14:58 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 14:58 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`.

jschoubben force-pushed fix/325-assign-says-why-a-module-is-not-there from 2a42e12bd2 to ee6a64abf8

2026-10-08 14:24:03 +00:00

Compare

mesh-admin referenced this pull request from novox/mesh-controller

2026-10-08 14:24:16 +00:00

Say why assign finds no module, and keep an assignment pending on its build (hq issue 325) #150

mesh-admin changed title from ~~Issue 325: assign said "no module of that name" while the module's build ran~~ to Issue 325 and ADR 0261: an assignment made while its module's build runs is kept pending

2026-10-08 14:24:24 +00:00

mesh-admin referenced this pull request

2026-10-08 14:38:52 +00:00

ADR 0262: a preference has a default in its manifest, and the operator's own value has none #216

jschoubben added 3 commits 2026-10-08 14:46:44 +00:00

Issue 325: assign said no module of that name while the module's build ran 63754ca874

Register the symptom and the fix in mesh-controller#150 (replay R325 in
mesh-lab#68), and name the pending assignment in the glossary.

ADR 0261: an assignment made while its module's build runs is kept pending 3a09387c8e

The review of mesh-controller#150 found the controller now makes an
assignment after the person's act, which no record decided. Decide it,
cite it from the glossary and to-be 45, and correct issue 325's account
of what is settled where and what is sent.

ADR 0261: one condition per pending assignment, and a raised row kept until it clears

mesh/merge-gate pass: the change touches no module of the mesh's graph

Details

mesh/repo-check pass: its merge-check.sh passed

Details

mesh/delivery delivered

Details

6dda1b1d77

The second review of mesh-controller#150 changed points 1, 6 and 7; say
what the code now does.

jschoubben force-pushed fix/325-assign-says-why-a-module-is-not-there from ee6a64abf8 to 6dda1b1d77

2026-10-08 14:46:44 +00:00

Compare

mesh-admin merged commit 31664fcd80 into main

2026-10-08 14:58:05 +00:00

mesh-admin deleted branch fix/325-assign-says-why-a-module-is-not-there

2026-10-08 14:58:05 +00:00

mesh-admin referenced this pull request

2026-10-11 10:29:45 +00:00

To-be 55: rests-on and touches links, the import's refresh; ADR 0248's index comes from the knowledge base #314

Sign in to join this conversation.

2 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: novox/hq#214